We can't change, re-link, or restore the login on a Railway account, including through the CLI or the API. That's a security boundary that protects the account, and no amount of ownership proof changes it.

There are two ways back in. The first is to sign in through the GitHub account that is already linked to your original Railway account. The "already linked to a different GitHub account" error means the GitHub identity you're using now isn't that one. The second is to get the login-code emails to arrive at the address on that account. Delivery to an Apple private relay address depends on the relay forwarding them, so that part has to be sorted out on Apple's side.

Once either route works, you can sign in normally and manage the account's email and login settings yourself.

This did not resolve the issue. I have already tried both suggested routes: the GitHub identity named in the error opens a different empty Railway workspace, while login-code emails to the original Apple private relay address do not arrive. Please escalate this case to a human support engineer and advise whether any supported manual account-recovery process is available. I am not asking for an account merge, authentication bypass, or project transfer, and I will not share credentials or tokens publicly.

We don't have a manual account-recovery process. That means we can't restore, change, or re-link the login on that account from our side, through the CLI, or through the API, and that holds even with proof of ownership. The "Not Authorized" response to the email change request comes from that same security boundary, which is there to protect the account.

Access has to be recovered through the provider that handles your sign-in. Once you're back in, you can manage the account's email and login settings yourself.