“The gateway did not answer” when connecting Rithmic in Senzoukria
When the first step of the Senzoukria connection diagnostic fails, no WebSocket session could be opened to the Rithmic gateway: a wrong URL, a colocation-only access point, or a firewall, VPN or proxy on the way. Nothing about the account has been tested yet.
Senzoukria · Troubleshooting · Updated September 2026
At a glance
- Message
- “The gateway did not answer. Check the URL, and that no firewall, VPN or proxy is blocking it.”
- Where
- Connection diagnostic, step “Gateway reachable”; a Test connection shows “connect failed: …”
- Gateway probe timeout
- 8 seconds for the list of systems
- Default access point
- Chicago (core)
What you see
The diagnostic stops at its first line with “The gateway did not answer. Check the URL, and that no firewall, VPN or proxy is blocking it.” The following steps are skipped: “Not run — the gateway did not answer.” A plain Test connection reports “Test failed: connect failed: …” with the network error. If the URL was left empty, the step reads “Not run — no gateway URL on this connection.”
Why it happens
- The URL does not start with wss://. The form refuses it with “Gateway URL must start with wss://”.
- The Colo75 access point is selected. Its host name resolves only to private addresses, so an ordinary internet connection can only time out. The form marks it “Colo75 — colocation only” and warns: “This access point is reserved for colocated servers… Keep Chicago (core) unless your machine is hosted inside that facility.”
- A firewall, antivirus, corporate proxy or VPN blocks outgoing WebSocket traffic from the app.
- A custom URL was typed by hand with a mistake in the host name.
How to fix it
- Pick your broker from the list so the gateway URL is filled for you, then choose “Chicago (core)” in Access point.
- If you typed a custom URL, compare it character by character with what your broker gave you; it must begin with wss://.
- Allow Senzoukria through the firewall or antivirus, and try once without the VPN or proxy to see whether the step turns green.
- Run the diagnostic again. When “The gateway answered.” appears, the next steps check the system and the login.
What it is not
- Not a credentials problem: the login has not been attempted.
- Not a closed market: gateways answer on weekends too, even when no tick is published.
- Not fixed by picking the closest city. Every access point serves the same systems, and the closest is not automatically the fastest.
When to contact support
If the message comes back after these steps, report it from Menu → Report a problem or on the Senzoukria Discord. Copy the diagnostic with “Copy the result” (it contains no password) and say which access point, VPN or proxy you use.
Related pages
- System name not on this gateway
- Connection diagnostic
- Rithmic connection and gateways
- Direct connection
In the same section
- Heatmap could not start (EvalError)
- Provider unavailable
- Market closed, nothing new
- Chart could not start
- Report could not be sent
- Bubble rebuild refused
- Sign-in server unreachable
- Subscription refused
This page in other languages
Frequently asked questions
- Is the “Rithmic Test” gateway an access point like the others?
- No. “Rithmic Test” has its own dedicated gateway, and access points are production only. It serves only the “Rithmic Test” system.
- Should I switch to the access point closest to me?
- Only after measuring. The form states that every access point serves the same systems and that the closest is not automatically the fastest.