• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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. D

    Issue [ PI-729] Plesk Updater uses wrong certificate chain

    Hi @learning_curve, thanks for your update on this. As far as I understood the problem, I cannot change anything to make it work, right? What is the way to go here? As far as I got it, I could temporarily install and use Firefox because it uses it own cert record set. I typically use the GUI...
  2. D

    Issue [ PI-729] Plesk Updater uses wrong certificate chain

    To minimize chances it's a matter of my end device, I used the tools of Geocerts which allows to scan the SSL certificate on a custom port. On mydomain.tld:8443, everything looks fine: However, the tool also complains on mydomain.tld:8447 when the autoupdater is up, running, and scanned...
  3. D

    Issue [ PI-729] Plesk Updater uses wrong certificate chain

    Hello Nic G, thanks for your ideas. I removed the lines from the panel.ini but this changed not the behaviour. Regarding your question 2, yes, I indeed use the same browser. This happens on both Chrome and Safari. Logged in on mydomain.tld:8443 (certificate valid) on my MacBook (MacOS Big Sur...
  4. D

    Issue [ PI-729] Plesk Updater uses wrong certificate chain

    I currently have trouble to secure the Plesk updater which opens at port 8447 when I click "Updates" on the tools and settings page in the Plesk admin panel. I migrated my server from Ubuntu 18.04 to 20.04 using the Plesk Migrator tonight and I'm now on Plesk Obsidian 18.0.39 Update 1...
Back
Top