502 Bad Gateway - Laravel App

espacio-arq
HOBBY

a month ago

I've deployed my Laravel application, but I haven't been successful. I've configured my port as 8080 in the configuration as suggested in other threads, but this doesn't solve the problem. I've configured everything and put a php artisan migrate in the deploy command, the database seems to connect well, but I don't know why it keeps giving me a 502 error.

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.

Request ID:
EvViGzyhR8WjhxDtCx5-qw

$10 Bounty

9 Replies

a month ago

Check the deployment logs for any errors, and make sure the code is listening on the same port that you configured in the network settings. Do you have example code that reproduces this problem, maybe just the part that listens on the port?


erisa

Check the deployment logs for any errors, and make sure the code is listening on the same port that you configured in the network settings. Do you have example code that reproduces this problem, maybe just the part that listens on the port?

espacio-arq
HOBBY

a month ago

This is HTTP Logs

Attachments


a month ago

Try not to use custom port (8080) because I also use Laravel and the working port is 9000. You can also see and use the port that appears in Deploy Logs.

Attachments


emmakade
FREE

20 days ago

I'm facing the same issue on my newly deployed laravel project to railway, I need help please.


emmakade

I'm facing the same issue on my newly deployed laravel project to railway, I need help please.

emmakade
FREE

20 days ago

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.

Request ID:
31kFY4FTRWCRNSYNYqdHTg


faishal

Try not to use custom port (8080) because I also use Laravel and the working port is 9000. You can also see and use the port that appears in Deploy Logs.

emmakade
FREE

20 days ago

can you help to get this error 502 fixed?


emmakade
FREE

20 days ago

73c55a9b-d265-4394-a004-028c92e092e2


emmakade

73c55a9b-d265-4394-a004-028c92e092e2

FYI the default port is 8000. If this still doesn't work please send the deployment logs.


loudbook

FYI the default port is 8000. If this still doesn't work please send the deployment logs.

emmakade
FREE

20 days ago

Starting Container

Jun 14 13:19:58

Jun 14 13:19:58

INFO Caching framework bootstrap, configuration, and metadata.

Jun 14 13:19:58

Jun 14 13:19:58

config ......................................................... 9.90ms DONE

Jun 14 13:19:58

events ......................................................... 1.36ms DONE

Jun 14 13:19:58

routes ........................................................ 11.79ms DONE

Jun 14 13:19:58

views ......................................................... 22.43ms DONE

Jun 14 13:19:58

Jun 14 13:19:58

Jun 14 13:19:58

INFO Configuration cached successfully.

Jun 14 13:19:58

Jun 14 13:19:58

Jun 14 13:19:58

INFO Routes cached successfully.

Jun 14 13:19:58

Jun 14 13:19:58

Jun 14 13:19:58

Jun 14 13:19:58

INFO Blade templates cached successfully.

Jun 14 13:19:58

Jun 14 13:19:58

Jun 14 13:19:58

INFO Nothing to migrate.

Jun 14 13:19:58

Jun 14 13:19:59

Jun 14 13:19:59

INFO Server running on [http://0.0.0.0:8080].

Jun 14 13:19:59

Jun 14 13:19:59

Press Ctrl+C to stop the server


502 Bad Gateway - Laravel App - Railway Help Station