Custom Domain
joselvelez
PROOP

a year ago

I setup a custom domain (a subdomain) and it does not seem to be working.

I get this:

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:

mvb6BzCNSRqgYiqwCx5-qw

Solved$10 Bounty

5 Replies

a year ago

Have you checked your application's logs? And is your custom domain pointed to the correct port?


joselvelez
PROOP

a year ago

Build log is successful. Deploy log is successful. Http log is showing 502.

What do you mean if my custom domain is pointed to the correct path?


joselvelez

Build log is successful. Deploy log is successful. Http log is showing 502\. What do you mean if my custom domain is pointed to the correct path?

a year ago

502 means bad gateway/gateway timeout

Please ensure you have the correct port set for your custom domain under the (public) networking section of your service's settings

Attachments


joselvelez
PROOP

a year ago

The railway settings automatically chose port 8080.

I see this: A port was detected by Railway magic 8080(node)

Should I change it to 80?


joselvelez
PROOP

a year ago

Fixed. It was an issue with docusaurus. I had to specify the port in the package.json file and modify the start script so that the production build was running on Railway. It was running the development build.

"start": "npm run build && npx serve build -l ${PORT:-8080}",

Status changed to Open uxuz about 1 year ago


Status changed to Solved uxuz about 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...