Skip to main content
Peec AI runs in the browser and talks to a small set of hosts over HTTPS. Most networks need no changes. On a network with a strict firewall, or with a proxy that inspects Transport Layer Security (TLS) traffic, the app may not load, sign-in may fail, or the Agent may show Reconnecting…. This page lists what to allow and how to check your setup.
Share this page with your IT or network team. In short: allow the required hosts, and pass responses from api.peec.ai and backend.peec.ai through without buffering them.

Hosts to allow

All connections start in the browser and use HTTPS on TCP port 443. No inbound rules are needed. Allow hosts by name, because their IP addresses can change.

Required

Sign-in

Allow the hosts for the sign-in methods your team uses. Sign-in with Google, Microsoft, or SSO opens a popup window. Allow popups for app.peec.ai.

Optional

Each of these hosts serves one feature. Blocking one turns off that feature and nothing else.

How Peec connects

Most of the app uses short HTTPS requests. Two connections stay open instead, and the server sends data through them as it becomes available. Both use server-sent events (Content-Type: text/event-stream) over ordinary HTTPS. Peec may also use WebSockets on these hosts in the future. Both streams work the same way:
  • The server sends a keep-alive ping as soon as a stream opens, and every 15 seconds after that.
  • If nothing arrives for 35 seconds on the Agent stream, or 45 seconds on live updates, the app closes the connection and opens a new one.
  • A stream stays open for up to 30 minutes. Then it closes and the app opens a new one.
The app also keeps a connection to firestore.googleapis.com open for live account data. That connection switches to long polling by itself when a proxy holds streamed responses back.

Polling fallback for the Agent

If nothing arrives within 3 seconds of opening the Agent stream, the app assumes that a proxy is holding the response back. It then switches to polling and asks api.peec.ai for new content every second while the Agent is working, and every 5 seconds otherwise. The Agent still works. Answers arrive in small steps instead of flowing in. The browser remembers the fallback for 7 days, so later chats start on polling right away. Live updates have no fallback. Behind a proxy that buffers them, changes made elsewhere show up after you reload the page.

Proxy and firewall settings

Proxies that inspect TLS traffic, such as Netskope or Forcepoint, often hold a response back until it is complete. A streamed response is never complete while the connection is open, so nothing reaches the browser. Ask your network team to:
  • Allow the hosts. Every host in the Required table, and the Sign-in hosts for the methods you use.
  • Exclude api.peec.ai and backend.peec.ai from TLS inspection. Depending on the product, this is called an SSL decryption bypass or a steering exception.
  • Pass streamed responses through as they arrive. Responses from these two hosts with Content-Type: text/event-stream must not be buffered.
  • Keep idle connections open for at least 60 seconds. Each stream carries a ping every 15 seconds.
  • Skip response size limits and content scanning for the streams. One Agent answer can stream several hundred kilobytes.
  • Allow uploads and downloads on api.peec.ai if your team attaches files to Agent chats or downloads files the Agent creates.

Troubleshooting

The app doesn’t load

A blank page usually means that storage.googleapis.com is blocked. The app’s code loads from there.

Sign-in fails or loops

Check the Sign-in table above for the method you use. Sign-in with Google, Microsoft, or SSO opens a popup, so a popup blocker can stop it. The email link form needs challenges.cloudflare.com before it can send the link.

The Agent shows “Reconnecting…”

The Agent stream isn’t getting through. The app switches to polling after 3 seconds, so you can keep chatting. If the message doesn’t go away, or the Agent never answers:
  1. Open https://api.peec.ai/health in the same browser. You should see a short status message. If the page doesn’t load, api.peec.ai is blocked.
  2. Try the same chat on a different network, for example a phone hotspot. If it works there, the cause is in your corporate network.
  3. Send your network team the settings from this page.

Capture a network log for Peec support

If the steps above don’t help, a browser network log shows where the connection stops. In Chrome or Edge:
  1. Open a new tab and go to chrome://net-export (in Edge: edge://net-export).
  2. Leave Strip private information selected, unless Peec support asks for more detail.
  3. Select Start Logging to Disk and choose where to save the file.
  4. In another tab, open Peec, start an Agent chat, and wait until Reconnecting… appears.
  5. Go back to the net-export tab and select Stop Logging.
  6. Send the saved .json file to support@peec.ai, together with the time the issue appeared and your company name.
The log lists the hosts your browser talked to during the capture. Review it before you send it if you prefer.