“System « … » does not exist on this gateway” (rp_code 1067) in Senzoukria

Rithmic answers rp_code 1067 when the system name you typed is not served by the gateway you connect to. Senzoukria fetches the gateway’s own list and prints it, so you can pick the exact system your account lives on.

Senzoukria · Troubleshooting · Updated September 2026

At a glance

Message
“System « {system} » does not exist on this gateway. Systems accepted here: …”
Rithmic code
rp_code 1067, “System name received is invalid”
Where
Test connection, Connect, or the “System recognised” step of the connection diagnostic
Related warning
“System name … isn’t one of {broker}’s (expected: …)” in the form

What you see

After a test or a connect, the error reads “System « {system} » does not exist on this gateway. Systems accepted here: {list}. (Check the gateway URL too: a test gateway does not know the prop firms’ systems.)”. When the list itself cannot be fetched, the text becomes “System « {system} » was rejected by gateway {url} (rp_code=1067), and the list of accepted systems could not be retrieved. Check both the system name AND the gateway URL.”

The connection diagnostic reports the same thing at its second step: ““{system}” is not among the systems this gateway serves. Fetch the live list and pick the one your account lives on.”

Why it happens

A Rithmic gateway only accepts the systems it serves. rp_code 1067 is Rithmic’s answer to a name it does not know at that address. The two usual reasons are a typo in the system name, and a gateway that is the wrong one: the “Rithmic Test” gateway is dedicated and only serves “Rithmic Test”, so a prop firm’s system typed against it is refused whatever the credentials.

Before you even test, the form can warn that the name “isn’t one of {broker}’s” when it differs from the systems the catalogue lists for the broker you picked. The gateway’s live list wins over that catalogue: if your firm moved to another system, the live list confirms it.

How to fix it

  • Pick your broker or prop firm from the list: it fills the gateway URL for you.
  • Click “Fetch live system list from gateway” and choose the system from that list rather than typing it. Spaces and capitals count.
  • If your firm’s system is missing from the list, you are on the wrong gateway. Test gateways do not serve prop-firm systems; production access points all serve the same systems.
  • Run the connection diagnostic: “Gateway and system agree” must pass before the login step means anything.

What it is not

  • Not a password problem: the login is never evaluated when the system is unknown.
  • Not the same as rp_code 13. An unknown system gives 1067; an account unknown on a real system gives 13.

When to contact support

When none of this helps, write to support through Menu → Report a problem or on the Senzoukria Discord. Include the system name exactly as your firm wrote it, the access point you selected and the list the gateway returned. No password or user ID is needed.

In the same section

This page in other languages

Frequently asked questions

Which access point should I use?
Keep “Chicago (core)” unless you have measured a better route. Every production access point serves the same systems; only the network route changes.
The system is in the list but the login is still refused. What now?
Then the route is correct and the refusal comes from the account layer, usually rp_code 13. Follow the rp_code 13 checks.

Keep reading

Strategy researchTest a trading strategy, from observation to challenge rulesDefine an observation, question it with the copilot, write a rule and explore costs, drawdown and fictional challenge limits in an interactive example.Quant · Start hereQuant trading for beginners: from idea to backtestDefine a testable rule, choose suitable data and evaluate later periods after costs.Order flow · HubOrder flow trading: the complete guideThe hub. What order flow is, what it shows — aggression, delta, imbalance, absorption, liquidity — and the tools that read it, each linked to a full guide.