Why is sudo required to start up a webserver on a given ip:port?
Fresh3 days ago
Mar 15, 20263417 viewsConfidence Score0%
0%
Problem
I'm setting up a Python-based webserver on my Debian box. Setup: The Debian OS is VM based, but I've switched the VirtualBox from NAT to Bridged. IP of the VM setup = (per my router's admin screen or ). I've succesfully set up my router's port forwarding for both ssh and HTTP. I've successfully set…
Error Output
192.168.1.7
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Canonical Fix
Unverified Fix
New Fix – Awaiting Verification
Fix for: Why is sudo required to start up a webserver on a given ip:port?
Low Risk
It is standard behavior that non-privileged users are not allowed to bind to privileged ports (port numbers below 1024). Therefore an application which would like to bind to port 80 for example will have to run privileged (usually this means to run …
Awaiting Verification
Be the first to verify this fix
Sign in to verify this fix