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

Issue Lets Encrypt - error in certificate renew process

Nobody has claimed that. It doesn't help to make accusations here.
Why would anyone want to do that?
You already mentioned that.

This is how it looks on my private server, but on all other 50 Plesk servers too

Code:
    location ^~ /.well-known/acme-challenge/ {
        root /var/www/vhosts/default/htdocs;

        types { }
        default_type text/plain;

        satisfy any;
        auth_basic off;
        allow all;

        location ~ ^/\.well-known/acme-challenge.*/\. {
            deny all;
        }
    }

You could check whether the route for http traffic is the same as for https traffic.
is exactly the same route
Are you using a proxy like Cloudflare? Could the issue be linked to port-related setting there?
We don't use that and no
Do you have any individual Nginx or Apache configuration directives in effect in your domain ("Apache and Nginx Settings")? These could take precedence over the default 301 in the "server" bracket of nginx.conf of the domain.
no, no individual settings have been made here
 
If you cannot find out where a redirect is done with the requirement of a working certificate, the best option will be to submit a support ticket to Plesk support so that an engineer can check it on your server why this happens.

i couldnt find anyone who could post a successful automatic lets encrypt renewal.
@t.echternach-weber The normal behavior is that certificates can be renewed without issues, with or without SSL redirect "on".
 
Back
Top