16 days ago
I know that Railway has Fastly in front of all of your services, but I also see that it can detect when Cloudflare's Proxy services is enabled on domains that you point to these services.
What happens in this case? Is Fastly bypassed, or does it become a chain of Client -> CF -> Fastly -> Service?
If the latter, would the general recommendation be to disable CF proxy?
Cheers!
17 Replies
16 days ago
Leave Cloudflare enabled, Cloudflare still provides you with the tuneable WAF functionality that Fastly doesn't.
16 days ago
Thanks for the reply, I suppose WAF makes sense to have. What does the chain look like in that case, is it still CF -> Fastly -> RW?
16 days ago
Exactly what you put in your root message.
16 days ago
Client -> CF -> Fastly -> Railway Proxy -> Service - if you want to get technical
16 days ago
And there's no way to remove Fastly from the picture when using CF?
16 days ago
I'm just worried about there being two points of failure, and extra hops.
16 days ago
There is no way for the user to disable Fastly, but two points of failure is a valid concern, and a very real problem, given that Fastly is currently withdrawn from our edge due to issues they experienced.
Though the extra hops concern is not an issue in practice, Fastly holds connections open to our edge, so there is no extra overhead from having to establish a connection per request.
15 days ago
I meant more from the CF->Fastly hop, but tbh we're not seeing too much of a latency increase on our dev setup at the moment, so we'll see how it goes.
Also wdym fastly is withdrawn? 🥺 Is my CDN cache kaput?
15 days ago
Fastly runs the CDN, so without Fastly the CDN functionality doesn't work.
15 days ago
Just to clarify - will requests hit Fastly or not?
14 days ago
Not at this time, Fastly is withdrawn.
14 days ago
Hmm, okay, was there an announcement or something that I missed? Had a search but can't find. Also is there any estimation on when it might resume? It's just that we're planning a migration in the coming weeks and I'd like to be prepared for any changes that may impact our user experience.
14 days ago
You didn't miss anything, and I am unable to provide an ETA. Sorry.
14 days ago
No worries, I appreciate your help!
14 days ago
Though, just out of concern for other users, should that not be communicated? We're okay because we do have CF providing us with a CDN, but if that were not the case post-migration, we would have been killed by egress fees - we have thousands of static assets (x1000s of users).
I agree, it would be great to receive notifications regarding planned Fastly outages. This would allow us to take measures to switch over to Cloudflare. After all, Fastly outages on your end occur constantly literally every week.
12 days ago
I've been experimenting with using Cloudflare Tunnels to skip the Fastly proxy and use only CF, and it seems to work pretty well. I think it's worth a try if you wanna prevent that double-proxy scenario.