• 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
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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