• 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

Resolved Plesk Monitoring = An unexpected error occurred

JohnBee

JohnBee

Basic Pleskian
Server operating system version
ubuntu22.04
Plesk version and microupdate number
Plesk Obsidian v18.0.49_build1800230110.16
Whenever I click on Monitoring on the left menu in Plesk, I get the following error; An unexpected error occurred
That said, I can however monitor my server on monitoring.platform360.io/dashboard/overview without issue, though it just doesn't seem to want to work with Plesk

Any ideas as to what might cause this?
 
I have the same problem with Plesk Obsidian 18.0.49 on Centos 7.0.2009
When I click on Monitoring, a white screen appears after a few seconds with the message "An unexpected error occurred" and then nothing happens.
Even a '# plesk repair install' doesn't help.

Anyone an Idea?
 
@JohnBee Please check log entries in /var/log/plesk/panel.log for entries like "ERR [panel] Unable to Connect to ssl://api.monitoring360.io:443. Error #110: Connection timed out:" or similar and following. Please provide these here for further analysis.
 
Miracles happen! I was just about to search the logs and suddenly the monitoring works as it should. The question is how long it lasts. But I'll try to find the relevant log sections anyway. But I think, that takes a while. ;)
 
Ok, here we are:
Output from "# cat panel.log | grep "Unable to Connect to ssl" | less
---
[2023-01-29 21:39:12.104] 822:63d6e78019633 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-29 21:49:11.509] 4133:63d6e9d77c30e ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-29 21:59:11.758] 7399:63d6ec2fb8f16 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-29 22:00:12.024] 7713:63d6ec6c05cc4 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-29 22:09:11.502] 10629:63d6ee877a8e7 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-29 22:29:11.592] 17376:63d6f33790703 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-29 22:39:12.018] 20656:63d6f590045a0 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-29 23:09:11.584] 30276:63d6fc978e891 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-29 23:19:12.192] 1185:63d6fef02ebbb ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-29 23:29:11.619] 4497:63d7014796e40 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-29 23:49:11.998] 10957:63d705f7f37bc ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-29 23:59:12.100] 14179:63d7085017a47 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 03:49:11.684] 4247:63d73e37a7008 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 03:59:12.021] 7521:63d740900504d ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 04:29:12.062] 17232:63d747980f090 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 04:39:11.835] 26319:63d749efcbcff ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 04:49:11.948] 29538:63d74c47e7715 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 04:59:12.023] 32767:63d74ea005893 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 05:19:11.983] 6875:63d7534fefd29 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 05:29:11.728] 10064:63d755a7b1896 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 05:59:11.960] 22516:63d75cafea148 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 06:00:12.268] 23032:63d75cec4151d ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 06:09:11.919] 26949:63d75f07e0270 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 06:29:11.543] 1248:63d763b784809 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 06:49:11.587] 8868:63d768678f2a5 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 07:19:11.580] 18954:63d76f6f8d9ca ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 08:29:12.012] 9369:63d77fd802bdc ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-30 08:49:11.712] 24911:63d78487adac6 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
---
This is just a small excerpt. ;)
 
Most likely either port 443 is blocked for outgoing traffic or the IPs of the Plesk 360 service are banned in either Fail2Ban, firewall or another security software on the server.
 
Seeing the same issue this morning with a customers box.

CentOS Linux 7.9.2009 (Core)
Version 18.0.49
Outbound 443 confirmed working.

Updating to 18.0.51 was able to resolve the issue.
 
Description: Ubuntu 20.04.6 LTS
Release: 20.04
Outbound 443 confirmed working (not on Fail2Ban or in iptables)

And I'm still getting the "An unexpected error occurred"

There is nothing in panel.log or syslog that refers to this or to api.monitoring360.io

Open to suggestions -

Many thanks,

Troy
 
Peter Debik said:
It's a new issue with a server certificate. You need to update it on your server. Here is a simple guide how to do it:
Click to expand...
Thank you - I had seen the "update-ca-certificates" and tried this - but no joy.
The command returned:

# update-ca-certificates
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.

And the problem persists.

I see your note to upgrade to next version of Plesk - so I'll look at that step next.

Many thanks for your help!
 
tyzer007 said:
Thank you - I had seen the "update-ca-certificates" and tried this - but no joy.
The command returned:

# update-ca-certificates
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.

And the problem persists.

I see your note to upgrade to next version of Plesk - so I'll look at that step next.

Many thanks for your help!
Click to expand...
After updating Plesk to the latest version - all is working again.

Thank you,

Troy
 
Hi, I have the same issues with one webserver. Plesk Monitoring returns: "An unexpected error occurred"
I tried:
1.
# update-ca-certificates
Dependencies resolved.
Nothing to do.
Complete!

2. Update Plesk from 18.0.55 Update 2 to Version 18.0.56 Update #4
no changes

(3. No entries like api.monitoring360.io in panel.log. 360 Monitoring 360 is not used - only local version.)

What can I do?

(AlmaLinux 8.8)
 
Hello, thanks for your quick answer. Unfortunately, this did not work for me. I tried it 3 times.
But in protocolls of grafana-server.service I can find:
/usr/lib/systemd/system/grafana-server.service:35: Unknown lvalue 'ProtectProc' in section 'Service'
/usr/lib/systemd/system/grafana-server.service:32: Unknown lvalue 'ProtectKernelLogs' in section 'Service'
/usr/lib/systemd/system/grafana-server.service:31: Unknown lvalue 'ProtectHostname' in section 'Service'
/usr/lib/systemd/system/grafana-server.service:28: Unknown lvalue 'ProtectClock' in section 'Service'
many times.
But Grafana is running - it seems.
On https://support.plesk.com/hc/en-us/...loaded-because-the-Grafana-service-is-stopped I found same issues. But there is no update available. All is uptodate.

plesk repair --installation -y
doesn't solve the issue.
 
Crazy. Today everything is fine. I have to configure the monitoring because of new installation yesterday. I don't know why its running today. May be the plesk repair takes a little bit longer. Thanks for quick answers
 
Hello, have same issue with AlmaLinux 8.9... Monitoring with Grafana does not work time to time and shows "An unexpected error occurred". Reinstall does not help. Plesk 18.0.59

?
 
You must log in or register to reply here.

Similar threads

V
Issue Plesk Monitoring Error
Replies
1
Views
227
AYamshanov
AYamshanov
J
Issue Monitoring: An unexpected error occurred
Replies
10
Views
1K
Ale3051D3v
A
Lenny
Resolved Seeking Assistance with API Communication Issues via SSL on Plesk
Replies
4
Views
677
Lenny
Lenny
J
Issue Cannot activate monitoring
Replies
6
Views
934
andreas.scherer
andreas.scherer
D
Issue Activate 360 error An unexpected error occurred
Replies
3
Views
1K
Digitalone
D
Back
Top