Search results

Hi, Cron task execution is logged in /var/log/cron. You will find there all the tasks that were executed. How do you back up your data? Is it scheduled within this timeframe?

Do you have, by any chance, the LiteSpeed extension?

That leaves you with a strace: dnf install strace strace -s1024 -o output.txt httpd -X -e Debug zip the output.txt file and send it in a private message. The file will contain references of all the hosted files, system users and IP addresses. Don't post it in the thread!

Understood. How about: systemctl reset-failed httpd systemctl start httpd

Try the following: httpd -X -e Debug Should tell you why it doesn't start

What do you consider a real firewall? Did you try Imunify360?

We also observed high traffic volumes from that huge subnet. The simplest approach is to block it since you don't expect traffic from a different hosting company. In your case, firewall blocking won't help since your firewall will see only Cloudflare IP addresses. You can block in nginx but it...

Interesting. Taking another look at my /etc/nginx/plesk.conf.d/server.conf, it's exactly the same as yours. If you reconfigure, do you still get the error message? plesk sbin httpdmng --reconfigure-all

Do you use a custom template? What do you have in: ls /usr/local/psa/admin/conf/templates/

What is the output of the following? plesk bin server_pref -s | grep ssl

I ran into a similar issue. In my case, it pointed out that I didn't have TLS1.3 enabled: plesk bin server_pref -s | grep ssl Since ssl-protocols didn't have TLSv1.3, I used: plesk bin server_pref -u -ssl-protocols 'TLSv1.2 TLSv1.3' Afterwards, I reconfigured the webserver and I had HTTP/3...

If you have 2 servers, just perform a migration with Plesk Migration Manager. The restore approach should also work.

Remove the AAAA records.

The domain DNS zone. Some registrars provide IPv6 by default in the hosted DNS zone. You changed only the A record while you still have AAAA records without having an IPv6 address on your server.

Interesting. Check the User-Agent used by the Let's Encrypt server. In the logs section of the website in Plesk, look for requests to /.well-known/. Please share the requests made while the certificate issue is attempted.

The Let's Encrypt error indicates you have a redirect loop. If you can access https://www.mydomain.com/.well-known/acme-challenge/gyFnutZ4Z6AHoPukt7ReBVgqd9Pkomcmu-0zKF_WKMU Let's Encrypt will also be able to access it. Once an attempt failed the challenge file remains in place. Thus the above...

Hi, Check /var/log/plesk/panel.log when the error is displayed. It should provide additional information.

Please provide all log entries related to 4577F8B8F9 grep 4577F8B8F9 /var/log/maillog

Hi, Plesk is set up in such a way that PHP scripts can't reach other webspaces/subscriptions. Along with the symlink protection, it offers good access separation between websites. You can also use CGroups to limit resources per subscription. Using Docker Proxy (can't reach the Docker...

Hi, Is the additional IP routed via 51.195.xx.xxx/32 by your provider, or is it within the same broadcast domain as the main IP?