Setting up load balancer in cloudflare (from the guide) and us-east service doesn't get health check
I'm using this guide to set up load balancer with proximity steering on my project. I set up 2 endpoints for 2 separate copies of my backend service, one on us-east4 and the other on us-west1. Both have a healthcheck endpoint.
The west service gets the healthcheck as expected, the east service doesn't get the healthcheck, but it gets other requests. Also, I enabled session affinity on load balancer for websockets, and they don't work.
If I take down the us-east4 service, and route everything to us-west1, the websockets work just fine.
8 Replies
Project ID:
bffee644-ec55-4122-9e19-fee98c401647bffee644-ec55-4122-9e19-fee98c401647
Sorry but this is something you would need to contact Cloudflare's support for.
I was curious if this was something that I missed in the docs, or they're not updated for this usecase
we don't cover session affinity as that is something you'd want to read up on Cloudflare's docs for.
right, that's in the docs. I was interested in the sticky sessions and the multi region replicas. are you at liberty to disclose if these are features being worked on or on the roadmap at railway?
it's something we want to do, but we are not working on it at this time
thank you