a year ago
I have been on this for hours, someone please help, this is urgent.. switched to port 8080 and didn't work still.
Application failed to respond
This error appears to be caused by the application.
If this is your project, check out your deploy logs to see what went wrong. Refer to our docs on Fixing Common Errors for help, or reach out over our Help Station.
If you are a visitor, please contact the application owner or try again later.
Project ID: 505d606b-64b3-4071-8bb0-1ca8767ee31c
43 Replies
a year ago
Hey! Did u try following our guide on how to deploy a laravel app?
https://docs.railway.com/guides/laravel
a year ago
There's even a 1-click-deploy template that you can use as a base for your app!
Well i deployed it manually by choosing the project from github and including all the necessary ENVs .The deployment is successful but i get 502 error
a year ago
Are you sure that your app listens on port 8080?
a year ago
if you notice the deploy status it says COMPLETED meaning nothing is actually running
a year ago
Is your startup command right? Is your application correct? It’s not a Railway issue as is
a year ago
Containerized?
a year ago
The console suggests it’s literally not running, so I would expect a startup command issue
a year ago
I also have no idea how Laravel works but I assume it’s not static
a year ago
I would recommend creating a default laravel template and then copy over some values. That's what I did to make my Mongo app work with my custom image.
i had a custom dockerfile, had to get rid of it in production… now i'm using railpack builder
a year ago
No idea what railpack builder is
a year ago
But that's definitly an issue with your app now
a year ago
railpack is railways new builder
a year ago
and yes, it’s a code issue at this point
a year ago
more robust logging will help you diagnose the issue
a year ago
😂 Literally started using Railway yesterday, cool
a year ago
No rust?!?!?

a year ago

a year ago
Hey I know Docker 😭
a year ago
I'm going to stick to my Dockerfiles
a year ago
did you just make this lol
a year ago
yes
a year ago
is it good?
a year ago
yes
a year ago
even better, then my meme helped you understand what railpack does
a year ago
unfortunately.
Working now but a new error again :
Mixed Content: The page at 'https://laravel-staging-production.up.railway.app/login' was loaded over HTTPS, but requested an insecure stylesheet 'http://*laravel-staging-production.up.railway.app/build/assets/app-B44XnbEb.css'. This request has been blocked; the content must be served over HTTPS.
Sorry guys… I am migrating from cloudways to railway.. i didn't face any of these with cloudways
a year ago
That's another code issue. You will need to Google that for yourself
a year ago
I'm no laravel dev but after a quick google session you might want to take a look at the URL::forceScheme('https'); function

