On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Wordpress SSL/TLS status does not update accordingly when SSL certificate is installed




  • Avatar
    B Pfleging

    The proposed method when not using the advisor does not work when having a multisite installation.

    In this case, the database changes as proposed at https://webdevstudios.com/2015/02/11/how-to-set-up-https-on-wordpress/ help to get this done.

    I remember, that I had login problems with that multsite installation beforehand, and right now, I was wondering whether the problem actually occured since I first relied on using the Advisor securing method. So maybe someone a Plesk can check: Create a new Wordpress installation (non-TLS), convert it into a multisite installation (with subdirectories for the new sites) and then try to enable TLS. Can it be that in this case the advisor securing method breaks the login?

    Comment actions Permalink
  • Avatar
    Nikita Nikushkin

    Hi @b_p,

    Thank you for the feedback!

    I followed the mentioned steps:

    1. Created a new Wordpress installation without SSL/TLS enabled
    2. Converted it into a multisite installation with "Sub-domains"
    3. Enabled SSL/TLS via "Plesk > Domains > example.com > Advisor > Secure WordPress Websites | Switch to HTTPS"

    However, it did not break the logging to the WordPress possibility

    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request