#Critical Cloudflare 503's on Express Backend

66 messages · Page 1 of 1 (latest)

twilit light
#

Two quick questions on outages I've using Cloudflare + Railway

  1. Does railway do any rate-limiting? If so, can this be disabled?
  2. Is there a more lengthy post about issues when enabling cloudflare for backend services? (beyond what is mentioned here https://docs.railway.app/deploy/exposing-your-app)

What we're seeing is that immediately after enabling the Cloudflare orange cloud, the express backend chokes on 100% of requests returning 503 errors. I've had many back-and-forths with the Cloudflare team and the current guess is that the origin server (Railway) is throwing these 503s.

noble tide
#

Does railway do any rate-limiting? If so, can this be disabled?
no, it doesn't do any ratelimiting

charred scarab
#

Please share your custom domain's url, railway's static url & project id.

abstract olive
#

Did you see the Cloudflare section at the bottom?

#

Where you need to have it set to full not flexible?

#

We don’t do rate limiting

twilit light
#

I have it set to full not flexible

#

Project: 46b499ee-c469-4cd0-8d59-e80657e4db3c

Service: 90a80fa7-879c-4463-8675-e3a1aeeafc8c

charred scarab
#

Your application isn't responding

#

Also, what's the url that railway provided you?

twilit light
charred scarab
twilit light
charred scarab
#

Does it return 503 for you?

twilit light
#

No, because I've disabled cloudflare

#

The moment I enable cloudflare I get all the 503's included in the chrome inspector screenshot above

abstract olive
#

So we can see

twilit light
abstract olive
#

Or add another route that we can check on?

#

Without repro it’s impossible to check

twilit light
#

Here is Cloudflare support's most-recent message

#

I've been going back-and-forth with them nearly 2-months on this issue

abstract olive
#

So this is quite odd

#

It seems to be a config issue somewhere

#

Because this is very possible

twilit light
#

If cloudflare were doing the 503's, it would be a cloudflare error though

abstract olive
#

But I need to narrow it down

#

Can you add an api3 that just points to api? And turn on orange cloud for it?

twilit light
#

This first began with someone DOSing my systems two months ago. Thousands of requests per minute

twilit light
#

Everything is set to grey cloud in the above example ^

abstract olive
#

But you can do it on a per URL level from the DNS section right?

#

Like what does your DNS page look like

twilit light
abstract olive
#

Ya don’t do that

twilit light
abstract olive
#

Go to DNS and toggle it on a route

twilit light
#

Turn on orange cloude?

abstract olive
#

On just that one route

twilit light
#

If cloudflare is disabled it won't send traffic anyways?

#

I'll enable api2 now

abstract olive
#

If you need api and api2

#

Add api3

twilit light
#

I do not need api2, that was the point of making it

#

Enabled.

abstract olive
#

Perf

#

Kk let’s see

twilit light
#

Will check back in an hour, going into a meeting 🙏

abstract olive
#

It looks fine to me BTW

#

CF is pretty instant

twilit light
#

And you're verifying that is indeed going through Cloudflare? I don't know how api2.* could be using the cloudflare orange cloud if the global "advanced actions" of disabling cloudflare is still set to Disabled

twilit light
#

Hey folks, api2 does not have cloudflare working still. Since my global config has cloudflare disabled

abstract olive
#

Ya saw that quite odd :/

#

Do you have another domain you could point there and enable it?