Timeline for Allow non-root process to bind to port 80 and 443?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 23, 2023 at 15:34 | comment | added | Ben Millwood |
I ran something analogous to sudo iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-ports 3000 and found that https requests issued from my Docker containers stopped working, I guess because they were going via the host machine?
|
|
| Oct 21, 2022 at 0:20 | comment | added | Jay Joshi | As soon as I start firewalld service on my machine, the port forwarding stop working. Any suggestion on what might be happening? | |
| Sep 21, 2021 at 2:52 | comment | added | Soheil |
Keep in mind you may need to bind to 0.0.0.0 instead of 127.0.0.1 for external traffic.
|
|
| May 25, 2021 at 9:48 | comment | added | J-Cake | Quick question: I ran the second command a while back, and I'm looking to remove this, as I have written an automatic forwarding server/loadbalancer, and would like to deploy it under port 80. | |
| May 11, 2021 at 8:14 | comment | added | noob | @JasonC I agree! It's more declarative and better supported and AFAIK nginx uses port-forward too. | |
| May 10, 2021 at 21:58 | comment | added | Jason C |
nginx is a great option along these lines, too; easy to set up and very powerful.
|
|
| Jun 27, 2018 at 7:00 | history | answered | noob | CC BY-SA 4.0 |