Knowledge Base

“Origin is not allowed” error in Monitoring extension when port 443 is in use in Plesk Panel UI

Symptoms

"No data" and "origin not allowed" messages are shown for graphs in Plesk > Monitoring:
Port 443 was used to log in to Panel UI.

Cause

Plesk Extension bug with ID EXTPLESK-5535 which was already fixed in Plesk 18.0.61.

Resolution

The bug has been resolved permanently in Plesk version 18.0.61, due to which it is recommended to update your Plesk to version 18.0.61 by following the steps in this article:
How to update Plesk Obsidian to the latest build

Plesk Obsidian 18.0.69 is Here!

Now Available: Plesk Obsidian 18.0.68

Plesk Obsidian 18.0.67 Has Arrived!

Knowledge Base

How to display hardware changes in Advanced Monitoring?

Cannot log into Plesk: Composer detected issues in your platform: Your Composer dependencies require a PHP version “>= 7.4.0”. – Plesk

Extensions return ERR_SSL_PROTOCOL_ERROR, cannot log in with 2-factor authentication after update to Plesk Obsidian 18.0.61

DNS Integration for Cloudflare® extension does not synchronize _acme-challenge TXT record while issuing WIldcard SSL automatically even with Auto-sync enabled

Hosting Wiki

Knowledge Base

“Origin is not allowed” error in Monitoring extension when port 443 is in use in Plesk Panel UI

Symptoms

Cause

Resolution

Plesk Obsidian 18.0.69 is Here!

Now Available: Plesk Obsidian 18.0.68

Plesk Obsidian 18.0.67 Has Arrived!

How to display hardware changes in Advanced Monitoring?

Cannot log into Plesk: Composer detected issues in your platform: Your Composer dependencies require a PHP version “>= 7.4.0”. – Plesk

Extensions return ERR_SSL_PROTOCOL_ERROR, cannot log in with 2-factor authentication after update to Plesk Obsidian 18.0.61

DNS Integration for Cloudflare® extension does not synchronize _acme-challenge TXT record while issuing WIldcard SSL automatically even with Auto-sync enabled

Install “Origin is not allowed” error in Monitoring extension when port 443 is in use in Plesk Panel UI extension