2 years ago
hey ,
when using the static ip with my backend
any connection with r2 throws time out error
(
connect ETIMEDOUT 104.xxx:443","stack":"Error: connect ETIMEDOUT 104.xxxx.90:443\n at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)
)
- working fine in local
- working fine when static ip is disabled
8 Replies
2 years ago
edit : this happens with any fetch request to other service from my backend !
R2 not working
Stripe not working
2 years ago
If I understand you correctly
backend: express
frontend: nextjs
When doing any fetch request from my express to my frontend (which is in the same service), the request goes normally.
However, any third-party request from my Express app when static IP is enabled throws a timeout error.
2 years ago
I'm having similar issues with my apps unable to connect to MongoDB when static IP's are enabled. Works fine with Static IP's disabled.
2 years ago
Hello! There was a bug that affected containers on certain host machines on our side. I've just implemented a patch - could you confirm this is working for you now?
2 years ago
now its not working at all
it goes back to the prev error of Application failed to respond
2 years ago
Please try re-deploying your service. The host machine you just got placed on was not yet up to date with our latest build, apologies.
Status changed to Solved Railway • almost 2 years ago
2 years ago
working fine now !