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.

Errors appear on a Plesk server in Apache log: RSA server certificate does NOT match server name

Follow

Comments

8 comments

  • Avatar
    Betafer

    Hello, i got the error and let's encryppt module but i cannot enable the option Secure webmail on this domain because the email is disabled for the subdomain 

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Betafer

    The option in question is available only if webmail is enabled due to business logic.

    Do you have webmail.example.com used just as a subdomain?

    What error does Let's Encrypt show to you?

     

    0
    Comment actions Permalink
  • Avatar
    Betafer (Edited )

    Hello Ivan, subdomain is not SSL Enabled 

    and the error is the same of the topic

    0
    Comment actions Permalink
  • Avatar
    George Alibegashvili

    Hello @Betafer

    In order to address your question more detailed investigation is needed. Can you please create a request to our support team? You can find instructions on how to create a request in the following article:
    https://support.plesk.com/hc/en-us/articles/213608509

    0
    Comment actions Permalink
  • Avatar
    Ralf Störmer

    Hello,

     

    you need to disable this warning with todays update to Version 18.0.31 Update Nr. 3!

    Otherwise Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips will fail to start

    0
    Comment actions Permalink
  • Avatar
    Ekaterina Babenko

    Hello,

    This warning does not affect Apache functionality and it is unlikely it caused failure on restart.
    To be sure I tried to reproduce this behavior in environment similar to yours and it worked smoothly. If you believe it is still the case, submit request to support and we will look into it deeper:
    https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support- 

    0
    Comment actions Permalink
  • Avatar
    Markus

    I also have these "normal" messages [default-123.123.123.123:443:0 server certificate does NOT include an ID which matches the server name], not with domains, but with all IPv4 and all IPv6. Do you have a workaround/fix. Otherwise I don't care about them...Greets

    0
    Comment actions Permalink
  • Avatar
    Pavel Rozental

    Hello,

    Markus , just ignore this warning. It means that there is no valid certificate for "default-123.123.123.123" site.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request