You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there's no easy way to let the Webserver run on port 443 by using cordial. The webserver will fail as by Unix standards, ports below 1000 are reserved to root.
Since 443 is a default port for HTTPS, a way to let the webserver run smoothly via cordial on that port would be very nice
The text was updated successfully, but these errors were encountered:
I've been looking at this and every method has pros and cons; In short, the best way is to continue listening on ports 8080/8443 and use iptables (nftables) to redirect traffic like this:
Hey Peter,
So to clarify: Are you saying to configure the webserver to run on port 8443 (if doing HTTPS), and that iptables command will redirect it to port 443?
Currently there's no easy way to let the Webserver run on port 443 by using cordial. The webserver will fail as by Unix standards, ports below 1000 are reserved to root.
Since 443 is a default port for HTTPS, a way to let the webserver run smoothly via cordial on that port would be very nice
The text was updated successfully, but these errors were encountered: