CAM Assist 2.0 requires outbound HTTPS (TCP 443) with HTTP/2 support, DNS resolution for CloudNC domains, and no SSL inspection or DPI that breaks certificate validation. No inbound firewall changes are needed. IT must whitelist specific CloudNC domains and ensure proxies allow HTTP/2, gRPC traffic, and large uploads. Troubleshooting involves verifying DNS resolution, HTTPS connectivity, and proxy behavior.
Summary for IT Teams
CAM Assist 2.0 requires:
- Outbound HTTPS (TCP 443)
- HTTP/2 support (required for gRPC services)
- DNS resolution for CloudNC domains
- No SSL inspection or DPI interference that breaks certificate validation
- No inbound firewall changes
If these conditions are met, CAM Assist will function normally.
Required Network Configuration
1. Allow Outbound HTTPS (Port 443)
The user machine must be able to:
- Initiate outbound HTTPS connections
- Use HTTP/2
- Upload multi-MB CAD/CAM files without payload restrictions or throttling
No inbound ports are required. All sessions are initiated from the local machine to CloudNC services.
2. Whitelist Required Domains
Ensure outbound access on port 443 to the following endpoints.
Authentication (Browser-Based)
CAM Assist 2.0 Services (Client Application – gRPC / HTTP/2)
Commercial
CAM Assist
auth.cloudnc.comapi.cam-assist-gateway.cloudnc.comui.cam-assist-gateway.cloudnc.comdemo-ui.cam-assist-gateway.cloudnc.comzendesk-widget.cam-assist-gateway.cloudnc.com
Cutting Parameters Explorer
- Fusion:
cp-proxy-fusion360.cloudnc.com - Mastercam:
cp-proxy-mastercam.cloudnc.com - Siemens NX:
cp-proxy-nx.cloudnc.com
GovCloud
CAM Assist
auth.us-gov.cloudnc.comapi.cam-assist-gateway.us-gov.cloudnc.comui.cam-assist-gateway.us-gov.cloudnc.com
Cutting Parameters explorer
- Mastercam:
cp-proxy-mastercam.us-gov.cloudnc.com - Siemens NX:
cp-proxy-nx.us-gov.us-gov.cloudnc.com
Diagnostics & Telemetry
We collect diagnostic and telemetry data to collect error logs and improve support.
Sentry
- sentry.monitoring.cloudnc.com
Amplitude
Documentation & Support (Browser)
Proxy and Secure Network Environments
If traffic passes through a corporate proxy, SSL inspection, deep packet inspection (DPI), or content filtering:
- Allow the domains listed above.
- Ensure HTTP/2 traffic is not downgraded or blocked.
- Ensure SSL inspection does not break certificate validation.
- Allow large HTTPS uploads.
- Allow the CAM Assist application to open outbound connections.
If SSL inspection is enforced, CloudNC traffic may need to be excluded from inspection.
Troubleshooting
If CAM Assist cannot connect, fails authentication, or becomes stuck during upload, the issue is typically caused by one of the following:
- DNS resolution failure
- Proxy blocking or filtering
- SSL inspection breaking certificate trust
- HTTP/2 or gRPC traffic being blocked
- Large HTTPS uploads being throttled or rejected
- Local firewall or antivirus blocking outbound connections
1. Verify DNS Resolution
From the affected machine:
nslookup auth.cloudnc.com
nslookup api.cam-assist-gateway.cloudnc.com
nslookup ui.cam-assist-gateway.cloudnc.com
If these hostnames do not resolve, there is a DNS or network restriction issue that must be addressed by IT.
2. Verify HTTPS Connectivity
Open in a browser:
If the page cannot be reached, outbound HTTPS is being blocked by a firewall or proxy.
3. Confirm Proxy and Inspection Behavior
Verify with IT:
- HTTP/2 is allowed.
- gRPC traffic is not blocked.
- SSL certificates are not being replaced in a way that breaks trust.
- Large HTTPS uploads are permitted.
If these checks pass and issues persist, capture network logs from the affected machine for further analysis.