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.

Articles in this section

See more

After update to Plesk Obsidian webmail shows invalid ssl warning for domains with no hosting

Avatar
Dinara Aspembitova
Updated
Follow
Plesk for Windows Plesk for Linux kb: bug ext: le ABT: Group A

Applicable to:

  • Plesk for Linux
  • Plesk for Windows

Symptoms

  • The server was upgraded to Plesk Obsidian;
  • Before the upgrade, there was domain without hosting, only email accounts, that were accessed through webmail via HTTP;
  • After the upgrade, webmail is redirected to HTTPS as a result webmail shows invalid ssl warning.

Cause

This is Plesk bug with ID PPPM-11114, which is planned to be fixed in one of the future product updates.
Follow the article to be notified when the bug is fixed - the article will be updated.

Resolution

As a workaround perform the steps below:

  1. Log into Plesk.
  2. Switch on hosting: go to  Domains > example.com > Hosting settings > click Change and set Hosting type to Website hosting ;
  3. Install the certificate for webmail according to the article How to secure the webmail with a Let's Encrypt certificate in Plesk ;
  4. Switch off hosting: go to  Domains > example.com > Hosting settings > click Change and set Hosting type to No web hosting.

Comments

8 comments

Sort by Date Votes
  • Avatar
    Sathiya

    Thanks for understand the issue and workaround.

    1
    Comment actions Permalink
  • Avatar
    Ralph W.

    The 3. step in the descriptions linked to by  How to secure webmail using Let's Encrypt in Plesk Onyx it says "Obtain a new Let's Encrypt certificate going to Domains > example.com > Let's Encrypt > Make sure the option Secure webmail on this domain is enabled > Click on Install:"

    In my Obsidian version 18.0.21 Update 3 there is no "Let's Encrypt" entry (the Let's Encrypt Extension is installed and activated for the domain), just a "SSL/TLS certificates" entry. Within that there's the domain SSL (including WWW.*) enabled and the wildcard *.domain.tld not enabled. Under "Advanced Settings" one can enabled "Secure Webmail" and "Secure Mail" (and it is), but it still doesn't work.

    Any other workarounds? Thanks.

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hi,

    Under "SSL/TLS certificates" select "Get it free" from let's encrypt and renew certificate with active checkbox "Secure webmail on this domain"

    0
    Comment actions Permalink
  • Avatar
    Gianluca

    Hi, the page https://support.plesk.com/hc/en-us/articles/214528865 show:

    oops

    You're not authorized to access this page

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hi,

    Fixed it, thank you for reporting!

    0
    Comment actions Permalink
  • Avatar
    Mesut Bilgili

    I installed Plesk obsidian on windows 2016 and webmail redirects to ssl , we don't want to redirect ssl. How can we disable redirect to ssl option for all subscription?

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Mesut Bilgili

    Since Plesk Obsidian for security reasons, webmail redirect to HTTPS is always enabled.

    The recommended approach is to get an SSL certificate to secure webmail: https://support.plesk.com/hc/en-us/articles/214528865

    0
    Comment actions Permalink
  • Avatar
    Ericbeck

    Am I to understand that this bug is not fixed yet?  We have very many "email only" plans on one server.  Upgrading to Obsidian soon.  By the sounds of things, I'm going to have to go into every one of the domains, one by one and perform the Let's Encrypt step to secure the webmail.  I guess there would be no way to have this automated, since it would require a script to execute all the steps to secure a let's encrypt cert for each domain (and recognize that there was no hosting) and apply it to the webmail.<domain> automatically.  Is that about the gist of it?  It sounds like it's going to remain a manual task?

    Eric

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles