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

    Resolved Failed to update Plesk. To solve this problem, you can send the update log to Plesk support

    Plesk tried to do an auto update? https://pastebin.com/raw/b3fzvw0g
  2. X

    Issue My websites won't run

    OS: ‪Ubuntu 16.04.6 LTS‬ Product: Plesk Onyx 17.8.11 Update #58 last updated at June 26, 2019 04:15 AM
  3. X

    Issue My websites won't run

    "Checking whether to disconnect long-running connections" Everytime one of my other websites is running. So for example if I go to domain1, then it launches with that message and disconnects domain6
  4. X

    Issue Plesk restarts all Node services

    I run about 5 node web servers on a dedicated server, everytime I update the website (by pulling the updates off Git and then restarting the node service) instead of restarting that specific website it restarts all. The issue is that it's incredibly slow and uptime is really important to my...
  5. X

    Resolved Let's Encrypt Wildcard, is set for the wrong domain

    Thank you so much! This ended up fixing it. Basically no certificate was selected for *.domain.net Thank you! :)
  6. X

    Resolved Let's Encrypt Wildcard, is set for the wrong domain

    For the first question, the domain name that I'm using is my .com domain. But even if I change it to my .net domain, wildcard certificates do not work. I've tested wildcard certificates on my .com and .net domain. Changing the hostname does seem to fix the error. The only change though is that...
  7. X

    Resolved Let's Encrypt Wildcard, is set for the wrong domain

    Also subdomain Let's Encrypt certificates are working, it's only wildcard certificates that do not work. Which is the feature that I need
  8. X

    Resolved Let's Encrypt Wildcard, is set for the wrong domain

    Sorry, for the third question, I am using the same IP Addresses for all of my domains. Basically what I want is to be able to use wildcard certificates for my .net domain. I just tried adding a wildcard certificate to the .com domain to see if it'll work, but that's not working either. I get a...
  9. X

    Resolved Let's Encrypt Wildcard, is set for the wrong domain

    If I change the hostname to my .net domain and request a new certificate, it doesn't change anything. Just says the same error, but instead says it with my .net domain (which means wildcard certificates still don't work)
  10. X

    Resolved Let's Encrypt Wildcard, is set for the wrong domain

    This is the error I get, and in Plesk these are the options I had set. I don't know why wildcards are not working....
  11. X

    Resolved Let's Encrypt Wildcard, is set for the wrong domain

    OS: ‪Ubuntu 16.04.5 LTS‬ Product: Plesk Onyx 17.8.11 Update #36 , last updated at Jan 17, 2019 07:36 AM
  12. X

    Resolved Let's Encrypt Wildcard, is set for the wrong domain

    So I changed the reverse dns to abc.tld, but it is still assigning the SSL to xyz.tld
  13. X

    Resolved Let's Encrypt Wildcard, is set for the wrong domain

    One thing that I also notice is that when I ping abc.tld, it shows as PING abc.tld (xxx.xx.xxx.xxx) 56(84) bytes of data. 64 bytes from xyz.tld (xxx.xx.xxx.xxx): icmp_seq=1 ttl=49 time=30.9 ms 64 bytes from xyz.tld (xxx.xx.xxx.xxx): icmp_seq=2 ttl=49 time=24.8 ms 64 bytes from xyz.tld...
  14. X

    Resolved Let's Encrypt Wildcard, is set for the wrong domain

    Yeah it's a really weird issue to explain. Essentially I enabled Let's Encrypt wildcard certificates using this: How to install wildcard certificates with Let's Encrypt? After enabling it, I want to add wildcard certificates for my domain abc.tld , but instead it issues the certificate to...
  15. X

    Resolved Let's Encrypt Wildcard, is set for the wrong domain

    Let's Encrypt Wildcard certificates are being set for the wrong domain, how can this be resolved? I get a connection not secure page, because it's being set for a different domain of mine.
  16. X

    Resolved Emails not immediately showing up in inbox

    Yup that fixed it thank you :)
  17. X

    Resolved Emails not immediately showing up in inbox

    Hello I am having an issue with emails, they used to immediately show up in my inbox, but sometimes they now take over an hour in order to show in Roundcube or Thunderbird. When I check MagicSpam, it shows that the email was received and displays it as HAM so it can't be getting rejected (plus...
Back
Top