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

Forwarded to devs Plesk 360 - Default Mis-Configuration(s)

learning_curve

Golden Pleskian
Username:

TITLE

Plesk 360 - Default Mis-Configuration(s)

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.41 MU # | Ubuntu 20.04.3 LTS | Nginx 1.20.2 | Apache2 2.4.41 (Ubuntu Backported) | - NB The Only Relevant Factors Are The Plesk Release & The OS

PROBLEM DESCRIPTION

Plesk 360 should not, by default, report disk usage errors for Ubuntu Snap Disk areas (/dev/loop*) - But it does

The whitelist of Plesk 360 IP IPv4 and IPv6 addresses has been changed without customer notification and still is (currently) a 404 page at the time this bug was raised

STEPS TO REPRODUCE

All of the required details are shown in this forum thread:

Question - Whitelists (IPv4 & IPv6) For Plesk 360 - Modified and/or Where Have They Gone?

ACTUAL RESULT

See above (Forum Thread)

EXPECTED RESULT

A re-configuration that resolves the two items detailed in "PROBLEM DESCRIPTION' above

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
AFAIK - This: Plesk 360 is still just a 404 page with zero content... but it's over two months now since the bug was confirmed.
Refer back to post #1 above for more details. Providing an acurate, up to date whitelist, for Plesk 360 cannot take more than two months... surely?
 
Back
Top