Search results

We never had an empty certificate request confirmation box in the moment, when a new certificate request was initiated manually. Maybe you should open an own bug report as my one is related to a different issue - the renewal of already existing wildcard certificates that are also used for...

@dklaric Was the renewal status already broken before the upgrade to the latest version of SSL It! ? If so see my annotations above.

For us the problem can be marked as solved. All recent certificate renewals worked out like a charm.

As it was not mentioned in the changelog - if you want to disable the paid and advertised "Vulnerability Protection" feature set the following rule in your "Panel.ini Editor": [ext-wp-toolkit] virtualPatchesFeature = false

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.