Recent content by futureweb

Ah, it seems I overlooked the mention of acme.sh . Thank you for sharing that information; it does indeed seem intriguing and worth considering down the line! Regarding the current Plesk Servers Setup, everything seems to be functioning as intended now with the fixer script I've crafted. ("LE" /...

DNS Services are completely disabled on those Plesk Servers, so unfortunately not really working ... Do you have DNS Mgmt active in Plesk and replicate to the external DNS Servers? Or have you integrated your DNS Servers somehow into the Plesk SSL Requests?

as the Forum won't let me edit my posts after 4 Minutes anymore I've made a GitHub for the Script: GitHub - futureweb/Plesk-Postfix-SNI-TLS-Cert-Fixer: SNI-TLS Cert Fixer for mail.dom.tld LE Certs when dom.tld is not pointing to Plesk Server itself. More Information here...

First untested script draft: Question - Issues with SSL Certificate Renewal for Mail Services in Plesk: Seeking Automated Solution via CLI or API

First untested script draft: # Loop through mail.dom.tld domains for domain in $(plesk bin domain --list | grep '^mail\.\|^[^.]*$'); do # Trim "mail." prefix if it exists domain_without_prefix="${domain#mail.}" # Get the SSL/TLS certificate for mail for the current domain...

Hi @learning_curve, I appreciate your response. Unfortunately, wildcard certificates aren't feasible on our Plesk servers due to centralized DNS management, which isn't handled by Plesk itself. However, I've come across a potential solution using the CLI: Issue - Postfix SNI TLS-Certs not...

This forum comment just became our support team's hero, potentially slashing hours from their monthly workload. Taking inspiration from the solution shared here, we're crafting a script to automate SSL certificate renewal for all our mail.dom.tld domains. Running it bi-monthly should keep...

Hello, we are experiencing the following issue with our Mail Only Hostings on Plesk. "dom.tld"/"www.dom.tld" point to a different server, "mail.dom.tld" points to Plesk. Email addresses are set up under dom.tld - for example: [email protected]. In order to obtain an SSL certificate for the mail...

@Peter Debik - I find it quite astonishing that this feature has not yet been incorporated into Plesk. Our support team is currently managing an extensive Excel list containing hundreds of domains, they have to manually renew every three months. This process consumes a significant amount of time...

Hi @AYamshanov , thx for the information and your decision to backport this change to 3.0.x branch! :-)

Hello Peter, I am familiar with the changes that Let's Encrypt (LE) has made as I develop a custom LE client for our company, and I implemented the protocol changes in our client yesterday. The ACME protocol has supported this asynchronous certificate issuance for a long time, and LE has only...

Hello, Unfortunately, some of our customers are still using outdated Plesk servers (including CentOS 6, Plesk: version 18.0.31 Update No. 3). These servers also use LE SSL certificates (from what I have seen, several hundred domains on multiple servers, yes, we are aware that this is a...

@Peter Debik - that's the reason! :-) --> Enabling Asynchronous Order Finalization For now it should work again as LE stopped brownout early - but SSLit Ext. needs to be update to reflect the Protocol change. Hope this helps, bye from Austria Andy

Hi Peter, the feature description in Plesk and your statement contradict each other 180 degrees. ^^ In Plesk, it explicitly states that "only sendmail can be used to send emails from this domain." Therefore, it is explicitly stated that it is purely about SENDMAIL delivery, which does not...

Hi Peter, I am pleased to hear the news, and I have a technical question regarding the change. In your message, you stated that selecting the third option removes all existing mailboxes for the domain, so the second Option won't delete them, right? I would like to clarify what happens to local...