IP not allocated when launching app

[andig]

@MatthewIngwersen Thank you! Reason for the setup is/was, that I wasn’t aware that Fly can handle Letsencrypt certificates, hence I had this built into the Go application.

Perhaps it would be helpful if fly launch printed a bit of explanatory text before the question?

I think so, yes (also mention UDP). In this specific case though, the question isn’t even asked, probably since Fly determined it could not allocate a shared address. It would be good if fly launch could explain what it’s doing and why it isn’t trying to allocate a shared IPv4 address.

Another oddity regarding services (and off topic): in the process of moving to Fly-managed Letsencrypt certificates I’m stuck with a strange error in another case. It would be great if you could also take a look there. I’m seeing this with two apps I’d like to convert and CLI doesn’t give any indication what is really going on:

You have a service exposing port 443 but no "tls" handler on it, either remove the service or add the "tls" handler on it

Service definition is: [[services]] internal_port = 8000 protocol = "tcp" [[services.ports]] handlers = ["http"] port = 80 [[services.ports]] handlers = ["tls", "http"] port = 443 [[services]] internal_port = 8080 protocol = "tcp" [[services.ports]] handlers = ["tls"] port = 8080 [services.concurrency] hard_limit = 500 soft_limit = 200 It seems this has all required TLS handlers, yet error message is still Status is You have a service expo…