jimmy
1
blanst
2
You can specify external ports in the services.ports section.
You’ll want to modify your config like this:
[[services]]
internal_port = 8080
protocol = "tcp"
[[services.ports]]
handlers = ["tcp"]
port = "22"
This config says accept TCP traffic at the fly.io edge on port 22 and send it to my VM at port 8080.
jerome
3
Unfortunately we do not currently allow exposing port 22. There’s a bit of complexity there with how our networking is setup.
We do plan on letting people bind to any port sooner than later though!
1 Like
jimmy
4
That’s a shame but makes sense - thanks.
kurt
5
I’ve been using 10022 for my SSH based apps. 
blanst
6
Yikes! I’d been up and down the docs recently and figured I’d notice something this big. Any other ports to watch out for?
kurt
7
These TCP ports work today:
25, 53, 80, 443, 5000, 8443, 25565, and ports 10000 - 10100
This detail is a little buried in our docs, though, we should make a bigger deal of it: Fly Launch configuration (fly.toml) · Fly Docs
deepakd
8
@jerome Have you added support to bind any port?
jerome
9
1 Like