The root :80 is working fine and you can see it running at 159.223.204.176
The issue I’m having is that when I point an A or AAAA record to the droplet it just doesn’t find the server. The ping for the on_demand_tls is also not firing.
You can see the records are set correctly here: dig test.justcors.com AAAA dig test2.justcors.com A
4. Error messages and/or full log output:
curl: (6) Could not resolve host: test.justcors.com
My log file specified in the Caddyfile is empty/doesn’t exist. There are no noticeable errors.
5. What I already tried:
I have tried quite a few variations on of the Caddyfile the only thing that seems to work is this set up the root :80 to make sure that it’s actually being used (which it seems it is).
That means your DNS records aren’t set; or at least that your DNS resolver isn’t able to find the domain’s A/AAAA records. Please be sure your DNS is set up properly.
I appreciate the help. The DNS records are set up correctly I’ve added IPv4 for http://test.justcors.com and changed the Caddy file to not do the tls handshake and it works fine (but is insecure, I’m working on it). Now I’ve readied the tls ask for https://andathird.justcors.com and it’s failing.
Hmmm, I see that Heroku is returning 301s instead of 200s for some obscure reason. I think if I can figure that out I’ll be gravy. Thanks for the help!
That’s kind of my fault, I didn’t know anyone really used that image – or even can find it. The DO vendor portal makes updating images painfully manual and tedious, even though @Mohammed90 has done an excellent job of automating it, the submission process is still manual and requires a review, and it’s really flaky.
So I might just remove it from the DO marketplace.
I don’t think that would be a heroku quirk, that sounds like your app is triggering the redirect. It would depend on the server/framework you’re running on there.