Problems running sshttp about sshttp HOT 4 CLOSED

The reason is because to bind to a port < 1024, you must be "root". Please note that it's a feature from the OS rather than a bug in sshttp.
Feel free to give it a try with a higher port so you can see the difference.

from sshttp.

The reason is because to bind to a port < 1024, you must be "root"

Right. That's why I tried sudo and authbind because they should allow me to use restricted ports. I've tried random ports above 1024 but I get

sshttpd: Using HTTP_PORT=8080 SSH_PORT=22 and local port=5050. Going background.
Using caps/chroot.
Operation not permitted

which is similar to what I get when using authbind and port 443.

If I use sudo the output is still the same

sshttpd: Using HTTP_PORT=8080 SSH_PORT=22 and local port=5050. Going background.
Using caps/chroot.
chroot: No such file or directory
chroot: No such file or directory

I have an http server running on 80 and ssh on 22 so I'm not sure why I can't get this to run

from sshttp.

Yes, you need to run sshttp as root. it will then drop to specified user (default nobody)
and chroot to /var/lib/empty. Either create that directory, or use -R to specify another one.

from sshttp.

solved I guess

from sshttp.