Before Enscape tries connecting to the Enscape licensing server to authenticate the License Key, you should check with your IT Administrator as to whether your machine connects to the internet via a proxy server and, additionally, whether you will need to specify some URL/IP exceptions in your Firewall.

Open the General Settings  window and select the Network option. The proxy server settings displayed are taken from your Mac’s System Preferences. If you want to enter other proxy server settings, you have to do this in the System Preferences of your Mac.

You can find the settings under System Preferences > Network > Used Network Connection > Advanced… > Proxies

Each time you open the network tab or put in a new proxy address, Enscape will automatically test the connection. You will see a green checkmark on the bottom right confirming that the connection is working. If you get an error message and the proxy settings are set correctly, it means that Enscape or the specified port is blocked by an antivirus program or firewall.

If Enscape cannot connect to the services you need even though you are not using a proxy server, you need to check your firewall settings.
The Mac firewall usually does not block connections of signed applications. However, if it does, or if you are using a 3rd party firewall, you will need to allow the Enscape app to communicate and possibly add other exceptions. You can find Mac firewall settings in Security & Privacy under System Preferences.

The following connections are required for Enscape to communicate with the Enscape licensing server as well as the server for panoramas, web standalones, the asset library, and the Enscape feedback feature.

http://licensing.enscape3d.com

The port for this URL should be set to ‘80‘ and the protocol should be set to TCP (http).

Also, please set the following URL exceptions that are for connection to the Enscape Asset Library, Web Standalone, Panoramas, Site Context and Feedback services. The port number should be set to listen on port ‘443‘ with the protocol being set to TCP (http and https):

https://chaos.com
https://my.enscape3d.com
https://api2.enscape3d.com
https://enscape-assets.chaosgroup.com
https://enscape-assets2.chaosgroup.com
https://asset-assetbucket-1binh6y04tlmk.s3.eu-central-1.amazonaws.com
https://feedback-feedbackbucket-kqjsgygrcfpd.s3.eu-central-1.amazonaws.com
https://panorama-panoramabucket-17m6l0kcpd6x2.s3.eu-central-1.amazonaws.com
https://enscape-mobile-runtime.s3.eu-central-1.amazonaws.com
https://webstandalone-raws3-p2dyeqrxcbok.s3.eu-central-1.amazonaws.com
https://webstandalone-bundles3-17tmvx8yf2hr9.s3.eu-central-1.amazonaws.com
https://geocoding.geofabrik.de
https://tile.geofabrik.de
https://overpass.geofabrik.de
https://api.ipgeolocation.io
https://www.gmrt.org

To understand how to add exceptions to a firewall, please refer to the information provided by your solution’s vendor.

If you continue to have issues connecting to our servers through your firewall, then please get in touch with us here.