• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Web Server's Default Page after updates

stevland

Basic Pleskian
Server operating system version
CentOS Linux 7.9.2009 (Core)
Plesk version and microupdate number
Plesk Obsidian Version 18.0.53 Update #2
I installed the latest minor update about an hour ago

Every site that I host is now displaying the "Web Server's Default Page" rather than its homepage. But the files (index.php, etc.) are intact.

Edit: There are no index.html files overriding index.php ones, etc.
 
I'm running
Code:
plesk repair fs -verbose
and seeing the following:

Code:
One or more files or directories in the root directory of the domain
  'coverac.ca' are either writable by anyone or neither readable nor
  writable by the owner. Such permissions are insecure and may result
  in or indicate a security breach
 
It's running through this for each of the domains I host and failing each time.

Code:
  There are incorrect permissions on some items in the system
  directory for the domain '[redacted]' .................... [ERROR]
    - Failed to stat
      /var/www/vhosts/system/[redacted]/conf/nginx.conf: No
      such file or directory
  Do you want to repair incorrect permissions? [Y/n] Y
    Repairing incorrect permissions ................................. [FAILED]
    - openat 'nginx.conf' failed: No such file or directory
      Failed to open safely
      /var/www/vhosts/system/[redacted]/conf/nginx.conf: No
      such file or directory
 
After running
Code:
plesk repair fs
and
Code:
plesk repair web
the situation has changed slightly. All secure domains result in a
Code:
ERR_SSL_PROTOCOL_ERROR
, while non-encrypted domains still show the Web Server's Default Page.
 
This is bizzare. I'm showing one example but it seems to be consistent with all of the domains that I host:

Code:
# plesk repair web mineralssouth.com

Checking web server configuration

  Repair web server configuration for domains mineralssouth.com? [Y/n] Y
    Repairing web server configuration for the domain
    mineralssouth.com ............................................... [2023-06-30 22:33:45.974] 3748:649fbaa683046 ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/httpdmng' '--reconfigure-domain' 'mineralssouth.com'] with exit code [1]
[FAILED]
    - httpdmng failed: [2023-06-30 22:33:30.044] 3799:649fbaa9e92db
      ERR [panel] Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.044] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.044] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.044] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.044] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.044] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.044] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.045] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.045] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.045] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.061] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.413] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.413] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.413] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.413] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.413] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.413] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.413] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.413] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.413] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.413] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:30.424] 3799:649fbaa9e92db ERR [panel]
      Invalid config structure in upload_max_filesize.0
      [2023-06-30 22:33:45.960] 3799:649fbaa9e92db ERR [util_exec]
      proc_close() failed ['/usr/local/psa/admin/bin/nginx_control'
      '--restart'] with exit code [1]
      Can not reload proxy server:

Error messages: 0; Warnings: 0; Errors resolved: 0

exit status 1
 
Code:
# plesk repair --installation -y -v

Reconfiguring the Plesk installation

[...]

Code:
 Cleaning active Panel sessions...
 Fixing permissions on Panel packages files
ERROR:[Errno 2] No such file or directory: '/opt/plesk/node/9/share/doc/plesk-nodejs9-9.10.1/CHANGELOG.md'

Bootstrapper repair finished.
Errors occurred while performing the following actions: regenerate web servers configuration files, fix Plesk packages permissions.
Check '/var/log/plesk/install/plesk_18.0.53_repair.log' and '/var/log/plesk/install/plesk_18.0.53_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Plesk support.
done

**** Product repair failed.

*****  problem report *****
Warning: rebuild web server configs with default templates after reconfiguration failure - using default templates does not solve the problem, restore custom ones
Warning: reconfigure web-server configurations skipping broken domains
Warning: rebuild web server configs with default templates after reconfiguration failure - using default templates does not solve the problem, restore custom ones

exit status 1
 
From one of your posts above I derive that at least in one domain or in one mutual php.ini file the upload_max_filesize is set to 0, which seems to be an issue for Apache. I have not encountered a similar situation before. My next step would be to check with
grep upload_max_filesize /opt/plesk/php/*/etc/*.ini
what the general settings are in the PHP ini files. These should default to 2M. Then please also check if you have a php section in /usr/local/psa/admin/conf/panel.ini. If so, what values does it have? If these are not actively needed, remove the php section completely.
 
grep upload_max_filesize /opt/plesk/php/*/etc/*.ini

Code:
/opt/plesk/php/5.2/etc/php.ini:upload_max_filesize = 2M
/opt/plesk/php/5.3/etc/php.ini:upload_max_filesize = 2M
/opt/plesk/php/5.4/etc/php.ini:upload_max_filesize = 2M
/opt/plesk/php/5.5/etc/php.ini:upload_max_filesize = 2M
/opt/plesk/php/5.6/etc/php.ini:upload_max_filesize = 2M
/opt/plesk/php/7.0/etc/php.ini:upload_max_filesize = 2M
/opt/plesk/php/7.1/etc/php.ini:upload_max_filesize = 2M
/opt/plesk/php/7.2/etc/php.ini:upload_max_filesize = 2M
/opt/plesk/php/7.3/etc/php.ini:upload_max_filesize = 2M
/opt/plesk/php/7.4/etc/php.ini:upload_max_filesize = 2M
/opt/plesk/php/8.0/etc/php.ini:upload_max_filesize = 2M
/opt/plesk/php/8.1/etc/php.ini:upload_max_filesize =  128M


Then please also check if you have a php section in /usr/local/psa/admin/conf/panel.ini. If so, what values does it have? If these are not actively needed, remove the php section completely.


Code:
[php]
settings.performance.upload_max_filesize[]=128M


[webserver]
nginxClientMaxBodySize = 128M

(The php and webserver values would have been added by myself at some point when I was trying to figure out how to overcome some limitation. I have now removed them and rebooted the server, but nothing has changed.)
 
I will not be able to solve this here without looking into the server. Please introduce the issue with a reference to the thread to Plesk support, so that a support engineer can check it and solve it on your server.

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
 
Hi Peter, that's exactly what I ended up doing. Gilson helped me right away. Super pleased with the service.

I'll post his findings here in case it helps anyone in the future:
For starters, I went through the logs but did not find a lot of things.
Then I noticed through nginx -t that the configuration syntax was OK but nginx itself was dead.

Jul 01 12:24:00 www.redacted.com systemd[1]: Starting Startup script for nginx service...
Jul 01 12:24:00 www.redacted.com sh[28839]: Not starting nginx as it is disabled in Plesk. Run 'plesk sbin nginxmng -e' to enable nginx in Plesk.

Thus I have disabled and enabled nginx:

[root@www ~]# plesk sbin nginxmng -d
[root@www ~]# plesk sbin nginxmng -e

And voilà, most of the time with this combination (syntax ok + nginx dead) this resolves the issue.
 
Back
Top