2 years ago
I have been using railway in the trial period to run a Strapi web server with great success, but after my trial expired and I upgraded, I've begun getting errors from my Strapi deployment. Now when Strapi attempts to start, I get the following error:
> troop-cms@0.1.0 start
> strapi start
[2024-07-02 15:37:31.945] debug: ⛔️ Server wasn't able to start properly.
[2024-07-02 15:37:31.947] error: Connection terminated unexpectedly
Error: Connection terminated unexpectedly
at Connection. (/app/node_modules/pg/lib/client.js:132:73)
at Object.onceWrapper (node:events:631:28)
at Connection.emit (node:events:517:28)
at Connection.emit (node:domain:489:12)
at Socket. (/app/node_modules/pg/lib/connection.js:63:12)
at Socket.emit (node:events:517:28)
at Socket.emit (node:domain:489:12)
at TCP. (node:net:350:12)
as well as
error: read ECONNRESET
Error: read ECONNRESET
at TCP.onStreamRead
When looking up the issue, some people have seen this problem when using a proxy, but obviously I have no control over the Railway proxy.
> ⓘ Deployment information is only viewable by project members and Railway employees.
3 Replies
2 years ago
What is the state of your database deployment? if it doesn't have a deployment you will need to redeploy it from the removed deployments 3-dot menu.
Status changed to Solved Railway • almost 2 years ago
2 years ago
What is the state of your database deployment? if it doesn't have a deployment you will need to redeploy it from the removed deployments 3-dot menu.
Ah, great catch thank you. The database was down, I didn't notice because it didn't have an X like the other deployments. Much appreciated!