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

Question How to parse error logs for a specific time period in Plesk?

Émerson Felinto

Regular Pleskian
Today at dawn my sites had a brief downtime. But I do not know a reliable way to know if the problem is in Plesk (configuration of apache, nginx and etc) or with the server (problems with the link).
The only information I got was the time the downtime happened. How can I use this to find the CAUSE of the problem?
 

Attachments

  • Screenshot 2018-02-26 at 06.39.41.png
    Screenshot 2018-02-26 at 06.39.41.png
    62.9 KB · Views: 7
First of all, read carefully and create bookmark for this KB article Plesk for Linux services logs and configuration files
This page is awesome !!! I will integrate all these logs to my papertrail, this way could this problem occur again I can check the logs for a certain period of time =)

If you haven't, be sure to whitelist the IPs for the various Uptime Robot servers;
Locations and IPs | Uptime Robot
Currently my firewall is disabled and I do not see any problem that could indicate blocking the robots uptime servers, considering that the lock should be permanent and not sporadic ...
(OFF-TOPIC) I see here on your profile that you are "Plesk Certified Professional". How can I get a seal like that? ;-)

Thanks for the suggestions but they were very vague and inaccurate! Could you give me more suggestions on how I can find where this problem is specifically?
 
Back
Top