Firewall and network requirements for CAM Assist

For IT teams: CAM Assist needs outbound HTTPS on port 443, with HTTP/2, to a short list of CloudNC addresses. No inbound ports are needed. This article lists the addresses for the standard and GovCloud versions, the proxy settings that matter, and how to check the connection.

Summary

Requirement	Detail
Outbound traffic	HTTPS, TCP port 443
Protocol	HTTP/2 must be allowed (CAM Assist uses gRPC over HTTP/2)
Inbound traffic	None. Every connection starts from the user's computer.
DNS	The CloudNC addresses below must resolve
Uploads	Allow HTTPS uploads of several MB (part files) without throttling
Certificates	SSL inspection must not break certificate validation

Addresses to allow

Allow outbound HTTPS (port 443) to these addresses. Use the column for the version your users install. See CAM Assist for GovCloud (US) if you're not sure.

Purpose	Standard	GovCloud (US)
Sign-in (in the browser)	`auth.cloudnc.com`	`auth.us-gov.cloudnc.com`
CAM Assist services	`api.cam-assist-gateway.cloudnc.com`	`api.cam-assist-gateway.us-gov.cloudnc.com`
CAM Assist window	`ui.cam-assist-gateway.cloudnc.com`	`ui.cam-assist-gateway.us-gov.cloudnc.com`
Demo parts	`demo-ui.cam-assist-gateway.cloudnc.com`	Not used
Error reports	`sentry.monitoring.cloudnc.com`	`sentry.monitoring.us-gov.cloudnc.com`
AI Support (Help menu)	`zendesk-widget.cam-assist-gateway.cloudnc.com`	Not used
Cutting Parameters Explorer, Autodesk Fusion	`cp-proxy-fusion360.cloudnc.com`	Not used
Cutting Parameters Explorer, Mastercam	`cp-proxy-mastercam.cloudnc.com`	`cp-proxy-mastercam.us-gov.cloudnc.com`
Cutting Parameters Explorer, Siemens NX	`cp-proxy-nx.cloudnc.com`	`cp-proxy-nx.us-gov.us-gov.cloudnc.com`

Also allow api2.amplitude.com (usage data). In the browser, users also need www.cloudnc.com (installers), cloudncsupport.zendesk.com (Help Center) and app.formcrafts.com (support forms).

Proxies, SSL inspection and filtering

If traffic goes through a corporate proxy, SSL inspection, deep packet inspection or content filtering:

Allow the addresses above.
Make sure HTTP/2 isn't blocked or downgraded to HTTP/1.1.
Make sure SSL inspection doesn't replace certificates in a way that breaks trust. If you can't avoid it, exclude the CloudNC addresses from inspection.
Allow large HTTPS uploads.
Allow the CAM package and CAM Assist to open outbound connections in any local firewall or antivirus.

Check the connection

Run these on the user's computer.

Check the addresses resolve. In a command prompt, run:
```
nslookup auth.cloudnc.com
nslookup api.cam-assist-gateway.cloudnc.com
nslookup ui.cam-assist-gateway.cloudnc.com
```
For GovCloud, use the GovCloud addresses. If a name doesn't resolve, DNS or the network is blocking it.
Open https://auth.cloudnc.com in a browser. If the page doesn't load, a firewall or proxy is blocking outbound HTTPS.
Confirm with your network team that HTTP/2 and gRPC traffic is allowed, certificates aren't replaced, and large uploads are allowed.

What users see when something is blocked

Symptom	See
The CAM Assist window never opens, or the progress window closes on Establishing a connection... (Siemens NX)	The CAM Assist window doesn't open in Siemens NX
Sign-in never finishes in the browser	I can't sign in to CAM Assist
We're experiencing high demand keeps coming back	"Usage limit reached" or "We're experiencing high demand" in CAM Assist
An error occurred with Service is not available	"An error occurred" in CAM Assist

Still not connecting?

If the checks pass and CAM Assist still can't connect, contact CloudNC support. Say which version (standard or GovCloud) and CAM package you use, what your IT team has allowed, and include the CAM Assist log files: see Find your CAM Assist log files.