• 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

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

learning_curve

Silver 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