• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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 Unable to issue a Let's Encrypt certificate for domain with forwarding hosting type: nginx is not installed or is disabled on the Plesk server

B3 Support

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.69
If you use domain forwarding with Apache, there is a bug for renewing the LetsEncrypt certificates.

Symptoms:
The Forwarding hosting type is set for the domain in Plesk > Domains > example.com > Hosting & DNS tab > Hosting Settings and when trying to issue a Let's Encrypt certificate in Domains > example.com > SSL/TLS Certificates, an error that is similar to the following is shown:
Code:
CONFIG_TEXT:Could not issue a Let's Encrypt SSL/TLS certificate for example.com.
The authorization token is not available at http://example.com/.well-known/acme-challenge/vjcxCwV74PbWUvnMTT2o5MeWP8z0rg054SP_IfIYfXg.
To resolve the issue, make sure that the token file can be downloaded via the above URL.
Details
Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/76408809540.
Details:
Type: urn:ietf:params:acme:error:unauthorized
Status: 403
Detail: Invalid response from https://example.com/.well-known/acme-challenge/vjcxCwV74PbWUvnMTT2o5MeWP8z0rg054SP_IfIYfXg

Please fix this bug with the solution from:
 
Hello, @B3 Support . We have a registered bug with ID EXTLETSENC-920 for the ability to secure domains with "Forwarding" hosting type without Nginx. At this point, I cannot provide an ETA on when a fix will be introduced. You can monitor the change log here.
 
Back
Top