• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue No data displayed in Monitoring extension anymore after modifying the Panel access port

frg62

Basic Pleskian
Server operating system version
Debian 11
Plesk version and microupdate number
Plesk Obsidian 18.0.67 Update #3
Hello,

Following continuous attacks on the Plesk panel of one of my servers (several hundreds per hour 24/7 for over a week now), I modified the access ports from 8880 and 8443 to other values.

Fail2ban was doing a good job, but this modification radically reduced the attacks to... zero! :cool:
(For now anyway...)

Unfortunately, as a side effect, the extension "Monitoring" does not display any graph anymore.
I guess it is using the standard ports on some level.

Is there a way to reconfigure this extension, so that it be able to function properly within this configuration?
 
Hello, @frg62 . As far as I am aware, the Monitoring extension uses http://127.0.0.1:8880 as endpoint. Please try adding the following lines to the panel.ini file where 8880 is the custom port you set:

[ext-monitoring]
rrdServerOrigin = http://127.0.0.1:8880

If there's no immediate effect, please try re-installing the extension. In case there's no change afterward, I would suggest opening a ticket with Plesk support for further review.
 
Back
Top