I can see why services.port
s / services.internal_port
s aren’t accessible when connecting to FLY_PUBLIC_IP
directly…
Though, one must be able to (I haven’t used it in a long time myself, so it may have stopped working) connect to FLY_PUBLIC_IP
over experimental.allowed_public_ports
(ref, via).
Note, connecting straight to FLY_PUBLIC_IP
may bypass (I am not sure) Fly Edge (and its handlers, DDoS protection, etc).