Scope: This guide applies to Omnifact Cloud. It does not apply to private on-premise installations or custom domain deployments.
Required Hostnames and Ports
The simplest and most reliable configuration is to allow outbound traffic to*.omnifact.ai and omnifact.ai on TCP port 443 (HTTPS).
If your firewall or proxy policy does not support wildcard domains, configure explicit rules for the following hostnames:
External Identity & OAuth Providers:
- If your organization uses Single Sign-On (SSO), allow outbound access to your identity provider (such as Microsoft Entra ID, Okta, or Google Workspace).
- If your organization enables OAuth-based MCP integrations (such as HubSpot, Atlassian, Slack, or GitHub), user browsers must also be able to reach the respective third-party OAuth authorization server before redirecting back to
https://chat.omnifact.ai/oauth/mcp-callback.
Resolving Common Network and Proxy Blockers
Even when ports and hostnames are open, specific inspection features on corporate proxies can disrupt platform functionality.WebSocket Connections
Chat responses and live conversation updates stream in real time over persistent WebSocket connections (socket.io) to api.omnifact.ai:
- Your proxy or next-generation firewall must allow the HTTP
Upgrade: websocketheader. - If WebSockets are blocked or improperly intercepted, the web interface loads, yet responses fail to stream or experience significant delays.
TLS/SSL Inspection
Deep packet inspection (SSL decryption) can break encrypted authentication and streaming handshakes:- Exclude
sso-auth.omnifact.aiandsso-app.omnifact.aifrom TLS inspection. Re-signing certificates during SAML handshakes often causes identity provider authentication to fail. - If users experience dropped chat streams or failed document uploads, exclude
chat.omnifact.aiandapi.omnifact.aifrom TLS inspection as well.
Response Streaming and Buffering
Omnifact delivers API responses incrementally as tokens generate:- Services such as Published Spaces and the AI Gateway stream data from
connect.omnifact.aiusing HTTP chunked transfer encoding (Server-Sent Events). - Configure your proxy not to buffer streaming responses and avoid prematurely closing long-lived connections.
Server-to-server API integrations only require access to
connect.omnifact.ai. If developers open the interactive API reference at connect.omnifact.ai/docs in a browser, ensure your network also permits cdn.jsdelivr.net.IP Address Limitations
Omnifact does not provide static IP addresses for cloud services. Incoming traffic routes through Cloudflare’s globally distributed edge network, so IP addresses behind each hostname change dynamically. Always allow traffic by hostname rather than IP address whenever possible. If your firewall strictly requires IP-based rules, you can permit Cloudflare’s published IP ranges.Verifying Network Connectivity
1
Sign in to the web app
Open
https://chat.omnifact.ai in your browser and sign in using your standard credentials or Single Sign-On.2
Send a test message
Start a new chat and send a prompt. Confirm that the response streams smoothly word by word without pausing or timing out.
3
Upload an attachment
Attach a small document or image to the conversation. Confirm that the file uploads cleanly and is analyzed in chat.
If access worked during initial testing and later stops, check whether your firewall rule was created with a temporary exception or lease that expired.
Contacting Support
If your team continues to experience connection issues after applying these rules, email support@omnifact.ai with:- The exact date, time, and timezone when the issue occurred
- The specific hostname or URL that was blocked
- Any error code or block page shown by your browser, proxy, or firewall