Recent content by Daveo

Set the usage percentages to 80% instead of 20%, for all three you have set to 20%. Setting to 20% is very restrictive. 80% is better for smooth operation of server and it's resources.

I've tested via my mobile's 4G data and that proves that I can't access any domain or subdomain. Also, tried to access plesk and that failed too (which I expected it to). I have locked down SSH with a line in the config file that allows only my internal IP range (and as backup my external IP)...

I've done some changes to make my home server accessible internally only, but it seems that it still accessible externally. I have IP Access Restriction Management set to my internal network IP range and localhost (localhost is so the Plesk app still works). Firewall is enabled. I have set in...

It's got no pattern to when it occurs. It seems to be random now. Can go days/week without an email then get an email with this message. I've done all I can to see if there are any issues with the server, but all my tests show that server is fine and everything working as it should... except...

Got another email today... Yet, apt-get update & apt update complete without issue via command line and going to https://<hostname>:8443/admin/pum and clicking the blue 'Recheck Now' button also completes without issue (button dims after clicking then is clickable again after about a few...

Will do. Based on the last two emails, it seems to occur around every 3 days. Strangely I haven't received one today, if I base it on that 3 day rota. Also, to add this is a freshly installed Debian 12 installed via the netinst.iso image.

Here's the autoinstaller3.log file from 26th November thru to today.

I've received this email again yesterday. Yet apt update and apt-get update both complete without issues. Also apt upgrade completes without issues.

I was trying to access site from another computer on my network, which should of worked but got 502. Wiped system and install Debian 12 & Plesk then restored backup and everything working fine. I'm guessing something occurred during restore that broke Apache or something changed between...

The process I did was... Obtain full server backup via Plesk. Wipe system Install Debian 13 Install Redis Install Elasticsearch Install Plesk (with same setup I had with Debian 12) Tested everything at this point and all was working as I expected it to be. Uploaded full server backup to /var...

Received the following email from local server this morning... There was an issue with updating system packages and third-party components on the server. Please wait for the next automatic update or run the update manually: https://<domain>:8443/admin/pum Reason: 2025-11-23 06:26:21 INFO: pum...

Here are the screenshots of the Apache & Nginx Settings page for one of the sites that is using Apache on my local server. The Deny * then Allow 192.168.50.0/24 sections limits my sites on local server to allowing local access only.

Yes proxy mode was/is enabled on the Apache sites. I'll get a screenshot of the Apache & Nginx Settings page, as soon as I get back home.

All done and everything is now working fine again :) Not sure why no Apache sites were working after restoring full server backup on Debian 13.

I've reinstalled the server to Debian 12.12. Installed the things I needed: redis, elasticsearch, samba, nfs and plex. When I get back home I'll do the following... Install Plesk Upgrade MariaDB to 11.4 LTS Restore full server backup Check to make sure Apache & nginx sites are working Will...