The connection error: Did not receive file manifest reply from server is commonly attributed to the customer's Network environment. In some cases, restarting the affected local machine is able to address this Network condition.
For more severe cases, we recommend getting your organization's IT Support team involved, and have them verify the local network exceptions across all endpoints (e.g., Web Proxy, VPN, Firewall) using the following guidelines:
Firewall Requirements: https://support.authentic8.com/support/solutions/articles/16000026587-firewall-rules-needed-for-silo-connections
Proxy Configuration for Windows Registry
https://support.authentic8.com/support/solutions/articles/16000042417-how-to-use-the-registry-to-update-proxy-settings
Please ensure that bi-directional traffic is permitted across all Silo server endpoints per the guidelines above.
If you continue to experience a connection error, please attach the session.log from the affected local machine, so we may help look for additional clues. The session.log file(s) can be found in one of the following folder paths:
If you continue to experience a connection error, please attach the session.log from the affected local machine, so we may help look for additional clues. The session.log file(s) can be found in one of the following folder paths:
Folder Location for Client Logs
Windows
%TEMP%\Authentic8\session.log
macOS
~/Library/Logs/com.authentic8.launcher.log
Alternative Access
Alternative Access
If enabled for your organization, you may try to access Silo using the Web Client at www.a8silo.com which utilizes the broadly used HTTPS protocol
Please contact Support for any additional questions