• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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. J

    Resolved apt conflict with javascript-common

    I went ahead and did the apt-get dist-upgrade, and it seems to have been successful and I seem to no longer receive this error.
  2. J

    Resolved apt conflict with javascript-common

    I am following the instructions to dist-upgrade from Ubuntu 16 to Ubuntu 18 from here, but I'm getting this same error: The following packages have unmet dependencies: psa : Conflicts: javascript-common but 11 is to be installed E: Broken packages I have tried: apt-get --purge remove...
  3. J

    Question letsencrypt certificate for fourth level domain not served from subdomain

    So far what I have is a cron job that runs this: /usr/local/bin/acme.sh/acme.sh --issue --dns dns_gandi_livedns -d mydomain.com -d *.mydomain.com -d *.subdomain.mydomain.com plesk bin certificate --update "LetsEncrypt wildcard_mydomain.com" -domain mydomain.com -key-file...
  4. J

    Input add external DNS APIs for Letsencrypt extension

    Hello Manuel, so far what I have is a cron job that runs this: /usr/local/bin/acme.sh/acme.sh --issue --dns dns_gandi_livedns -d mydomain.com -d *.mydomain.com -d *.subdomain.mydomain.com plesk bin certificate --update "LetsEncrypt wildcard_mydomain.com" -domain mydomain.com -key-file...
  5. J

    Question Dovecot Shared Folder (ACL)

    I am also interested in knowing a little more about how to set up the ACL plugin for dovecot in a Plesk environment. When I enable the plugin, I then get the following error when trying to run doveadm acl commands: Error: auth-master: userdb list: User listing returned failure doveadm: Error...
  6. J

    Question how to preserve custom roundcube configuration between plesk updates or mail reconfigurations

    sorry it was a typo, it was supposed to be config.inc.php and not custom.inc.php . However in the meantime my configs were overwritten again, and I have also noticed that configs are not always being picked up from config.inc.php, so my hopes are not as high as they were back in April. I guess...
  7. J

    Resolved assign certificate to host from terminal

    Seeing that Letsencrypt wildcard certificates have been given support in Plesk for a while now, I have been however finding that Plesk is not able to automatically renew my certificates because I use gandi.net as my registrar and DNS record holder, and Plesk doesn't use gandi's API, Plesk is...
  8. J

    Question letsencrypt certificate for fourth level domain not served from subdomain

    Yes I have already done this. I am currently making a single request through the acme client which includes two wildcards: example.com *.example.com *.thirdlevel.example.com This is producing a single certificate that covers all subdomains and fourth levels. However having to manually paste the...
  9. J

    Question letsencrypt certificate for fourth level domain not served from subdomain

    I believe I'm making some progress seeing this thread (344076) .
  10. J

    Resolved assign certificate to host from terminal

    If I use a cron job to renew a certificate, I'm guessing I have to: 1) remove the certificate from the domain it's assigned to plesk bin certificate --remove "my certificate" -domain my.domain 2) create a new certificate with the same name under the domain plesk bin certificate...
  11. J

    Question letsencrypt certificate for fourth level domain not served from subdomain

    Well I was able to manually issue a LetsEncrypt certificate using DNS challenge, by making use of the acme.sh client, which supports Gandi LiveDNS along with many many other DNS services with APIs. I issued a certificate for: example.com *.example.com en.thirdlevel.example.com...
  12. J

    Input add external DNS APIs for Letsencrypt extension

    for example, integration of the acme.sh client would be great. I just used it from the command line and it is quite simple, it works very nicely.
  13. J

    Input add external DNS APIs for Letsencrypt extension

    I use Gandi.net's DNS service for most of my domains. I also use wildcard certificates issued by the Letsencrypt extension. However the automatic update of the DNS records with the _acme-challenge only works if the DNS is handled within Plesk, if I understand correctly? Gandi, as many DNS...
  14. J

    Question letsencrypt certificate for fourth level domain not served from subdomain

    I've tried a few things but nothing seems to fix this issue. I tried adding explicit CNAME records for each fourth level in my DNS records: de.thirdlevel 1800 IN CNAME thirdlevel.example.com. en.thirdlevel 1800 IN CNAME thirdlevel.example.com. es.thirdlevel 1800 IN CNAME thirdlevel.example.com...
  15. J

    Question letsencrypt certificate for fourth level domain not served from subdomain

    I have a domain example.com to which a letsencrypt wildcarded certificate is issued. I also have a subdomain thirdlevel.example.com which would have worked theoretically without another certificate, since the main domain is wildcarded. But the subdomain has some fourth levels to designate...
  16. J

    Question how to preserve custom roundcube configuration between plesk updates or mail reconfigurations

    @Heinrich which version of Plesk are you using? I just updated Plesk yesterday from version 18.0.25 to 18.0.26 and I was able to confirm that FINALLY my custom configurations in config.inc.php were kept and are being used. I think maybe this issue has been fixed now, at least in this latest...
  17. J

    Question installing fts-xapian module for dovecot

    Or, other option, I'm thinking of putting up a solr instance which I will probably use for a number of things. I may prefer solr over xapian. Would anyone be able to tell me if the plesk-dovecot package is compiled with the "--with-solr" parameter? And if not, what are the suggested parameters...
  18. J

    Issue Plesk 12.0.8 incorrectly generating /etc/postfix/sasl/smtpd.conf

    I find that this is still happening on Plesk Obsidian. I have tried setting the chroot flag to yes on plesk-sasl in the postfix configuration, but it still didn't work with the relative paths. The only way I can get this to work is to set the chroot flag to no and use full paths.
  19. J

    Question installing fts-xapian module for dovecot

    I see that Plesk is installing a recent version of dovecot (2.3.9.2) on my system with Ubuntu 16.04. I would like to build the fts-xapian module, so I need to install the dovecot-dev package, however I cannot find version 2.3.9.2 of the dovecot-dev package. After enabling the official dovecot...
  20. J

    Question how to preserve custom roundcube configuration between plesk updates or mail reconfigurations

    Well I must congratulate @IgorG and all those working on Plesk, I see it has come a long ways in the past couple years as regards SSL certificates and multiple domain management. I see that now Let's Encrypt certificates can not only be issued per domain, but also wildcarded and set not only for...
Back
Top