Search results

This issue did also disappear in other affected areas (e.g. PHPMyAdmin / [...]). And most important: we have special domains that are reverse proxying the Plesk admin panel to have individual login URLs for our clients and resellers. This was not working anymore since Plesk 18.0.61, when the...

With Plesk Obsidian 18.0.61 Update #3 the build-in monitoring tool is working again, same as the Multi-Factor Authentication (MFA) extension - at least for HTTP/2.

We can confirm the bug also on servers, where Google Authenticator was replaced by the Multi-Factor Authentication (MFA) extension (Debian 11).

Sure, it was not patched / solved yet. Better not update your live systems.

Sad to see that this issue has a low priority. Based on the weekly update release strategy of Plesk we have to live with it for at least one more week or even more.

We have the same issue on our servers. There seems to be no real cleanup. We have servers that came originally from Debian 10 and are now on Debian 12. Because of those dependencies we still have old packages of Debian 10 and 11 on the system. To check and remove those packages in aptitude via "...

@learning_curve This bug is a clear indicator, that Plesk does not make a proper (automatic) testing before new releases are deployed. It just cannot be, that the admin panel gets inaccessible after a normal update. We do not have a fancy setup, we are just using the normal options, the admin...

@Kaspar@Plesk The big problem behind this issue is, that our clients cannot handle it and this triggers support requests. If there is no fast patch release with version 18.0.61 Update #2 addressing this issue, the whole 18.0.61 release should get a red flag and not rolled out anymore.

The issue also affects other plugins, e.g. the "Google Authenticator". A redirect is triggered including port "8880" leading to the know "ERR_SSL_PROTOCOL_ERROR".

@Kaspar@Plesk In our case the problem is caused by our login URL to the Plesk interface. We do not use Port 8443 to login to the admin panel. If we login via this port, the monitoring works like a charm. e.g. https://[hostname-plesk-server]:8443/ But if we login without this port, the...

@ChristophRo We tested on Debian 11 and 12. Both operating systems are affected for our servers. If you have no problems at all maybe we have a conflicting extension or setting. We will investigate it further.

@Kaspar@Plesk Yes latest version Plesk Obsidian 18.0.61 Update #1.

We can confirm this bug. We updated some test servers to Plesk Obsidian 18.0.61 Update #1 too. The build-in monitoring tool is broken and does not display any graphs anymore. The Google Chrome development console shows the errors mentioned in this bug report: Failed to load resource...

@Kaspar@Plesk Thanks for the clarification. The minimal file size + the different behavior when "Serve static files directly by nginx" is activated caused our confusion. The topic can be marked as resolved. Everything works fine and as expected related to the Plesk documentation.

As described previously in this bug report, we also encounter the problem, that sometimes the "SSL/TLS certificate for mail" is removed from the domain leading to warnings in the mail clients of our customers. This happens very seldom, but it occurs. The affected wildcard certificates are still...

Username: TITLE "Smart static files processing" is not working anymore PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.60 Update #1 PROBLEM DESCRIPTION When "Smart static files processing" is enabled for a website, some static files should be delivered by...

@Kaspar@Plesk Thanks for the clarification. The problem did disappear when the license status switched from "expired" (orange label) to "terminated" (red label) in Plesk 360. Then the license will not be re-installed automatically anymore. Maybe Plesk should stop downloading keys with the...

Adding a server to Plesk 360 does involve a lot of private data transfer where we do not have the permission of our clients for. I will make a bug report soon.

Yes it also happens when we retrieve the keys manually. We did not sign up for Plesk 360 yet.

This problem does still exist in 2024 under specific circumstances. We have an extension where we did exchange the license key to an external one (not bought from Plesk). The old subscription was cancelled via cleverbridge (Plesk). The already expired key was deleted under "Tools & Settings -...