The newer hosted servers support Let's Encrypt "SSL" encryption. This can be a benefit for SEO as well as providing additional security.
The way it is implemented in shared hosting, Let's encrypt uses site verification. This is done by let's encrypt making a connection to a verification file in the website. For the certificate issuance to work, that file must be accessible without SSL.
The path is like the one below
<www.mysite.co.nz>/.well-known/acme-challenge/
It's important that the site is configured so that this path can be reached, and sometimes modifications to the web.config file are required to ensure this.
The below config snippet may assist in creating a HTTPS redirect along with allowing the Lets encrypt certificate renewals to work.
--web.config file
<rules>
<clear />
<rule name="EasyCrypt Exception" stopProcessing="true">
<match url="(.well-known/*)" />
<conditions logicalGrouping="MatchAll" trackAllCaptures="false" />
<action type="None" />
</rule>
<rule name="HTTP to HTTPS redirect" stopProcessing="true">
<match url="(.*)" />
<conditions>
<add input="{HTTPS}" pattern="off" ignoreCase="true" />
</conditions>
<action type="Redirect" url="https://mywebsite.co.nz/{R:1}"
redirectType="Temporary" />
</rule>
</rules>
Comments
0 comments
Article is closed for comments.