Applicable to:
- SolusVM
Symptoms
- Cannot access SolusVM Master web interface on fresh intsallation:
CONFIG_TEXT: Unable to connect
- SolusVM web server fails to start:
# systemctl start svmstack-nginx.service
Job for svmstack-nginx.service failed because the control process exited with error code. See "systemctl status svmstack-nginx.service" and "journalctl -xe" for details.# tail -fn0 /var/log/svmstacknginx/error.log
2018/08/30 06:32:22 [emerg] 920388#0: bind() to 0.0.0.0:80 failed (98: Address already in use) -
Another web server service (httpd) is running on ports 80,443:
# netstat -tuxnlp | grep "80\|443"
tcp6 0 0 :::80 :::* LISTEN 916813/httpd
Cause
Most likely httpd webserver were installed on the fresh server as a part of default set of components
Resolustion
- Connect to the server via SSH
- Stop running httpd webserver and disable its start up on reboot:
# systemctl stop httpd.service
# systemctl disable httpd.service - Start SolusVM Master nginx-based web server:
# systemctl start svmstack-nginx.service
Comments
0 commentsPlease sign in to leave a comment.