• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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

Code:
listen 12345 ssl;
listen 127.0.0.1:8880 default_server;
 
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.
 
Back
Top