The app only has an IPv6 address for the moment, I will add a v4 address when I’m ready to launch. I have an SSL certificate issued for the HTTP transport.
I am experiencing an error similar to the one described in this thread:
Any connection to the app over port 80 or 443 gets reset on the other end.
My app is fine: when I SSH into the VM I can reach the internal port. The Dashboard reports all the health checks as passing, however, my app logs all requests, and I actually don’t see any requests for the /check URL in the logs, so I am not sure if that is working properly. Redeploying the app hasn’t helped, but I haven’t tried destroying and recreating yet.
AFAIK everything on my side is fine, so at this point my assumption is that it’s a problem with Fly. Can someone else sense check this?
I added the [services] section to the TOML file and the app became reachable. When I then removed the [http_services] section it stopped working, so it seems like it needs both sections to be present to work. That doesn’t seem match up to either @charsleysa’s advice or @kurt’s (and the documentation).
Anyway, my app seems to be working now but I wanted to flag the mismatch between the documentation and the observed behaviour.
@MatthewIngwersen by the way, my app is a new(ish) one that I only created a couple of weeks ago, using fly launch. I wasn’t aware that using fly launch would create an app on a “legacy” platform - that’s not in the documentation IIRC.
The http_servicedocs have been updated to note that it’s for Apps v2 only, and flyctl (with v0.0.500, released today) will now emit a warning if http_service is used for a Nomad app. (We might change this to an error in the future, but for now we want to be careful not to break anybody’s pipelines.)
Sorry about the fly launch confusion! New users get Apps v2 by default now, but this change is very recent and happened after you deployed your app. If you want to opt your existing organization(s) into Apps v2-by-default, you can run fly orgs apps-v2 default-on <org-slug>. You can also try it out for a single app by using --machines with fly apps create or --force-machines with fly launch and fly deploy.