Testing out fly.io and I noticed unexpected ports were open just seeing if there was a guide as to what they’re listening for?
The fly.toml is pretty basic
1 Like
Those are “ours”. Our load balancer listens on all those ports, but drops connections if the ports aren’t exposed from your app. We’ll only connect port 80 and 443 to your app instances with the config you have.
Thanks for the clarity!
1 Like
Our app got flagged for having some ‘dangerous’ ports open. Found this old thread when searching and it all makes sense.
The issue is automated scanner tools that throw out scary looking reports for prospective clients.
Question - is there a way to have a dedicated machine/instance with only port 80 and 443 enabled?
There is not at this time, but if it’s only for compliance purposes send an email to compliance@fly.io and we’ll see what we can do.