• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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