What do your memory metrics look like? might be an out of memory issue since trial plan users can only use up to 500MB.

Yea it seems to spike alot during the deployment, but I should be able to deploy a basic express app for the free tier I thought? :)

Can you attach a screenshot please.

Can you attach a screenshot please.

It doesn't let me attach files, here's two image links:

https://gyazo.com/307c3d62bb9a52a5abda9f118a1a8f0d

https://gyazo.com/52f6db60bbbe1e46f001467b20e8a14e

Thanks, let me know if you continue to experience errors after upgrading to the Hobby plan and redeploying.

But shouldn't the solution be to not have to upgrade to hoppy plan? My application is not allocating this memory AFAIK?

It could be so we need to rule that out as an issue before proceeding.

Hi, It still doesn't seem to work. Even after I upgraded to Hobby plan.

Have you since re-deployed?

Yes I have. The issue now is that I get "Application failed to respond" and all HTTP requests return 503 service unavailabe. Both via my custom domain as well as the railway-generated one.

The logs looks fine... Latest log is:

node build/server.js

Jul 14 00:18:03

Server is running on port 5771.

Curl:ing gives me:

HTTP/2 502

content-type: application/json

server: railway-edge

x-railway-fallback: true

x-request-id: z6bkqO7KS0Gnfk2qvt13QQ_2823689937

content-length: 120

date: Sat, 13 Jul 2024 22:49:44 GMT

{"status":"error","code":502,"message":"Application failed to respond","request_id":"z6bkqO7KS0Gnfk2qvt13QQ_2823689937"}

Logs when switching to new builder/deploy:

Pushed us-west1.registry.rlwy.net/5eaa399f-d6aa-4e34-af22-c171ec7332e6/cache@sha256:71c8b38b957b999df9bf767dd30758891287260cbea648d786762306e5b90db4

Jul 14 00:54:10

Pushed us-west1.registry.rlwy.net/5eaa399f-d6aa-4e34-af22-c171ec7332e6/cache@sha256:08c04951b02cf4d93a32989d1e6793a97f534b41defa480d477a8b07181aa99f

Jul 14 00:54:11

Pushed us-west1.registry.rlwy.net/5eaa399f-d6aa-4e34-af22-c171ec7332e6/cache@sha256:9663cb0f3562f1757a6d704f53d4ae517bc062c62cdd67eee5ba3744c1864407

Jul 14 00:54:11

Pushing image to us-west1.registry.rlwy.net/5eaa399f-d6aa-4e34-af22-c171ec7332e6:12f3c8b7-950f-4bbe-9efa-20ca7c8070e4

Jul 14 00:54:19

container event container died

Jul 14 00:54:19

Pushed us-west1.registry.rlwy.net/5eaa399f-d6aa-4e34-af22-c171ec7332e6@sha256:8cbbfedf75ba2ecce25a40bc83b0ca28d953d780844eb7a7b1d37691a549e503

Jul 14 00:55:27

Stopping Container

Jul 14 00:55:50

Starting Container

Jul 14 00:55:52

yarn run v1.22.22

Jul 14 00:55:52

$ node build/server.js

Jul 14 00:55:52

Server is running on port 8080.

Is your app also listening on the host 0.0.0.0 ?

That did the trick! Thank you for the help @brody :)