Troubleshooting Revit Live

This section describes common issues when working with Revit Live and how to resolve them.

Proxy server settings changes required to unblock Live Service

Issue: While using Autodesk Revit Live, requests to Autodesk online services, including Live Service, are being denied.

Cause: Autodesk desktop product requests to Autodesk online services can be blocked by proxy servers.

Solution(s): If your network uses proxy servers to access the internet, one of the following methods can prevent internet access issues for Autodesk service components.

Note: Websense virus software must be disabled.

Exception Rules

If you have problems accessing Autodesk servers through a proxy, try adding an exception to your internet browser proxy settings.

1. From your computer's Start menu, select Control Panel.
2. Select Network and Internet, and then Internet Options.

   The Internet Properties dialog appears.

3. In the Connections tab, click LAN settings.

   The Local Area Network (LAN) Settings dialog appears.

4. Under the Proxy server group, select Use a proxy server for your LAN, and then click Advanced.

   The Proxy Settings dialog appears.

5. Under the Exceptions group, add an exception to allow the following domains to bypass the proxy server:
   • *.autodesk.com
   • *.s3.amazon.com
   • *.amazonaws.com
   • *.edgekey.net
   • *.akamaiedge.net
   • *.google-analytics.com
   • *.cloudfront.net
   • *.virtualearth.net
   • *.autocadws.com
   • *.newrelic.com
   • *.getsatisfaction.com
   • *.autodesk360.com
   • *.skyscraper.autodesk.com
Note: Make sure your network is set up to route requests directly to these domains without routing through proxy servers.

Authenticated proxies

To use Autodesk online components through proxy servers with Authentication enabled:

1. Enable http (port 80) and https (port 443) access to the following domains in the proxy without Proxy Authentication (i.e. Access for "All users" or Anonymous access through the proxy):
   • *.autodesk.com
   • *.autodesk.com
   • *.s3.amazon.com
   • *.amazonaws.com
   • *.edgekey.net
   • *.akamaiedge.net
   • *.google-analytics.com
   • *.cloudfront.net
   • *.virtualearth.net
   • *.autocadws.com
   • *.newrelic.com
   • *.getsatisfaction.com
   • *.autodesk360.com
   • *.skyscraper.autodesk.com
   • *.ssl.google-analytics.com
   • *.js-agent.newrelic.com
   • *.hotjar.com
   • *.optimizely.com
   • cdn.jsdelivr.net
   • www.googletagmanager.com (optional)
   • cdn.web-platform.io (optional)

Common questions

• Why can't we use IP addresses for the firewall rules?

  The Single Sign-On solution from Autodesk takes advantage of Akamai for network route optimization. Since the Akamai network has many 1000s of edge nodes that change over time, it is not advisable to filter based on IP addresses. If filtering is required, then it should be done by URL (*.autodesk.com).

• Why should we enable special rules in the proxy server for certain URLs?

  Authentication information is not currently sent to the proxy server; hence an exception rule is required on the proxy to enable these communications anonymously.

• What if we don't use proxy servers and access the control list directly on the firewall?

  If the rules can be added with DNS names you can use the URLs mentioned above to allow the traffic.

• We have secureNAT on our clients. Why can't I access Autodesk Revit Live services?

  The issue is due to the ISA Firewall service performing reverse DNS name resolution to determine whether a rule applies for every request from SecureNAT client. Try adding Akamai hosts (*.edgekey.net and *.akamaiedge.net) to the exception lists to resolve the issue.