We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
nginx: [emerg] bind() to 0.0.0.0:80 failed
-
- Posts: 258
- Joined: Fri Jan 10, 2014 7:34 pm
nginx: [emerg] bind() to 0.0.0.0:80 failed
When i am trying to do:
I am getting this error:
Stopping vesta-nginx: [FAILED]
Stopping vesta-php: [FAILED]
Starting vesta-nginx: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()
[FAILED]
What's wrong is there?
Code: Select all
service vesta restart
Stopping vesta-nginx: [FAILED]
Stopping vesta-php: [FAILED]
Starting vesta-nginx: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()
[FAILED]
What's wrong is there?
Re: nginx: [emerg] bind() to 0.0.0.0:80 failed
Sounds like nginx is stuck. Try "service nginx stop" first, or "ps faux | grep nginx" to see if an instance is still running that won't die. Maybe throw a kill -9 at the PID as a worst case scenario...I only say that because I like to live life on the edge ;)
-
- Posts: 258
- Joined: Fri Jan 10, 2014 7:34 pm
Re: nginx: [emerg] bind() to 0.0.0.0:80 failed
jarland wrote:Sounds like nginx is stuck. Try "service nginx stop" first, or "ps faux | grep nginx" to see if an instance is still running that won't die. Maybe throw a kill -9 at the PID as a worst case scenario...I only say that because I like to live life on the edge ;)
Code: Select all
[root@server conf.d]# ps faux | grep nginx
root 1852 0.0 0.0 103244 828 pts/0 S+ 14:34 0:00 \_ grep nginx
root 1625 0.0 0.0 66224 1304 ? Ss 14:29 0:00 nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf
nginx 1626 0.0 0.0 66368 2572 ? S 14:29 0:00 \_ nginx: worker process
nginx 1627 0.0 0.0 66228 1844 ? S 14:29 0:00 \_ nginx: worker process
nginx 1628 0.0 0.0 66228 1656 ? S 14:29 0:00 \_ nginx: cache manager process
service nginx stop worked well and start either.
when i access https://IP:8083/ it says page not found lol. But when i open any domain name on port 80 it works. What's going on here :D
Re: nginx: [emerg] bind() to 0.0.0.0:80 failed
kill 1625
If you're adventurous like me, kill -9 1625
If you're adventurous like me, kill -9 1625
-
- Posts: 258
- Joined: Fri Jan 10, 2014 7:34 pm
Re: nginx: [emerg] bind() to 0.0.0.0:80 failed
Killed, now i cannot see it in ps faux | grep nginxjarland wrote:kill 1625
If you're adventurous like me, kill -9 1625
But i still can't open my vesta panel page not found geez. What might be causing this?
Re: nginx: [emerg] bind() to 0.0.0.0:80 failed
Hmm. Did you try a "service vesta restart" again? My first thought is the failed restart attempt killed apache but failed to start things back up again because it couldn't kill nginx. With nginx dead now everything should start up again at command.
Maybe add in "service apache2 restart" or "service httpd restart"
Maybe add in "service apache2 restart" or "service httpd restart"
-
- Posts: 258
- Joined: Fri Jan 10, 2014 7:34 pm
Re: nginx: [emerg] bind() to 0.0.0.0:80 failed
Oh, thanks i rebooted my vps, and now service vesta restart works without errros!jarland wrote:Hmm. Did you try a "service vesta restart" again? My first thought is the failed restart attempt killed apache but failed to start things back up again because it couldn't kill nginx. With nginx dead now everything should start up again at command.
Maybe add in "service apache2 restart" or "service httpd restart"