Looking for help in installing or hosting Plesk? Or want to migrate a Parallels Confixx server to Plesk? At Infiniroot we've helped our existing customers on exactly these topics. With this config update in place and Nginx reloaded, the HTTP challenge from the Let's Encrypt API finally works (response status 200):ġ8.159.196.172 - "GET /.well-known/acme-challenge/M_BJMgIt3IawUTTYSczKE5nKGwdR_cGG0x_5GEVVT5s HTTP/1.1" 200 87 "-" "Mozilla/5.0 (compatible Let's Encrypt validation server +)"ģ.19.56.43 - "GET /.well-known/acme-challenge/M_BJMgIt3IawUTTYSczKE5nKGwdR_cGG0x_5GEVVT5s HTTP/1.1" 200 87 "-" "Mozilla/5.0 (compatible Let's Encrypt validation server +)"ĥ2.39.4.59 - "GET /.well-known/acme-challenge/M_BJMgIt3IawUTTYSczKE5nKGwdR_cGG0x_5GEVVT5s HTTP/1.1" 200 87 "-" "Mozilla/5.0 (compatible Let's Encrypt validation server +)"Ħ4.78.149.164 - "GET /.well-known/acme-challenge/M_BJMgIt3IawUTTYSczKE5nKGwdR_cGG0x_5GEVVT5s HTTP/1.1" 200 87 "-" "Mozilla/5.0 (compatible Let's Encrypt validation server +)"Īnd in Plesk the certificate was successfully created! Professional Plesk and Confixx consulting Click Install (or Renew if the domain is already secured with a Let’s Encrypt certificate). This tells Nginx to use the file system path /var/in the URI. Go to Tools & Settings > SSL/TLS Certificates (under Security). Select the Issue wildcard certificate checkbox and select the domain aliases you also want to secure (if any). Important here is the location /.well-known/ path in the plain http section. This can be verified with curl:Īlias /var/www/vhosts/default/htdocs/.well-known/ Nginx receives the request but then responds with the redirect (302) to port 8443. The Let’s Encrypt extension can automatically keep hosted websites secured with free, trusted SSL/TLS certificates from Let’s Encrypt. Mailboxes, Websites, databases and Letsencrypt. By default, new Plesk installations come with pre-installed Lets Encrypt extension and if the servers hostname is correct, Plesk secures itself automatically. I migrated only 2 domains from an older Starto V-Server with Ubuntu 14.04 and Plesk 12.5 to test the migration. However, from February 2022, Let’s Encrypt on Plesk will be converted into a plugin for the SSL It Extension. I ordered a new Strato V-Server with Ubtuntu 16.04 LTS and Plesk Onyx 17.8 (Web Pro edition). Let’s Encrypt is an SSL solution offered by Plesk. By enabling the access logs, the requests can be seen:ģ.120.130.29 - "GET /.well-known/acme-challenge/tE36pZxx5vCnK_3RuMg5NZRMVWzggaMkyvKjFeuk30Y HTTP/1.1" 302 138 "-" "Mozilla/5.0 (compatible Let's Encrypt validation server +)"ĥ2.39.4.59 - "GET /.well-known/acme-challenge/tE36pZxx5vCnK_3RuMg5NZRMVWzggaMkyvKjFeuk30Y HTTP/1.1" 302 138 "-" "Mozilla/5.0 (compatible Let's Encrypt validation server +)" Converting Let’s Encrypt from a standalone extension into a plugin for SSL It. But this redirect now causes problems when the Let's Encrypt verification API tries to validate the domain. The redirect makes sense, especially for the (mostly not tech-savvy) customers of this Plesk server. In this particular setup, a global redirect for the Plesk domain exists in /etc/nginx/conf.d/:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |