• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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