Network Requirements
Troubleshooting connectivity issues, firewall rules, and proxy settings for Dotwork
Last updated: 08 May, 2025
Occasionally Dotwork functions may have trouble performing when Dotwork is not allowed access. This can happen due to issues or limitations applied to your network connection or the environment that you use.
Dotwork relies on modern, stable network connections. If you can sign in and navigate settings but experience issues loading content (for example images, fields, or requiring refreshes), your network may be restricting one or more of the technologies we use.
The following article lists the most common causes of such issues.
1. WebSocket Connectivity
Dotwork’s live updates and interactions all require outbound WebSocket connections over port 443.
If you suspect WebSockets are blocked, try the following:
- Switch to a different network such as a mobile hotspot.
- Disable or re-configure your VPN or secure web gateway.
- Ask your IT team to allow outbound WebSocket traffic, and
wss://on port443. - Ensure Dotwork domains are not blocked (see section 3).
2. If you use a proxy or firewall
If your organization uses a firewall or secure web gateway, confirm that Dotwork domains and services are allow-listed. Dotwork’s core infrastructure is hosted on AWS and uses dynamic IP addresses, so we recommend allowing traffic by domain rather than by IP.
Please ensure that you provide Dotwork with a by-pass. The following specifications will help.
- The proxy server must support WebSocket connections over HTTP/1.1 on port
443. - The proxy server must support gRPC-Web or gRPC connections over HTTP/1.1 requests on port
443. - The proxy server must support HTTP connections over HTTP/1.1 on ports
443. - The proxy HTTP version should be set to 1.1.
- Browser destination ports:
443using HTTPS protocol. - TLS: 1.2 and 1.3. (Dotwork uses AWS Security Policy
ELBSecurityPolicy-TLS13-1-2-2021-06for protocols and ciphers. We will migrate to TLS 1.3 once fully supported.) - Increase proxy idle/handshake timeouts to 120–180 seconds.
- Increase proxy per request timeout to 60 seconds.
- Ensure the proxy does not strip
UpgradeorConnectionheaders. - For third party integrations different network allowances will be needed.
3. Dotwork Domains Allowlist
In secure environments you must permit access to all Dotwork domains for the application to function correctly.
| Domain pattern |
|---|
*.dotwork.app |
cdn*.dotwork.app |
After reviewing the steps above, if you still experience connectivity problems please contact our support team at support@dotwork.com. We’re here to help.
© 2025-2026 Dotwork, Inc. All rights reserved.