What kind of rate limit are you facing?

the Cloudflare blocking the Railway CLI is on Railway's side, not yours. It's Railway's own servers protected by Cloudflare, and you don't have access to that

from what ai says its that

So you're not able to access Railway CLI?

That's not something you can change — the Cloudflare blocking the Railway CLI is on Railway's side, not yours. It's Railway's own servers protected by Cloudflare, and you don't have access to that.

It's likely just a temporary rate limit on the Railway API from the CLI making too many log requests today. Just check the logs directly in the Railway web dashboard instead — go to railway.com, open your project, click the service, and hit the Deployments tab to see live logs

this is what it says fully

Auth is fine. The logs endpoint itself is being blocked by Cloudflare temporarily. Check the status directly at the Railway dashboard: railway.com/project/1a57c388-e2d3-49f3-848f-4a40679ce37b — you can see the live logs there. The last log we saw was still retrying every 5 minutes, so it's either still rate limited or has connected by now.

I asked for what exactly is happening.

I didn't ask for what AI said.

oh uh

gimme sec

The 429 is Discord blocking Railway's server IP, nothing wrong with your code or token

Why the Railway CLI logs are broken:

Completely separate issue — railway logs CLI command is hitting a Cloudflare challenge on Railway's API, probably because the CLI made too many requests today. The web dashboard still

Railway bot → stuck in 429 retry loop, retrying every 5 min

Discord's identify ban on Railway's IP could last anywhere from a few hours to 24 hours depending on how bad the quota was exceeded

.

.

because i was updating it too often i suppose, and re-deploying but thats my guess

i tried putting a different discord token to see if that would fix it but it didnt 🤷

anyways, is there any way to fix this problem i'm having?

is there any fix to this issue or no?

@pepper

Okay please stop sending AI's responses. It's throwing me off.

Let me clarify.

Your application is being rate limited by Discord.

Is that correct?

yes

i believe railway's ip is being blocked by discord

for my discord bot

idk

Have you tried adding an authorization header?

I’ll check it out a bit later, im go sleep

@pepper

nvm i fixed it actually, i guess switching your region in railway fixes it

Yeah because that most likely changes the IP.

It most likely wouldn’t be a permanent fix if you’re making over 50 requests per second or making too many invalid requests.

im wondering tho, what happens if i change it back, does it change back to the same ip or a different one?

I don’t know.

Also, read the Discord documentation.

There’s a way to contact them about rate limits if you’re absolutely sure it’s not your problem.

i guess