• Inviting everyone who uses WordPress management tools in Plesk
    The Plesk team is conducting a 60-minute research session that includes an interview and a moderated usability test.
    To participate, please use this link .
    Your experience will help shape product decisions and ensure the tools better support real-world use cases.

Recent content by BuzzLightBurger

  1. B

    Issue Plesk 18.0.70 and Could not issue/renew Let's Encrypt certificates

    Some per-requisites I've seen re Plesk and Let's Encrypt.. If your server has both ipv4 and ipv6 addresses, LE will use the ipv6 so ensure all AAAA records are created in addition to any ipv4 A records. If your existing SSL does not include www (or a wildcard) then ensure the preferred domain...
  2. B

    Question Spam Folder Location

    Hi Both servers have the same contents in the dovecot.conf file, with the namespace matching the code quoted above. I wasn't specifically referring to the learning, but that too. I was referring to the movement of mail to a spam folder at the server side (rule in the mail accounts) Regards
  3. B

    Resolved 421 Misdirected Request on IP address after Apache update

    Running U20.04LTS and the latest Plesk with the Apache mod applied, the default site set on the (shared) primary IP address (ionos vps) works fine, albeit with an SSL warning as the cert is for the domain name and not the IP. (it's the correct cert and site that opens though). Proxy mode is...
  4. B

    Question Spam Folder Location

    Hi Quick Q. It was my understanding that Plesk moved the default location of the Spam folder to within the inbox (Inbox.Spam) to make it more compatible with other extensions like SpamAssassin, but after setting up a new Ubuntu 24.04 server running the latest Plesk/Roundcube etc, the Spam folder...
  5. B

    Resolved 421 Misdirected Request

    I looked at this code in another thread and it looks like it maps the xml/config files for each vhost domain as I'm using PPE but all my domains use the server's domain name for webmail and have no issues (aside from the repair I needed to do on the SQL following a kolab/roundcube upgrade the...
  6. B

    Resolved 421 Misdirected Request, Activesync no longer working

    Hi I'm glad you found a solution :) Looking at the solution, it would seem that you're not using the default domain name of the server with its webmail subdomain and are requiring to route each domain's webmail subdomain following the Apache mod in order to resolve the correct xml files for...
  7. B

    Resolved 421 Misdirected Request, Activesync no longer working

    I hope that at least gets you back up n running.. It's strange that the Apache SNI error is clearly causing this and the nginx sslfix isn't helping (unless nginx isn't being used on the domain, would that make a difference?)
  8. B

    Resolved 421 Misdirected Request, Activesync no longer working

    I was going to edit the above, but I cant :/ Also, open this in your browser with valid details to see if you get any XML back https://mydomain.tld/mail/[email protected]
  9. B

    Resolved 421 Misdirected Request, Activesync no longer working

    Although this won't help you with your server, have you looked at the following to ascertain the data being exchanged with the server from outlook? https://www.codetwo.com/admins-blog/how-to-quickly-verify-if-autodiscover-is-working/#using-outlook Although you're using (or trying to) the auto...
  10. B

    Resolved 421 Misdirected Request, Activesync no longer working

    When you visit webmail.domain.tld does that work without any errors being added in the log. Can you see anything in the Settings > ActiveSync section of the webmail account you use AS with? Be careful when using domain names during account setup if you've asked the server to rewrite a URL from...
  11. B

    Resolved 421 Misdirected Request, Activesync no longer working

    Yup, your entire problem is that 421 that hasn't been resolved by applying either the patch or the Plesk update :( Are there any additional directives in the Apache/NGINX settings for the domain? The domain I repaired overnight relies on both Apache and NGINX, running both the original patch...
  12. B

    Resolved 421 Misdirected Request, Activesync no longer working

    Check the domain's nginx log for any entries related to a client connecting to AS. Filter by "ActiveSync". You should at least see some POST requests reaching the server. If not, then the client might need inspection (a firewall on the client computer or possibly on the server)
  13. B

    Resolved 421 Misdirected Request, Activesync no longer working

    & if that doesn't work, check the error log for ActiveSync here: /var/log/kolab-syncroton/errors.log I had my own dramas on a 20.04 LTS server after updating kolab/roundcube resulting in missing columns in the roundcube SQL database (was causing 500 errors in the domain's NGINX log for both...
  14. B

    Resolved PPE - repository GPG Error

    Ditto..The GPG error resolved itself and following an update / upgrade the server installed the latest kolab / roundcube. One small issue though, the kolab and roundcube upgrade broke my Plesk Premium Email ActiveSync :( Attempts by the mail client were met with NGINX 500 errors for both sync...
  15. B

    Resolved PPE - repository GPG Error

    The result of that command :( root@server:~# apt-key adv --keyserver keyserver.ubuntu.com --recv-keys C8B3DA4DF6491D3D Executing: /tmp/apt-key-gpghome.ealtRK3qJC/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys C8B3DA4DF6491D3D gpg: keyserver receive failed: No data
Back
Top