• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question what's the reason you pulled Plesk v18.0.61 again?

ChristophRo

Regular Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
18.0.61
Just askin, because we've already installed it on two servers...
Something we need to be worried about or look after specifically?
 
There is an issue which prohibits users to login to Plesk on port 443 (so via a custom URL). A hotfix is scheduled for this week.
 
Hi, I also updated one of our servers to 18.0.61 earlier than I should have... now Monitoring / Grafana is broken. This also seems to be a port / redirect issue of some sort.
 
My Monitoring / Grafana is also broken after updating to Plesk Obsidian 18.0.61 Update #1.

Browser console reports a request timed out to https://[host_name]:8880/modules/grafana/service/logout and also https://[host_name]:8880/modules/grafana/service/d/monitoring__overview?kiosk=tv&theme=light

and Unhandled Promise Rejection: AxiosError: timeout exceeded
 
I just created a new ISSUE for MFA on Port 8880, which breaks on custom URLs logins using Cloudflare to secure Plesk.
 
Hello everyone, I also have the problem with the 8880 after updating to Plesk Obsidian 18.0.61 Update 1 :(

I have 3 servers, the same everywhere. How can I solve the problem?
 
Back
Top