• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Panel Login 404 Error

DaejuanJ

New Pleskian
After a fresh install on a Debian Wheezy system, I get the following error(s) when trying to access the control panel.

https://sub.example.com:8443/
404 Not Found
Nginx

My log
Code:
2014/06/09 19:04:15 [warn] 32236#0: conflicting server name "" on 0.0.0.0:8443, ignored
2014/06/09 19:04:26 [error] 22597#0: *43 "/usr/share/html/index.html" is not found (2: No such file or directory), client: 68.51.77.126, server: , request: "GET / HTTP/1.1", host: "sub.example.com:8443"


While http://sub.example.com:8880/ works fine
 
Last edited:
root@tower:~# grep -Rn "server_name" /etc/sw-cp-server/
/etc/sw-cp-server/fastcgi_params:21:fastcgi_param SERVER_NAME $server_name;
/etc/sw-cp-server/fastcgi.conf:22:fastcgi_param SERVER_NAME $server_name;
This is what I have.
 
Same problem after upgrade from 11.5 to 12.0 on Centos.

Same error messages in the log.

Any fix?

Another topic suggests you can fix it for a fresh install by removing --install-component agent. Not sure how to do that for an upgraded installation.
 
Last edited:
Same problem after upgrade from 11.5 to 12.0 on Centos.

Same error messages in the log.

Any fix?

Another topic suggests you can fix it for a fresh install by removing --install-component agent. Not sure how to do that for an upgraded installation.
 
Back
Top