Zeronet: Setting a port number below 1024

[styromaniac]

It prevents ZeroNet from working.

You have to change the port number under ZeroNet.conf back to one that's above 1023 to make ZeroNet work again.

[HelloZeroNet]

What OS are you using?

Do you see any error on the startup?

[styromaniac]

Both Linux and Android, Py3, latest revision.

[JuanitoAlimana]

[e-mail]
Sent from iPhone

El 20/02/2020, a las 9:48 a. m., [e-mail] escribió:


It prevents ZeroNet from working.

For instance, 8080, 8081 or the like is fine, but 443, 80 and 22 are not. Three d gifts and below prevent ZeroNet working. You have to change the port number under ZeroNet.conf back to a four digits+ port number to make ZeroNet work again.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[imachug]

Let me make a guess: port 1023 doesn't work while 1024 does. The reason is that Linux-like OSes disallow non-root to use ports below 1024. If you want to bind to those ports, check this SO thread.

[styromaniac]

Let me make a guess: port 1023 doesn't work while 1024 does. The reason is that Linux-like OSes disallow non-root to use ports below 1024. If you want to bind to those ports, check this SO thread.

ZeroNet needs to tell the user that those numbers below 1024 are invalid.

You're exactly right. I tested 1024 and 1023. The results are what you expected.

[filips123]

ZeroNet needs to tell the user that those numbers below 1024 are invalid.

They are not invalid. It's just OS that prevents non-root programs to use them.

If you run ZeroNet as root (or use options that @imachug linked), ZeroNet should work with any port.

[styromaniac]

ZeroNet needs to tell the user that those numbers below 1024 are invalid.

They are not invalid. It's just OS that prevents non-root programs to use them.

If you run ZeroNet as root (or use options that @imachug linked), ZeroNet should work with any port.

Then a warning and recommendation to avoid the issue.