Attempting to create CNAME to link subdomain to Fly deployment

Hello, and thanks for the help in advance! I’m trying to quickly test using a custom subdomain, e.g.,, and linking it to my deployment, e.g., In my fly.toml I’ve set [[services.ports]] handlers to http, so an https redirect shouldn’t be required. In GoDaddy (where I own I’ve set a DNS CNAME record for Name: “tasks” with Value: “”. I can validate that the CNAME is set by running dig which shows a CNAME record pointing to

With the above, trying to visit in my browser returns a “ERR_CONNECTION_RESET” error. Am I missing a crucial step to get this subdomain working?

1 Like


The first thing to check is that your app works at all, to rule out any issues with that (before looking at the custom domain). So load and check that responds.

If so, then it sounds like Fly is simply not aware of your custom domain being pointed at that. And as such, when a request for arrives at Fly’s edge, it does not know where to route that (which app to send it on to). And hence you get an error.

You need to tell Fly about the existence of your custom domain or send a Host header. That is indeed the crucial step you reference. Generally telling Fly about the custom domain is the easier option (as sending a custom Host header involves using a proxy like a CDN). Take a look at this section, scroll down, and follow the suggested commands:

1 Like

Thank you so much for your response @greg! I can confirm that works as expected.

I was still a bit stumped as I had seen those docs before, but I didn’t realize I needed to go through with the cert process listed here. Thank you for pointing me there! Everything is working as expected now.


Thanks, I also read the docs as saying the certs step applied only to the A record approach and not the CNAME approach

1 Like