Re: nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied)

[lists]

I don't have server access at the moment, but I think nginx under FreeBSD runs under user www.  From: Zhang Chao Sent: Monday, July 10, 2017 6:24 PM To: nginx@nginx.org Reply To: nginx@nginx.org Subject: Re: nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied) Hi! Only the root can bind the ports small than 1024. You should start your nginx service with the sudo prefix. On 11 July 2017 at 09:20:40, Viaduct Lists (li...@viaduct-productions.com) wrote: Hi there. Looking to get port 80 serving. Changed to root, but the error keeps the user from running: nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/etc/nginx/nginx.conf:2 nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied) nginx: configuration file /usr/local/etc/nginx/nginx.conf test failed Is there any way to get nginx working as root? Is this a bad idea? I just don’t like running as port 8080. It complicates things down the road as I want to implement SSL (port 443) later on. Port numbers also get into my code later on. Any advice appreciated how I can get this on normal ports 80 and 443. _____________ Rich in Toronto @ VP _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx