• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Let's Encrypt Error 400 on every domain

RingoStar77

Basic Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
18.0.64
Hi!

I have switched to a new server recently. I restored a full backup and every website is up and running. But something seems to be different as I cannot manage to reissue Let's Encrypt certificates. This is happening for every domain on the server. DNS entries are managed through an external provider (ipv4 and ipv6) I've also removed bind dns extension in plesk.

It seems like the server is generally redirecting all requests to HTTPS, which is causing the problem. I have activated the SEO-friendly 301 redirect for each domain. But why does this also apply to the server globally? Unfortunately, I don't know where I can deactivate this.

When the backup was not yet restored, a customised maintenance page should have appeared. But even there it was already redirected to HTTPS and therefore the page was not available because no certificate was present at this time.
 
Hey, @RingoStar77. I am afraid, I cannot completely understand what exactly the issue is. If the issue is with the Let's Encrypt installation failure, please provide us with the full error message you are encountering. If the HTTPS redirection is your concern, what I can think of is having custom Apache/NGINX directives configured to force the HTTPS redirection.
 
Back
Top