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

Question About updating certificate of Let's Encrypt

Zoo3

Regular Pleskian
I use an application called Mattermost. Since this application can not be managed by Plesk and made it function, nginx etc directly edit nginx.conf and operate Mattermost. But Let's Encrypt uses Plesk's Let's Encrypt. *It is not externally installing it separately.
The program itself is put in a different place by proxy_pass and port. That is outside the site.


In this state Let's Encrypt certificate can not be updated.
" Error: Could not issue Let's Encrypt SSL/TLS certificate of SITE-URL.
You can not use an authentication token with SITE-URL/TOKEN.
In order to solve this problem, please be able to download the TOKEN file from the above URL."
I will display "404 Not found" when accessing that site. When I look at the server, the file itself exists in that location.


I tried the troubleshooting below, but I could not.
Troubleshooting failed Let's Encrypt certificate installation on Plesk domain

It could not be done by the following method either.
I wrote the following in nginx.conf or Plesk's nginx additional directive.
# ACME challenge
location ^~ /.well-known {
allow all;
default_type "text/plain";
try_files $uri =404;
}
location ^~ /.well-known/acme-challenge/ {
allow all;
}

It is my imagination. I think this is an event unique to using Plesk. When trying to check a well-known directory, will it be redirected to Mattermost(place)?

Is there a way to update the certificate?
 
After that I understood. I disabled the permanent 301 redirect setting in Plesk's hosting settings, and it was possible to automatically update the Let's Encrypt certificate.
About this permanent 301 redirect. If this setting can't be done, the user is required to input "https://".
Is there a workaround for this?
 
Back
Top