2 months ago
Hello,
My architecture is made of one dockerized angular frontend, one dockerized nest.js backend and one postgre sql database. de62241c-d9ce-4b1c-b0f9-55d63dd34aa1
They are all interconnected using internal / private network, and all on the EU West region.
For any of my app requests (angular calling api calling db), the response time for the same exact request can vary from 60ms to more than 1 minute. It seems to be random and makes me unable to try correctly my application before validating poc and continue with Railway as my infrastructure provider.
Is there anything I can do or try to solve this ?
The only thing I can see inside my logs are these alerts from the nginx / angular web app (I removed any sensitive data) : [warn] 8#8: *242 upstream server temporarily disabled while connecting to upstream, client: , server: , request: "GET /api/users/me HTTP/1.1", upstream: "", host: "", referrer: ""
[error] 8#8: *242 upstream timed out (110: Operation timed out) while connecting to upstream, client: , server: , request: "GET /api/users/me HTTP/1.1", upstream: "", host: "", referrer: ""
About cpu/memory limits, I am still far from the free tier limit ...
Thank you,
Antoine
Pinned Solution
2 months ago
I am closing this issue as it appears I have solved the problem.
I found out that discussing between API and databases caused no problems, and I always had really short response times.
So the problem was sitting between angular frontend and api backend. It turned out I was not replacing correctly my proxy_pass variable for /api calls in nginx config, so variable was set as undefined, which might caused problems when resolving ipv4/ipv6 (I didn't do any further checks as I analized myself directly on my computer, but it seems to have solved the problem).
I'm leaving this here as it might help someone else someday.
Regards,
Antoine
2 Replies
2 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
Status changed to Solved antoineheseque • 2 months ago
2 months ago
I am closing this issue as it appears I have solved the problem.
I found out that discussing between API and databases caused no problems, and I always had really short response times.
So the problem was sitting between angular frontend and api backend. It turned out I was not replacing correctly my proxy_pass variable for /api calls in nginx config, so variable was set as undefined, which might caused problems when resolving ipv4/ipv6 (I didn't do any further checks as I analized myself directly on my computer, but it seems to have solved the problem).
I'm leaving this here as it might help someone else someday.
Regards,
Antoine
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Solved ray-chen • 2 months ago