Search results

Hello @SalvadorS , it could also be a "bad crawler" that brings your site down. We had this a lot recently too even though we are using a very good firewall to block most of such bad networks where the crawlers coming from. Just check your access log of the domain affected with the following...

We can confirm now, that the first domain + subdomain setups with one wildcard certificate did renew correctly without any issues. That looks promising. Let's wait one more week to be sure. Only combinations with an already broken renewal status are still problematic. The Plesk team is on it but...

Clicking "Cancel" did work for us. Later the wildcard certificate was renewed correctly and assigned to the main domain plus subdomain. We have another server with the same issue. The certificate is not due yet but we still have an old order including the "Cancel" button. We did install the...

We did it but it has no effect. Looks like the bugfix does not work for our case. We did click now "Cancel". Let's wait another 24 hours if at least the certificate gets renewed.

The affected certificate of domain + subdomain was not renewed and shows still the known buggy behavior: Does the new version take care already "broken" renewal processes?

Is there any ETA for a bugfix? We get a lot of negative response from our clients that they are forced to make the 2FA every time they login again. Especially admins are annoyed.

We did install the latest version on one of our smaller servers that is affected by this bug (only 8 domains hosted in total on that server). At the moment we still see the bug for one combination of domain + subdomain using the same SSL certificate (certificate will expire in 18 days and is in...

@learning_curve The command... ... should be used carefully. Plesk has temporary sources while updating the base system (e.g. 50sw_autoinstaller.list). In that moment many packages are not in the list of "Obsolete and Locally Created Packages" anymore. After the update procedure is finished...

@learning_curve We did not experience such problems but we did only uninstall packages from the previous OS. The "old/obsolete" packages from the current OS are still in place.

We had nearly 150 Debian 10 packages left after upgrading from Debian 10 to 11. All dependencies were connected in some way to Plesk packages. Originally this came to our attention because some dependency warnings were thrown in the upgrade process. You can check your Debian systems to find the...

Maybe as additional information for the developers of Plesk directly here in the bug report: - This issue did also disappear in other affected areas (e.g. PHPMyAdmin / [...]). - Reverse proxying was also affected: we have special domains that are reverse proxying the Plesk admin panel to have...

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