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

Search results

  1. I

    Resolved Lots of DKIM/DMARC errors - mails are rejected

    @TorbHo, set your DMARC policy to none or quarantine, then send a message to another mail service (which should be delivered with a DMARC policy of 'none') and inspect the header. As @Sebahat.hadzhi said, you likly have a domain conformance failure, probably due to you setting the 5322.From...
  2. I

    Issue Mail delivery deferred (4.4.2 delivery temporarily suspended)

    Ah ... I knoew it. As soon as I post, I'll find the fix... I recall in the rapid migration, SpamAssin is no longer availe and I presume has been incorporated into Plesk Email security. I therefore looked at Warden Anti-spam and Virus Protection, but didn't go through with licensing it. All has...
  3. I

    Issue Mail delivery deferred (4.4.2 delivery temporarily suspended)

    Mail stopped being delivered on our Plesk server in the early hours of this morning with: Looking through KB articles, I have... Restarted Dovecot and Postfix milter and SMTP via Tools & Settings > Services Management and requeued all mail ... failed Restarting amavisd and postfix and...
  4. I

    Question Renewing Let's encrypt automatically

    I can confirm, cert rotation with wildcard deselected now goes not only without challenge, but oh so quickly. You have just saved me a bunch of time. Thank you so much @Kaspar :cool:
  5. I

    Question Renewing Let's encrypt automatically

    Hi @Kaspar ... so it is the wildcard option that triggers the _acme.challenge update at every cert rotation? If that's the case, it will save me a lot of hassle. Plesk/SSL It! like to 'encourage' including the wildcard option, but if ignoring this removes the need for TXT record update each...
  6. I

    Issue Let's Encrypt "urn:ietf:params:acme:error:caa" 403 failure

    I have been trying all manner of things @mow :) What's more, I have some interesting findings and questions for Plesk... I have indeed set CAA for the various domains, however, and yes as a CISO I recognise you 'best practice' point, CAA are not required and both these 'problem subscriptions'...
  7. I

    Issue Let's Encrypt "urn:ietf:params:acme:error:caa" 403 failure

    This issue is back and looking for anyone reporting this issue I find my own post :rolleyes: What I notice is that I mention two subscriptions having this 'checking CAA' error ... both for domains that have no CAA and never have. I also see I said... Well, the same 1+5 subscription is back to...
  8. I

    Issue Let's Encrypt "urn:ietf:params:acme:error:caa" 403 failure

    This is maybe relevant... Type: urn:ietf:params:acme:error:caa Status: 403 Detail: Error finalizing order :: Rechecking CAA for "www.sprakekingsley.org.uk" and 14 more identifiers failed. Refer to sub-problems for more information Why relevant? Well, the request is for the root and wildcard...
  9. I

    Issue Let's Encrypt "urn:ietf:params:acme:error:caa" 403 failure

    Just to add to the thread, but not expecting a magic answer, other subscriptions on the same host all update okay, even now, one that was suffering the same 'urn:ietf:params:acme:error:caa' 403 error. Trying to work out what is the key issue, although I cannot see why one that was failing, is...
  10. I

    Issue Let's Encrypt "urn:ietf:params:acme:error:caa" 403 failure

    Many thanks Peter. Yes, I understand a 403, but it's not just "can't access", but is being forbidden .. it's a 403, not a 404. I'll have a look at the logs and maybe put a tail on while an attempt to reissue is running in the hope of seeing what it is that's being attempted and denied.
  11. I

    Issue Let's Encrypt "urn:ietf:params:acme:error:caa" 403 failure

    Hi Peter, no, nothing in front and Nginx disabled just to rule that out. No, DNS is not managed by the Plesk service and yes I know where the autorotative DNS are and it all been working for years. Yes I have checked the DNS for all names and one idea I followed was a misreading of an wildcard...
  12. I

    Issue Let's Encrypt "urn:ietf:params:acme:error:caa" 403 failure

    Just to add to my own thread... I took the smaller 1 + 5 domain subscription I de-selected all the additional domains and tried again ... it still failed I then de-selected wildcard and when to domain and www.domain options only ... it worked! ... however... While the 'domain + www only' v...
  13. I

    Issue Let's Encrypt "urn:ietf:params:acme:error:caa" 403 failure

    There seems to be numerous items about: Details Invalid response from https://acme-v02.api.letsencrypt.org/acme/finalize/356300830/211673632166. Details: Type: urn:ietf:params:acme:error:caa Status: 403 Detail: Error finalizing order :: Rechecking CAA for "example.com" and 18 more identifiers...
  14. I

    Resolved Expired SSL certificate keeps showing

    @learning_curve, maybe you have an insight to an issue I see and which I see others log as an improvement request with Plesk ... I have an expired default cert that refuses to go away! These are all Let's Encrypt certs which I rename as "FQDN from_date to end_date" ... it helps to know what...
  15. I

    Issue Let's Encrypt and "Assign the certificate to mail domain" problems and AutoDiscovery issues caused by this

    first4it, I think "Can we please have some information on this?" is just DerDanilo being very polite in asking for a response. As you say, it is a very well researched and described issue. I came here having noted the "Assign the certificate to mail domain" option and wondering how it knew which...
  16. I

    Question Problems with Email certificate renewal - seems linked to changes in SNI support

    This morning I ran into issues with the TLS cert on mail. The mail services – Dovecot + Postfix are secured with Let’s Encrypt certs issued by Plesk, although for some reason I sometimes need to come into the Home > Tools & Settings > SSL/TLS Certificates panel and use the ‘+ Let’s Encrypt’...
  17. I

    Question Updating OS components without breaking Plesk

    Many thanks @Ales. That pretty much was my thinking, but good to get an experience d review. The last thing I want to do is build an unsupportable system, especially as I'm running Plesk deliberately so as to not get into those complexities. I think it was the ISP though that advised me not to...
  18. I

    Question Updating OS components without breaking Plesk

    I understand Plesk's position is that packages like OpenSSL are a part of the base OS and so not updated by Plesk, but conversely I've been advised it is better not to update the server via yum so that OS updates are in line with Plesk support. So maybe the first question to ask is: Do Plesk...
  19. I

    Question How can I update SpamAssasin version for Plesk

    Getting SpamAssassin up to date would be good as we all suffer too much spam, but I was a little surprised to see the comment that this is an OS package and so outside the scope of Plesk. I thought the entire purpose of Plesk was to make server admin (much) simpler and that pretty much all the...
  20. I

    Question cron will not run working Bash script

    So I found a Plesk article; "How to extend chrooted environment with additional commands" (How to extend chrooted environment with additional commands) which seemed promising, however, the provided <recreate_chroot_env> script doesn't work on my CentOs 7 system: [root@at chroot]#...
Back
Top