• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. Hangover2

    Forwarded to devs SSL It! breaks renewal and usage of Let's Encrypt wildcard certificates when subdomains are involved

    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...
  2. Hangover2

    Forwarded to devs SSL It! breaks renewal and usage of Let's Encrypt wildcard certificates when subdomains are involved

    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...
  3. Hangover2

    Forwarded to devs SSL It! breaks renewal and usage of Let's Encrypt wildcard certificates when subdomains are involved

    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.
  4. Hangover2

    Forwarded to devs SSL It! breaks renewal and usage of Let's Encrypt wildcard certificates when subdomains are involved

    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?
  5. Hangover2

    Resolved Multi-Factor Authentication (MFA) extension does not remember device

    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.
  6. Hangover2

    Forwarded to devs SSL It! breaks renewal and usage of Let's Encrypt wildcard certificates when subdomains are involved

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

    Issue Older packages not being cleaned up

    @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...
  8. Hangover2

    Issue Older packages not being cleaned up

    @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.
  9. Hangover2

    Issue Older packages not being cleaned up

    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...
  10. Hangover2

    Resolved Monitoring does not work with http3

    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...
  11. Hangover2

    Resolved Plesk 18.0.61 Login Problem w/ Google Auth/MFA & Cloudflare

    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...
  12. Hangover2

    Resolved Monitoring does not work with http3

    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.
  13. Hangover2

    Resolved Multi-Factor Authentication (MFA) extension does not remember device

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

    Resolved Plesk 18.0.61 Login Problem w/ Google Auth/MFA & Cloudflare

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

    Resolved Plesk 18.0.61 Login Problem w/ Google Auth/MFA & Cloudflare

    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.
  16. Hangover2

    Issue Older packages not being cleaned up

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

    Resolved Plesk 18.0.61 Login Problem w/ Google Auth/MFA & Cloudflare

    @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...
  18. Hangover2

    Resolved Plesk 18.0.61 Login Problem w/ Google Auth/MFA & Cloudflare

    @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.
  19. Hangover2

    Resolved Monitoring does not work with http3

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

    Resolved Monitoring does not work with http3

    @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...
Back
Top