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

[frg62]

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!
(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?

 

[Sebahat.hadzhi]

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.

 

[frg62]

I applied the two first suggestions, they did not change anything.
After a while, I still end up with the following error message:
The page is not redirected correctly.
An error occurred while connecting to <domain>:<modified_secured_port>.
The cause of this problem may be the deactivation or refusal of cookies.

As I am not using any cookies filtering in my browser, unless anyone has another suggestion, I suppose it leaves me with opening a ticket with Plesk Support...

 

[King555]

Did you change the Plesk port in /etc/sw-cp-server/conf.d/plesk.conf? I did this and Monitoring works fine. Maybe because I allow the old port via localhost:

listen 12345 ssl;
listen 127.0.0.1:8880 default_server;

 

[frg62]

I had indeed modified plesk.conf, as instructed in:

https://support.plesk.com/hc/en-us/articles/12377561753111-How-to-change-the-ports-for-the-Plesk-interface-on-Linux

And reverting there to port 8880 solved the display problem.
Thanks a lot!

(I also deleted the lines I previously added to panel.ini.)

Now I wonder if this could have consequences somewhere else in the GUI.
I would think not, because this line only concerns intern listening on localhost, but I am not sure...

 

[King555]

Now I wonder if this could have consequences somewhere else in the GUI

I work with a changed port since many, many years and did not encounter any problems, except a warning message when installing Plesk updates via CLI ("... some ports not reachable ..."), which can obviously be ignored.

 

[frg62]

Cool, thanks for this info!