I am also having problems after deploying a small code change to a previously working app. No changes to deployment configuration. The app was there before the deployment and now the DNS does not resolve.
All other apps in my org are working correctly. Just the one that I redeployed is unreachable.
I have tried multiple redeploys, scaling to 0 and and then scaling back to 1 instance. Nothing is working. The logs show the app startup and listening on the correct port. DNS and certs are all in order. No request resolves to the service though.
I have [[services]] section but haven’t allocated an IP address. Thought I wouldn’t need one for hobby tier app? I followed the instructions in the example guides and as far as I know, it should work.
Huh that fixed it, thanks a lot! Should probably add a debugging section about this though in the Nodejs guides. Hopefully @macdrich you got your problem also sorted out.
Hey, any chance you could share exactly what you did to resolve this? I’m having the exact same issue you describe and can’t get it sorted. Seems like it should just work and it’s weird that the basic usage example doesn’t work out of the box.
i am running into this issue, ive deployed my site through fly.io and it said everything worked however when I open the site it says the server cannot be found, any fix?