NopCommerce 4.00+ uses rewrite rules to create an additional 'wwwroot' directory under the website which confuses the Plesk Let's Encrypt module. Therefore, in order to use Let's Encrypt with NopCommerce 4.00 or Greater on Plesk, we will need to create some rewrite rules that will allow the SSL module to find the verification tokens.
The first step is to try and issue a Let's Encrypt certificate via the Plesk Control Panel.
NOTE: Make sure you have SSL/TLS enabled under the website you are trying to issue the certificate.
After logging into the Plesk control panel navigate to and click Websites & Domains in the side navigation bar. On the Websites & Domains page, you'll see a list of the domains hosted through your hosting account.
Simply click Hosting Settings on the domain you are working with. If you forgot your Plesk control panel login you can find that information in the Welcome Email we sent to you when you first signed up. You can also view that email in the Email History section of your billing dashboard.
Then under Security, make sure SSL/TLS support is enabled.
Go back to Websites & Domains and click the Let's Encrypt icon and attempt to issue the certificate with default options and you will get the failed notification. We need to do this step so that the server creates the correct folder structure for the authentication tokens.
Once that's completed, click on Files from the left-hand navigation menu and drill into the 'httpdocs' folder. You will find a folder called .well-known, drill into that and the next folder acme-challenge, drill into that. Finally, you will see the web.config which we need to click again to edit and add the following rewrite rules overwriting anything currently within the web.config.
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<rewrite>
<rules>
<clear />
<rule name="block" stopProcessing="true">
<match url="(.*)well-known/acme-challenge/(.*)" />
<action type="None" />
</rule>
</rules>
</rewrite>
<handlers>
<clear />
<add name="StaticFile" path="*" verb="*" type="" modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule" scriptProcessor="" resourceType="Either" requireAccess="Read" allowPathInfo="false" preCondition="" responseBufferLimit="4194304" />
</handlers>
<validation validateIntegratedModeConfiguration="false" />
<staticContent>
<mimeMap fileExtension="." mimeType="text/json" />
</staticContent>
</system.webServer>
<system.web>
<authorization>
<allow users="*" />
</authorization>
</system.web>
</configuration>
Once that's completed, go back and proceed to issue the certificate once again and it should work fine this time. Moving forward, if you republish your website with FTP or Visual Studio make sure you do not delete the .well-known folder as will lose your changes and your Let's Encrypt certificate will not renew automatically. If you have any issues, please contact us for further assistance.
Please note, Let's Encrypt cannot issue SSL Certificates to any domains or subdomains that are not resolving to the server. You will need to make sure to update your domain's or subdomain's nameservers or A record to point to your server at PeoplesHost.
Looking for reliable Windows hosting with Award Winning Customer Support?
Grab your hosting today with a 20% discount. All plans come with our 60 Money Back Guarantee!
Check out our plans & promotions on our website -- https://www.peopleshost.com/
