Search results for query: "Let’s Encrypt" "webmail"

Hello, I recently switched from using a paid certificate for the mail server of Plesk to a free lets encrypt one. Now i have the problem that the customers sing webmail are complaining about certificate popups. How can i fix this? Kind Regards, Quinten

Testing new Mailman3 integration on Plesk Obsidian Version 18.0.60, on Debian 12: Dear @IgorG Please improve Plesk and Mailman/Let's encrypt integration. We manage DNS on another server and can not use wildcard LetsEncrypt certificates: make it so lists.<domain> can have have its own LE TLS...

You can issue a separate Let's Encrypt certificate for any subdomain that is routed to the server. What exactly does not work for you here?

I'm sorry, but I'm not a Plesk employee.

Hello, I was having some problems with SSL certificates (a different thread) and for a single domain generated Let's Encrypt without a webmail certificate. I want to have all the domains with common certificate formats, e.g I choose webmail.example.com and www.example.com and example.com. I was...

Hello, thank you for replying. We are in a situation where we do host Mailman mailing lists for customers whose web site and email are hosted on other servers. I'm currently testing Plesk implementation of Mailman3 on Debian 12. When I go to generate a Lets Encrypt certificate for the domain I...

We're on Ubuntu NOT AlamaLinux (caveat) but, assuming, that you're referring to Let's Encrypt SSL Certificates: Is the Let's Encrypt SSL Certificate that covers dom.tld a TLD only Certificate, NOT a Wildcard or SAN Certificate that also fully covers the sub-domain mail.dom.tld and/or any other...

My domain has a valid SSL certificate from Let's Encrypt. I have used the wildcard specification to generate a certificate. However no matter what I try I the webmail does show as protected in Plesk, but the server is not providing the certificate when I access webmail.domain.com Issued...

I'm trying to set up webmail in one of my domains, but neither horde nor roundcobe works. Both tell me connection to webserver fails. some facts: webmail.my.domain is secured with LetsEncrypt, the config of i.e. roundcube looks like this: $config['imap_host'] = 'ssl://localhost:993'; // IMAP...

@tkalfaoglu @AYamshanov I solved it, thanks. The old SSL certificate expired on March 3 and renewed on the 5th. It was subsequently installed again in Plesk for all subdomains. What I didn't do (and I don't remember reading it in the documentation) is that I then have to go into "Domains / Mail...

See a solution / workaround for this here: Change Log for Plesk Obsidian It states: The gist is that if there's some kind of failure with general renewal (such as a firewall block preventing access to one of the many Let's Encrypt servers as described above), Plesk would try excluding the www...

When issueing a Let's Encrypt certificate you can check or uncheck the www subdomain. You can create such a cert for the domain only. It is possible, too, to only create it for Webmail. What checkboxes have you checked on the certificate creation dialog page?

@hansitheking (and @Peter Debik), In essence, there is a question unanswered here : @hansitheking , do you use an external DNS provider? Although the answer is relevant, the general comments to the issue are not dependent on the answer. In general, it is correct to state that the SSLit and...

Please click "Detaggli" for more information. I assume that the "webmail" subdomain is not routed to your server, because from the other part of the screenshot it can be seen that the domain itself is not routed to the server. Domainvalidated certificates can only be issued if the domain is...

Yes. That ^ domain's current config / setup for the Let's Encrypt Certificate itself looks fine (in isolation...) However, settings at the level above this (Server / Plesk Mail etc) are also a major factor. Assuming that you're using Roundcube for Webmail, that iss IMAP based, hence your...

I don't know how your previous provider did this, maybe he had a special piece of software on his systems or was using one of the extension-supported DNS services ("DNS integration for Cloudflare®", "DigitalOcean DNS", "Amazon Route53"). In general, Let's Encrypt certificates need to be renewed...

If you've completed those checks, that's all good, but that's not specifically relevant to you not being logged in to IMAP (yet) on that domain. There ^ you're ensuring that on that specific domain, you are going to use a chosen, specific certificate for both Mail and Webmail (this is also...

Hi, I have setup a Hetzner dedicated server with Plesk/AlmaLinux combination. I've setup so far one no hosting domain that is used just for mailing purposes and several others that are website domains. The certificates for securing Plesk server (the hostname used in the keep Plesk secured...

Hello, Instead using the subdomain mail you can use webmail and configure this option for your domain. Using all others subdomain except webmail is not possible with let's encrypt with Plesk, this is a well-known big problem, we have for example lists.example.ext and mailman. Best Regards AR

By default it seems that Let's Encrypt will only secure the main naked domain, www and webmail, as per my first screenshot-1 However, our situation is different and we need to Wildcard secure all domains by default (when created) and then assign the certificate to the mail domain, as per...