Syntic Code behind a proxy or firewall
On company networks, Syntic Code may need to go through a proxy or trust your company’s security certificate. If you see “Can’t reach the Syntic server — check your internet” with a countdown, or requests fail only at work, set the proxy and certificate options below.
Signs of a network problem
| Message | Meaning |
|---|---|
| ”Can’t reach the Syntic server — check your internet (…) · retrying in 4s · attempt 2/10” | The request could not get through. Syntic Code retries up to 10 times; the reason in brackets says why. |
| ”Could not reach the Syntic server after 10 attempts” | Every retry failed. Fix the connection and send your message again. |
| Certificate or TLS errors | A security device on your network is inspecting encrypted traffic. |
Use a proxy
Set the proxy before you start syntic:
export SYNTIC_HTTPS_PROXY="http://proxy.example.com:8080"
synticThe standard HTTPS_PROXY and HTTP_PROXY variables work too. To skip the proxy for some hosts, list them, comma-separated, in SYNTIC_NO_PROXY.
Trust your company’s certificate
If your company inspects encrypted traffic, point Syntic Code at its certificate bundle (a PEM file your IT team can give you):
export SYNTIC_EXTRA_CA_CERTS="$HOME/certs/company-ca.pem"Syntic Code refuses to start if the file contains no certificates, so you find out right away if the path is wrong. If your company requires a client certificate, ask IT for it; Syntic Code supports mutual TLS too.
What to allow in a firewall
Syntic Code only talks to Syntic’s own hosts over HTTPS (port 443), and it refuses any other API address. Ask your IT team to allow HTTPS to syntic.ai and its subdomains. Those cover the browser sign-in page and the Syntic platform that runs the model.
The browser sign-in also needs your browser to be able to return to your own computer at a local address. Security software that blocks this causes a sign-in loop.
To cut background traffic to a minimum, set SYNTIC_PRIVACY=essential. It stops the update check, connection warm-up and usage refresh, while requests to the model keep working.
Still failing?
Run syntic --debug api to see each request and its error, and include the output (with keys removed) when you contact support.