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

Issue Converting site to https:// with Advisor Extension

gbotica

Regular Pleskian
Hi,

I miss the old Security Advisor extension, there was a nice easy way to install a Let's Encrypt cert and then, in another click, convert the site to https://. It all worked well, rewriting the database so all references to the site's domain were changed to https://

Now, with the Advisor extension it's not very clear.. I guess it's now the "Enable HTTP/2" option?

However, on my Plesk 17.8 / CentOS 7.5 server, whenever I click "Enable" for HTTP/2 I get the spinner and then ... nothing happens. The Enable button just reappears and that's it. Broken.

Is it possible to use the old Security Advisor instead?
 
What if you try to enable it in CLI with

# plesk bin http2_pref enable

What sort of errors do you have in the output?
 
Hi,

Thanks for the suggestion. It appears to work OK via CLI, but no difference when I go back to Plesk web UI -> Advisor

Code:
# plesk bin http2_pref --enable
HTTP/2 support was successfully activated.
# plesk bin http2_pref --status
Enabled

I think this is just a bug with Advisor, many of my sites are already using HTTP/2.

What does turning it on globally even actually do? I thought this would just be a site-specific option.

Is there anyway to convert site to https://, like there was with the old Security Advisor in PLesk 17.5? That was a really handy feature to convert a site's database to https:// with a single click.
 
Back
Top