Recent content by stevland

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...

/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...

# plesk repair --installation -y -v Reconfiguring the Plesk installation [...] 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...

This is bizzare. I'm showing one example but it seems to be consistent with all of the domains that I host: # plesk repair web mineralssouth.com Checking web server configuration Repair web server configuration for domains mineralssouth.com? [Y/n] Y Repairing web server configuration...

After running plesk repair fs and plesk repair web the situation has changed slightly. All secure domains result in a ERR_SSL_PROTOCOL_ERROR, while non-encrypted domains still show the Web Server's Default Page.

It's running through this for each of the domains I host and failing each time. 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...

I'm running plesk repair fs -verbose and seeing the following: 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...

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 use curl to get a DNS record from my Plesk server: curl -X GET -H 'authorization: Basic xxx' -H 'accept: application/json' 'https://example.com:8443/api/v2/dns/records/15781/' result: { "id": 15781, "type": "A", "host": "home.example.com", "value": "123.123.123.123"...

I tried lots of other things that I didn't get around to documenting as well. I don't know what ultimately worked. In fact, it still doesn't make sense to me at all. But just now I went back to My Domain > PHP Settings Although the maximum value for both post_max_size and upload_max_filesize...

Things I've been trying: # php -i | grep php.ini Configuration File (php.ini) Path => /opt/plesk/php/8.1/etc Loaded Configuration File => /var/www/vhosts/system/mydomain/etc/php.ini I've edited both /var/www/vhosts/system/mydomain/etc/php.ini (even though it's read-only)...

Oops, since I replied I realized I followed the instructions for nginx when there are different instructions for Apache. I have subsequently added LimitRequestBody 2147483647 to /etc/apache2/apache2.conf{,.orig} I have restarted httpd and psa and used # plesk repair web -domains-only for good...

Does this article help? Thank you. Yes. Although when I restarted nginx: # service nginx reload Redirecting to /bin/systemctl reload nginx.service Job for nginx.service invalid. So I said three 'Hail Marys' and restarted httpd instead.

I have tried absolutely every tip I have found. upload_max_filesize shows at 16M in Plesk and in my phpinfo.php. The default setting in Plesk is 2M! I am frantically trying to upload a critical file to WordPress that is slightly over 16 MBs. "The uploaded file exceeds the upload_max_filesize...

Nevermind. I assumed I should be able to connect using the IP address, so when it didn't connect I panicked. There's nothing worse than a torrent of customers freaking out with email issues. But when I use mail.hostname.com it resolves to the new IP and everything works perfectly.