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

Resolved Lets Encrypt using hosts file (on domain not live) for testing

larryk

Regular Pleskian
hi is it possible?

i'm on
Plesk Onyx
Version 17.0.17 Update #28, last updated on June 16, 2017 03:20 AM

my site is not live (no DNS pointing), but have site running in plesk.
I'm testing it to make sure all is good and https works, BUT how to test https, if site is not LIVE yet?
I added the dedicated IP and domain to my host file... so the domain 'appears' to be live... but i guess it can't work?

I got this error when I tried it :)



Error: Let's Encrypt SSL certificate installation failed: Challenge marked as invalid. Details: Invalid response from http://mydomainname.com/.well-known/acme-challenge/bPzzD4Gn0l5sT5fdinDtANO9Eus1f32np8yuGEMGezc: "

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

"
 
Let's Encrypt will only issue certificates for domain names, not for IP addresses or fo unregistered domain names. So to get a Let's Encrypt certificate, you should register a domain name and then request a certificate for that name. Domain name should be resolvable.
 
Back
Top