Dns problem
artembavykin
HOBBYOP

8 days ago

After redeploying, the service shows as running in logs but the public domain is not resolving (DNS failure). it stopped working properly when I switched to the hobby plan

$10 Bounty

5 Replies

Status changed to Awaiting Railway Response Railway • 8 days ago

xmrafonso
FREETop 5% Contributor

8 days ago

Hey,

I assume you didn't do any changes in ports or anything like that?

xmrafonso

Hey,I assume you didn't do any changes in ports or anything like that?

artembavykin
HOBBYOP

8 days ago

So switching to a hobby plan could change the port?

artembavykin

So switching to a hobby plan could change the port?

xmrafonso
FREETop 5% Contributor

8 days ago

I don't think so, but I'd simply go ahead and double check everything including ports, configs, etc.

artembavykin
HOBBYOP

8 days ago

I found a pattern, I generated a new public HTTP, and everything worked. But the next time I deployed, it stopped working again, and now everything is working again

artembavykin

I found a pattern, I generated a new public HTTP, and everything worked. But the next time I deployed, it stopped working again, and now everything is working again

xmrafonso
FREETop 5% Contributor

8 days ago

So it was a problem regarding Port/HTTP? I guess glad it worked lol. Not sure if I helped? but yeah

Loading...