Error while visiting my API
tobiblaster00912
TRIALOP

2 years ago

Im Hosting a Discord and API to see some stats for the Minecraft Server 2b2t. The Discord Bot is online and working, the API is working too, same for the free Domain. But when i use my custom domain, 2b2queue.site, its not working. I don't know whats wrong and i tried looking on Namecheap (where i bought the domain) and it is set up correctly. Would be nice if someone could help me out (Free Domain: 2b2queue2-production.up.railway.app | Paid domain: 2b2queue.site )

Solved

16 Replies

brody
EMPLOYEE

2 years ago

Please attach a screenshot of your public networking.

tobiblaster00912
TRIALOP

2 years ago

Im pretty new to this, what exactly do you mean?

brody
EMPLOYEE

2 years ago

The public networking section of the Railway service.

tobiblaster00912
TRIALOP

2 years ago

Here it is

brody
EMPLOYEE

2 years ago

Have you tried redeploying?

tobiblaster00912
TRIALOP

2 years ago

I tried restarting but it didn't work

brody
EMPLOYEE

2 years ago

Please show me the DNS settings in namecheap.

tobiblaster00912
TRIALOP

2 years ago

Here (Redeploying didn't work too btw)

tobiblaster00912
TRIALOP

2 years ago

Do you have any idea how to fix?

brody
EMPLOYEE

2 years ago

Looks like everything is correct as far as I can tell.

brody
EMPLOYEE

2 years ago

This thread has been escalated to the Railway team.

Status changed to Awaiting Railway Response brody • over 1 year ago

christian
EMPLOYEE

2 years ago

The DNS Record Type is dependent on your DNS provider. For Namecheap, you will need to set an ALIAS record instead of a CNAME. See the docs.

Status changed to Awaiting User Response Railway • over 1 year ago

tobiblaster00912
TRIALOP

2 years ago

The time to live is limited to 5 mins now but is this right?

Status changed to Awaiting Railway Response Railway • over 1 year ago

tobiblaster00912
TRIALOP

2 years ago

And it still wont work

christian
EMPLOYEE

2 years ago

Thank you. We'll investigate.

Status changed to Awaiting User Response Railway • over 1 year ago

christian
EMPLOYEE

2 years ago

This is likely to be an edge case where your custom domain is on the old proxy. Please delete your domain in Railway, make sure the New Proxy is enabled, and re-add it.

tobiblaster00912
TRIALOP

2 years ago

Thank you, it worked. It didn't told me to set the Port when i added it the first time. After deleting it, i could set my port and its workind now :D

Status changed to Awaiting Railway Response Railway • over 1 year ago

Status changed to Solved brody • over 1 year ago

Loading...