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

HTTP/2 not working on browsers

@trialotto thank you so much for all the help. I've been trying to sort this out and every one of your answers is several google searches away from understanding it for me so sorry if I reply a bit late. I am still not getting it.. even in FF that you mentioned.

@learning_curve but it would be right to fix this yes? I think I will go for let's encrypt wildcard/multi-domain. Is it possible to solve this within plesk or the letsencrypt extension? if you have any online resource on how to set this up I'd love to read up. Thanks again!
 
@TonyD You can fix it if you want to, yes. In our case, it's not by using the (current) Plesk Extention, but by sourcing the Let's Encrypt certificate from an external provider. It's explained in the Plesk Extention thread in this forum HERE That link is to Post 184, so progress through to Post 187 and that gives some context, plus a link to an external Let's Encrypt provider.
 
Back
Top