• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Question Create an SSL certificate with Let's Encrypt for a second domain with the same physical directory.

khunochan

New Pleskian
Context:
We Have Plesk Onyx Version 17.8.11 and IIS v10 on Windows Server 2016.

- We create store1.com with Plesk (store1.com), with this binding in IIS:
- HTTP store1.com 80
- HTTP www.store1.com 80
- HTTPS store1.com 443
- HTTPS www.store1.com 443
HTTPS with SSL with Let's Encrypt... all good so far.
and its physical directory: C:\inetpub\vhosts\store1.com.

And we create, also with Plesk, a second store (store2.com) with his domain, but in IIS we bind on store1.com this:
- HTTP store2.com 80
- HTTP www.store2.com 80
- HTTPS store2.com 443
- HTTPS www.store2.com 443
with this physical directory: C:\inetpub\vhosts\store2.com
Because we want to use the same website with this new domain (store2.com) (nopcommerce can have more than one store on the same site)
Works fine.

The problem:
Now i try to put SSL with Let's Encrypt but the Let's Encrypt Extensions writes the challenge file on C:\inetpub\vhosts\store2.com\httpdocs\.well-known\acme-challenge, but the URL for the challenge
http://store2.com/.well-known/acme-challenge/[TOKEN]. it's in C:\inetpub\vhosts\store1.com\httpdocs\.well-known\acme-challenge

There is a way to change the physical directory for the store2.com on Plesk to the store1.com physical directory?
So that Let's Encrypt Extensions write the challenge file in the physical directory of store1.com.
 
Last edited:
Back
Top