3 months ago
I am a hobby user and have an Ruby/Rails app with a Postgres DB that was ported over from Heroku and had been deploying and running fine for over a year. Besides the new Macbook, there were a few other potentially contributing factors, which are worth a mention. So here is the time line:
Back in July I tried deploying an update from my new Apple M1 running Sequoia and after updating to the latest "railway" in my development environment, I hit a problem where I would get an "Indexing" message and the deploy would hang. There were "deployment incident" messages being posted around that time, so I held off deploying for a few days.
When I re-engaged what I started seeing was an "Indexing" message followed by a timeout. Web searches suggested that the app was too big for a console deploy. Trimming it was going to take time, so I put everything aside.
Two weeks later I got a notice that a new Railway release had gone out. None of my problems were listed, but I redeployed anyway. The timeout was gone and the app appeared to deploy. However the app now gives the error "We're sorry, but something went wrong." and the log shows the following:
2025-09-04 00:22:48 +0000 HTTP parse error, malformed request: #
2025-09-04 00:22:48 +0000 HTTP parse error, malformed request: #This is an app and deploy that had been working for over a year without issue.
The repo is: https://github.com/gltarsa/Motleytones
Is any of this familiar enough to anyone that they could give me some insight into the best next steps for troubleshooting this?
0 Replies
3 months ago
how do you have the port configured on the railway end? also, are you using a reverse proxy?
3 months ago
You ran railway up while linked to your Postgres service instead of your website's service. While this won't hurt the data in the database, it will take the database offline.
I have gone ahead and redeployed your database for you with the correct image, and your website is now back online.
3 months ago
🤔 strange that would result in a puma error and not something within activerecord
3 months ago
It was a 500 error page, which seems completely reasonable given the application couldn't talk to the database.
3 months ago
no totally, but a puma parsing error doesn't make sense when the database connection is done via activerecord and is totally seperate from puma
3 months ago
Hey, I'm no puma expert; all I know is that the database is back online and the website works.
3 months ago
true, I'm just curiously thinking out loud why it would say that
@Brody Thank you, very much. It is great to see this working again. How did you go about redeploying the database to fix this?
3 months ago
Opened the database service -> CMD + K -> Deploy latest commit
3 months ago
!s
Status changed to Solved noahd • 3 months ago