• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Plesk Internal Monitoring & 360 Showing False 403s

IanJSaul

New Pleskian
Server operating system version
Ubuntu 20.04.4 LTS
Plesk version and microupdate number
Version 18.0.45 Update #2, last updated on Aug 14, 2022 07:07 AM
Aloha!

I've got an odd issue occurring with just 2 of ten nearly identical sites, they show as offline in monitoring, but are fully accessible and operating correctly.

All use DNS through Cloudflare, with Strict SSL/Origin CAs.

All sites have identical cache settings and optimizations.

They have been showing offline for over 24 hours, not short outage notifications by any means.

Nothing is jumping out at me in the logs, however, or I'm not looking in the correct areas.

Thanks for attention and assistance.
 
Just be sure I understand the issue correctly; you're websites are working fine but Plesk monitoring shows them being offline with 403 errors?
 
Yes, that's correct.

I've experimented with disabling the "Always Online" feature from Cloudflare to see if this was masking an issue, and there is no impact.

There is one other site that is occasionally showing "503 - Unavailable", and it is fully accessible as well.

Only the monitoring of the sites seems to be where issues exist.

Since posting this query, I've whitelisted all Cloudflare IPs in modsecurity and ipban.

I see a new recommendation from @myft above, and I'll try disabling bot fight mode now.

Thanks!
 
Ok, so this issue is still ongoing for some of the sites, and not others.

Enabling "Bot Fight Mode" will result in a "503 Unavailable" report in monitoring.

The "403 Forbidden" doesn't appear to be impacted by flipping bot mode on or off.

Anyone else experiencing similar issues?
 
Back
Top