New VestaCP Install and now Nginx is busted
Posted: Sat Jun 01, 2019 8:26 pm
I normally don't ask for help, but I'm stumped on this. After a 6 hour migration to get my website moved to a new VestaCP instance, get Opcache and Redis,as well as the site online. I noticed that VestaCP is no longer accessible, though it was working last night.
This instance is using Apache + Nginx for the backend as I'm not versed with Nginx and we have a lot of stuff in our .htaccess file.
So far, when I try to start Vesta, it completes. Nginx does not. And I really need access to the CP as I have another site to bring over, and I need to lock down the site. Looking for any assistance.
service nginx status
Redirecting to /bin/systemctl status nginx.service
● nginx.service - nginx - high performance web server
Loaded: loaded (/usr/lib/systemd/system/nginx.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2019-06-01 11:22:57 EDT; 4h 58min ago
Docs: http://nginx.org/en/docs/
Process: 12144 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE)
Jun 01 11:22:55 204816-4.204816-4.com nginx[12144]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Jun 01 11:22:55 204816-4.204816-4.com nginx[12144]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Jun 01 11:22:56 204816-4.204816-4.com nginx[12144]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Jun 01 11:22:56 204816-4.204816-4.com nginx[12144]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Jun 01 11:22:57 204816-4.204816-4.com nginx[12144]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Jun 01 11:22:57 204816-4.204816-4.com nginx[12144]: nginx: [emerg] still could not bind()
Jun 01 11:22:57 204816-4.204816-4.com systemd[1]: nginx.service: control process exited, code=exited status=1
Jun 01 11:22:57 204816-4.204816-4.com systemd[1]: Failed to start nginx - high performance web server.
Jun 01 11:22:57 204816-4.204816-4.com systemd[1]: Unit nginx.service entered failed state.
Jun 01 11:22:57 204816-4.204816-4.com systemd[1]: nginx.service failed.
journalctl -xe
Jun 01 16:21:55 204816-4.204816-4.com systemd[1]: Unit nginx.service entered failed state.
Jun 01 16:21:55 204816-4.204816-4.com systemd[1]: nginx.service failed.
Jun 01 16:21:55 204816-4.204816-4.com polkitd[8525]: Unregistered Authentication Agent for unix-process:47010:1900002 (system bus name :1.649, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jun 01 16:21:57 204816-4.204816-4.com unix_chkpwd[47035]: password check failed for user (admin)
Jun 01 16:21:57 204816-4.204816-4.com sshd[47029]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.81.81 user=admin
Jun 01 16:21:59 204816-4.204816-4.com sshd[47029]: Failed password for admin from 141.98.81.81 port 42477 ssh2
I've checked the Nginx config and it's also good.
nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
This is on a VM running Centos 7, PHP 7 and MariaDB. I really don't want to reinstall and migrate this site again, only to run into these issues.
Thanks!
This instance is using Apache + Nginx for the backend as I'm not versed with Nginx and we have a lot of stuff in our .htaccess file.
So far, when I try to start Vesta, it completes. Nginx does not. And I really need access to the CP as I have another site to bring over, and I need to lock down the site. Looking for any assistance.
service nginx status
Redirecting to /bin/systemctl status nginx.service
● nginx.service - nginx - high performance web server
Loaded: loaded (/usr/lib/systemd/system/nginx.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2019-06-01 11:22:57 EDT; 4h 58min ago
Docs: http://nginx.org/en/docs/
Process: 12144 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE)
Jun 01 11:22:55 204816-4.204816-4.com nginx[12144]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Jun 01 11:22:55 204816-4.204816-4.com nginx[12144]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Jun 01 11:22:56 204816-4.204816-4.com nginx[12144]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Jun 01 11:22:56 204816-4.204816-4.com nginx[12144]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Jun 01 11:22:57 204816-4.204816-4.com nginx[12144]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Jun 01 11:22:57 204816-4.204816-4.com nginx[12144]: nginx: [emerg] still could not bind()
Jun 01 11:22:57 204816-4.204816-4.com systemd[1]: nginx.service: control process exited, code=exited status=1
Jun 01 11:22:57 204816-4.204816-4.com systemd[1]: Failed to start nginx - high performance web server.
Jun 01 11:22:57 204816-4.204816-4.com systemd[1]: Unit nginx.service entered failed state.
Jun 01 11:22:57 204816-4.204816-4.com systemd[1]: nginx.service failed.
journalctl -xe
Jun 01 16:21:55 204816-4.204816-4.com systemd[1]: Unit nginx.service entered failed state.
Jun 01 16:21:55 204816-4.204816-4.com systemd[1]: nginx.service failed.
Jun 01 16:21:55 204816-4.204816-4.com polkitd[8525]: Unregistered Authentication Agent for unix-process:47010:1900002 (system bus name :1.649, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jun 01 16:21:57 204816-4.204816-4.com unix_chkpwd[47035]: password check failed for user (admin)
Jun 01 16:21:57 204816-4.204816-4.com sshd[47029]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.81.81 user=admin
Jun 01 16:21:59 204816-4.204816-4.com sshd[47029]: Failed password for admin from 141.98.81.81 port 42477 ssh2
I've checked the Nginx config and it's also good.
nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
This is on a VM running Centos 7, PHP 7 and MariaDB. I really don't want to reinstall and migrate this site again, only to run into these issues.
Thanks!