Hello TeamViewer Community,
We are integrating the TeamViewer Web API / Session API to allow IT support technicians to connect remotely with clients who need assistance completing digital documentation on our web portal (hdclaims.co.uk).
Issue Description:
When initiating an embedded remote support session via the Web API REST endpoint (/api/v1/sessions), the API correctly returns the session ID and code. However, when rendering the TeamViewer Web Client iframe on our portal, the session fails to connect and times out with a WebSocket connection closed before connection was established error.
Technical Setup:
- API Version: TeamViewer REST API v1
- Frontend: React SPA with embedded Web Client iframe
- Network: HTTPS / TLS 1.3 over Nginx proxy
Steps Taken:
- Confirmed API token permissions for
Session Management and User Management. - Verified that direct TeamViewer client-to-client connections work without issues.
- Inspected CORS headers on our server to ensure no origin policy blocking is occurring.
Is there a specific Content Security Policy (CSP) directive or WebSocket port restriction required on external .co.uk domains when hosting the TeamViewer Web Client iframe?
Any technical insights would be appreciated!
