• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue [Bug️] Real-Time Log Monitoring Times Out on Cloudflare

J.Wick

Regular Pleskian
Server operating system version
Rocky Linux 8.10
Plesk version and microupdate number
18.0.67
When starting real-time log monitoring, it crashes after 100 seconds, which is Cloudflare's default, and throws a 524 Error.

No matter your rule, it's unpreventable. Even when disabling caching with the orange cloud, going straight to the subdomain IP does not fix it, suggesting it's the origin server.

hosting.domain.net/smb/log-file/browser/id/*

Could anyone possibly suggest a fix?
 
If I am not mistaken, as long as your domain/subdomain is routed through Cloudlare's DNS the 100 seconds limit is applied even if your bypass the Cloudflare proxy/pause Cloudflare. To me that sounds like you are hitting the limit rather than product bug with Plesk. Have you checked the server performance?
 
If I am not mistaken, as long as your domain/subdomain is routed through Cloudlare's DNS the 100 seconds limit is applied even if your bypass the Cloudflare proxy/pause Cloudflare. To me that sounds like you are hitting the limit rather than product bug with Plesk. Have you checked the server performance?
Server performance is acceptable.

Doing some research, if Plesk were to use Server-Sent Events (SSE) instead of what it currently uses, it would solve this problem. Considering the hosts using Cloudflare, this might be something Plesk Devs want to implement.
 
Thank you for your suggestion. I will double-check with our team for the possibility of SSE integration. In the meantime, what I can recommend is to try using the server IP address or the hostname (if the same is not routed through Cloudflare) that should allow you to check the logs in real-time.
 
Thank you for your suggestion. I will double-check with our team for the possibility of SSE integration. In the meantime, what I can recommend is to try using the server IP address or the hostname (if the same is not routed through Cloudflare) that should allow you to check the logs in real-time.
Thanks, but that defeats the purpose of using Cloudflare security to protect the server IP. Hope to see a future upgrade.
 
Back
Top