Hey there! We've found the following might help you get unblocked faster:

• 🧵 Flask/Gunicorn on Railway: JSON response truncation (Unterminated string errors in production)

• 🧵 Worker Timeout, SIGKILL, and Database Connectivity Issues in Railway Deployment

• 🧵 Can't connect from server on pythonanywhere but can do same from local

If you find the answer from one of these, please let us know by solving the thread!

Please reply fast as this is a critical issue

I am confused as you are on the legacy hosts which have no one on the instance. Can you describe more about your issue?

https://octet.design/colors/mood-based/sophisticated-elegant/
Click on this url . this url is giving timeout error .
Now the frontend is on vercel and backend app is on railway. so every api is taking more than 30 sec time to respond to the frontend application .
Previously it was on railway metal server then one of your support team member told to switch to the legacy server and after it starts working fine.
Now the same issues of long api response time are started coming on legacy server .
I hope you understand and provide me a solution.

please reply fast

What's the specific network error that you are seeing?

(I need it for the platform team.)

504

Look this error I am getting

Okay, try now, I think I see the issue.

Not working

Check this url : https://octet.design/colors/industry-specific/construction/

I don't see this URL on your dahsboard.

and the API you are reporting to not be availible is returning: https://api.addding.com/

Still The reponse time is taking too much time like more than 15 secounds

I wouldn't know what else to do here- the host it's self is performing fine. You will need to resolve the issue with your code.

https://api.addding.com/colorpalette/categories?collection=accessibility-focused --- can you check this url ?
It is from the host and talking long time to load the response . Is it a host issue or Code issue ?

It loaded in like 250ms for me... which is... weird.

Look, I am not doubting that you are facing this issue, however, it's hard to trace down, so I will need logs and timestamps more so than just screenshots that load fine on my machine.

https://api.addding.com/colorpalette/categories?collection=brand-specific

Instant

WARNING: database "railway" has a collation version mismatch

DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.

HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE railway REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.

is this a major issue ?

That would affect performance sometimes

How to resolve it ?

can you check this logs as you asked ?

are you there ?

?????

Are you there ?

I have provided you with the logs . can you check ?

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

Forgive me, I logged off at 4 AM my time, I have escalated this to the platform team.

How Much time Do I have to wait ? I am Frustated with your service because its not the issue from my side and i am paying for the vercel bill due to timeout issues.

Are you still getting timeouts?

We just observed that we have fixed most if not all stalls on writes, if not that, then it's a different issue.

If you need to avoid a "network" issue, you can deploy the front-end and connect via the private network.

Can you this logs I am asking you this issue .

Are you there ?

Can you provide me a guide to this ?

Look I Have deployed the frontend : https://palettes-staging-production.up.railway.app/colors/city-inspired/
Go to any page and you will be able to see that response is coming in 40 to 50 secounds . Now please check this

??

Your plan SLO states that you are entitled to response time responses within a 24 hour period. I understand that you may be frustrated, but please keep in mind that there is someone across from this screen. We are trying to engage with you to solve this issue.

When hitting that link, I am getting: around 2 to 3 seconds. Not 40. So I am a bit confused on how that you are getting that figure.

Ok Here I am giving a step by step process to see the API timings going 40 seconds and above.

Backend Service: addding-django
Go to Octet-projects and open addding-django service then the latest deployment and in that open Http logs. Now keep watching the logs

Now open a other Railway window for Frontend Project
Frontend Service: Palettes-staging
Go to triumphant-radiance and open Palettes-staging service then the latest deployment and in that open Http logs. Now keep watching the logs

After this two steps you have to visit this URL https://palettes-staging-production.up.railway.app/colors/city-inspired/hong-kong-skyline/ and try to use this application and now check the logs for addding-django and Palettes-staging and you will see that APIs are calling to the addding-django service and the response time are more than 40 seconds

Hi there,

To resolve this issue, run ALTER DATABASE railway REFRESH COLLATION VERSION; from your SQL client when connected the railway database.

Please give that a go and let us know if you see any improvement.

Regards,
Christian

We have resolved this databse issue and still the error is there. Now this issue is here from very long time and I am not getting a proper solution from Your side and my costs are going very high like 100 dollars a weak.

Have you checked this ?

✅ The ticket Database Performance Issue has been marked as completed.

We have, we found that there is a possible issue with the network on your workload.

So How to reolve it ?

If the issue you are experiencing is still present, then any remaining issues would be on your side, either at the application level, due to incorrect configurations or setup, or issues with your local network. I have gone through all the links and reproduction steps you gave Angelo, and nothing is timing out for me or took anywhere near 40 seconds. I'm sorry, but we are not able to help further, as everything is operating correctly on our side.

I’m extremely disappointed with this response. If you are unwilling to acknowledge or assist with the ongoing issues I’ve been facing, then there’s no point in continuing with your platform. I am moving all of my services to AWS directly and cancelling my plan with you effective immediately. Your lack of support and accountability has made it clear that this is not a reliable long-term solution.