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

Resolved 17.8.11 U2 Certificate not used although it is selected

jamin587

New Pleskian
upload_2018-3-21_22-6-24.png

Securing Plesk is ok, but mailserver uses certificate from domain.

plesk: mail.domain.com:8443 => Certificate for mail.domain.com
mail: mail.domain.com => Certificate for domain.com/www.domain.com/webmail.domain.com

Additionally:
I could only update from U1 to U2 with setting the used Certificate for domain.com to mail.domain.com. Before that there was always an timeout on https://mail.domain.com:8447, with something being wrong with TLS Handshake.
  1. upload_2018-3-21_22-43-15.png
  2. upload_2018-3-21_22-44-23.png
 
More Info
Mailservice is working. But i used Nextcloud to authenticate against smtp by {mail.domain.com:143/imap/tls} which worked with Plesk 17.5.3. I was able to open https://mail.domain.com:443/ too. I now use {mail.domain.com:993/imap/ssl/secure/readonly} and Nextcloud works again.


Ok i found my problem:
The IP address is distributed as: shared instead of dedicated solved https://mail.domain.com:443/ being accessible again
 
Back
Top