[FIXED BUG] Unable to issue Let's Encrypt certificate: Your domain in Plesk is hosted on the IP address(es): 192.0.2.2, but the DNS challenge used another IP address: 203.0.113.2.

Follow

Comments

2 comments

  • Avatar
    Fouad Ahmed Fouad

    I have the web sites hosted on another server, and webmail.example.com can't be secured because Plesk can't issue the SSL as the web site is not hosted on the same server, why Plesk doesn't automatically try DNS challenge instead of using the web site to identify the domain in question, so we can still secure the webmail and SMTP services, can you help?

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Fouad Ahmed Fouad

    Thank you for sharing your user experience.

    This approach was the one used by Let's Encrypt. DNS challenge was added only with introduction of Wildcard certificated by Let's Encrypt not long ago.

    Consider creating a feature suggestion at Plesk user-voice.

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request