Troubleshooting
Connection Problems
Troubleshoot WebSocket handshake drops, SSL/TLS negotiation errors, firewall blocks, and latency spikes.
Overview
The Asiyst Web SDK establishes encrypted bidirectional streams to deliver real-time speech synthesis, token streaming, and telemetry.
WebSocket Fallback to SSE
If a client environment (such as an enterprise proxy or restrictive mobile browser) terminates WebSockets (wss://api.asiyst.com), the SDK automatically falls back to HTTP/2 Server-Sent Events (SSE) within 3 seconds.
You can verify the active transport mode at runtime:
console.log("Active Transport:", Asiyst.getTransportMode()); // 'websocket' | 'sse'
Corporate Firewall & Proxy Blocks
For enterprise corporate networks, ensure the following endpoints and ports are open on your egress firewall:
https://api.asiyst.com(Port 443 / HTTPS)
wss://api.asiyst.com(Port 443 / WSS)
https://cdn.asiyst.com(Port 443 / HTTPS)
SSL / TLS Certificate Verification
All connections to Asiyst endpoints require TLS 1.3 or TLS 1.2. If testing in local development environments with custom self-signed SSL certificates, ensure the local root certificate authority is trusted by your browser.
Latency & Geographic Routing
Asiyst Edge Gateways route traffic to the closest geographical point of presence (North America, Europe, Asia-Pacific). Average global connection establishment latency is under 45 milliseconds.