2 years ago
Hi,
I have verfied my code its okay. Its running OK. However I am getting a 502 error when trying to access it.
19 Replies
2 years ago
same here. my services are in SouthEast Asia and getting 502 error
2 years ago
same here
2 years ago
I think we're having the same networking problem here on the Southeast Asia region. Just with the service we redeployed to this morning. Requests that don't hit the database seem to be okay (static files), so I suspect there's a networking problem between our application container and Postgres.
2 years ago
Can y'all link to the service you are having issues with?
2 years ago
I think something is wrong with postgres
mongodb has no problem
fba556c2-09ab-4c36-a616-d5da0d54f6d6/service/a1f2748c-b3dd-4583-b150-e59142f62b91?environmentId=2c15a52c-7afd-4f3c-85fe-6525a58626d7
2 years ago
/project/b022b1af-4898-4f67-ae21-c86111a2e4b7/service/35f8e4c4-c40d-4bb3-ae98-f7b0e41c6999?environmentId=421d5a68-925f-4f65-9ff0-9b614e719486
2 years ago
It started working on my dev env when I migrated my dev postgres to US West
2 years ago
Please provide direct links to the service in question, this can be copied from your browser's omni bar while you have the service in question open.
brody
Please provide direct links to the service in question, this can be copied from your browser's omni bar while you have the service in question open.
2 years ago
fba556c2-09ab-4c36-a616-d5da0d54f6d6/service/a1f2748c-b3dd-4583-b150-e59142f62b91?environmentId=2c15a52c-7afd-4f3c-85fe-6525a58626d7
brody
Please provide direct links to the service in question, this can be copied from your browser's omni bar while you have the service in question open.
2 years ago
Mine was originally returning triggering 502 for all database-related requests, and eventually changed to timing out and hitting Cloudflare's 100s response time limit instead.
2 years ago
Postgres, backend and front end are all in Southeast Asia, and having 502 gateway error on cloudflare
2 years ago
Looks like an incident has now been logged for this: https://railway.instatus.com/cma4wxa8j00047yj7joi492tw
2 years ago
I found a workaround in my deployment. If i use the string stored in DATABASE_PUBLIC_URL instead of the string stored in DATABASE_URL as my database connection string for my frontend, my app loads and works fine.
Public networking appears to be fine for the backend on mine, the problem appears to be with the internal networking between services.
EDIT: I take that back. Did another build and broke it :(
2 years ago
Please follow along with the incident linked above, we are actively working on a fix.
2 years ago
Hello All,
Update here, we have resolved the incident!
Again, very sorry for the inconvenience caused.
2 years ago
!s
Status changed to Solved brody • over 1 year ago


