Firewall configuration for Autodesk Services

article #1050, updated 2724 days ago

Here:

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/AutoCAD-requests-to-Autodesk-servers-blocked-by-proxy-servers.html

and here:

https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/Collaboration-for-Revit-Proxy-Server-and-domain-exceptions-for-Autodesk-A360-services.html

and here:

https://knowledge.autodesk.com/support/fusion-360/troubleshooting/caas/sfdcarticles/sfdcarticles/Fusion-360-cannot-access-the-services-through-proxy.html

are found some very interesting items which may be helpful when configuring either firewalls or proxy servers to work with AutoDesk products. We need to except the following FQDN’s from all proxy intervention on ports 80 and 443:

*.autodesk.com
*.google-analytics.com
*.cloudfront.net
*.virtualearth.net
*.autocadws.com
*.newrelic.com
*.akamaiedge.net
*.amazonaws.com
*.s3.amazon.com
*.edgekey.net
*.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
cdn.web-platform.io
*.notifications.api.autodesk.com
*.pubsub.pubnub.com
cdn.jsdelivr.net
akamai.com
*.akamai.com
akamaitechnologies.com
*.akamaitechnologies.com
*.protolabs.com
tracepartsonline.net
*.tracepartsonline.net
mcmaster.com
*.mcmaster.com

Categories: