• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Connot access Plesk Web interface anyore - 404 Error

QST

New Pleskian
Hi!

I have installed the latest Plesk update a few days ago and on that day everything worked fine. Today, after trying to login into the Plesk Web interface, I get a 404 error message.

Error log shows:

[error] 14743#0: *4 open() "/opt/psa/admin/htdocs/index.html" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /index.html HTTP/1.0", host: "127.0.0.1:8443"​

Installed version: 17.5.3 Ubuntu 14.04 1705170317.16

Web-interface is using an nginx proxy command to redirect to the 8443 port (hence host address is 127.0.0.1). Before that everything worked just fine.

plesk repair installation - did not help
 
Try:

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
# plesk repair installation
 
Hi IgorC, thanks a lot for the prompt reply. It did not help, the error persists. I have noticed that in sw-engine.log there is the latest record:

[21-Jun-2017 02:00:25] NOTICE: Reloading in progress ...
[21-Jun-2017 02:00:25] NOTICE: reloading: execvp("/usr/sbin/sw-engine-fpm", {"/usr/sbin/sw-engine-fpm", "--fpm-config", "/etc/sw-engine/sw-engine-fpm.conf", "-c", "/opt/psa/admin/conf/php.ini"})
[21-Jun-2017 02:00:25] NOTICE: using inherited socket fd=8, "/var/run/sw-engine.sock"
[21-Jun-2017 02:00:25] NOTICE: using inherited socket fd=8, "/var/run/sw-engine.sock"
It looks like the config file was overwritten by someone/something, doesn't it?
 
Just to add, my nginx redirect command looks like this:

Code:
location / {

allow xx.xx.xxx.xxx/24;
 deny all;

proxy_pass https://127.0.0.1:8443;

}
 

Attachments

  • Capture.JPG
    Capture.JPG
    83.1 KB · Views: 6
Back
Top