• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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