Hello,
I am trying to figure out how to add the `www` second-level domain to my
sourcehut pages custom domain website.
I am using the command `tar -cvz index.html > site.tar.gz` to package the
tar and `hut pages publish -d niktivan.org site.tar.gz` to publish it.
The site works fine at niktivan.org.
I have further added the following CNAME record to my registrar's DNS config
as per https://srht.site/custom-domains:
CNAME Record www pages.sr.ht.
If I visit www.niktivan.org I get the following:
```
An error occurred during a connection to www.niktivan.org. Peer reports it
experienced an internal error.
Error code: SSL_ERROR_INTERNAL_ERROR_ALERT
The page you are trying to view cannot be shown because the authenticity
of the received data could not be verified.
Please contact the web site owners to inform them of this problem.
```
I am not sure which part I have set up incorrectly.
Thanks for any help!
On Wed May 3, 2023 at 2:39 AM CEST, Ivan - ivan at niktivan.org wrote:
> Error code: SSL_ERROR_INTERNAL_ERROR_ALERT
That's the error returned by caddy while it's fetching a certificate. Nothing
to worry about. Just try again later.
--
Moritz Poldrack
https://moritz.sh
Hi Ivan,
On May 3, 2023 2:39:58 AM GMT+02:00, Ivan <ivan@niktivan.org> wrote:
>Hello,>>I am trying to figure out how to add the `www` second-level domain to my>sourcehut pages custom domain website.>>I am using the command `tar -cvz index.html > site.tar.gz` to package the>tar and `hut pages publish -d niktivan.org site.tar.gz` to publish it.>>The site works fine at niktivan.org.>>I have further added the following CNAME record to my registrar's DNS config>as per https://srht.site/custom-domains:>>CNAME Record www pages.sr.ht.>>If I visit www.niktivan.org I get the following:>>```>An error occurred during a connection to www.niktivan.org. Peer reports it>experienced an internal error.>>Error code: SSL_ERROR_INTERNAL_ERROR_ALERT>> The page you are trying to view cannot be shown because the authenticity>of the received data could not be verified.> Please contact the web site owners to inform them of this problem.>```>>I am not sure which part I have set up incorrectly.>
The error is caused by the SSL/TLS certificate generated. Because you publish your site as niktivan.org, the certificate auto generated is for niktivan.org only. When you try to access as www.niktivan.org the certificate does not match the name of the site and raises an error (you should have a certificate for www.niktivan.org instead).
IIRC this is an expected limitation. One workaround is to publish your site twice, once with each name, or to add a redirect from one name to the other (www -> blank or the other way around). For the redirect you'd have to set it up with an html page published in the other name, like explained here: https://stackoverflow.com/questions/5411538/how-to-redirect-one-html-page-to-another-on-load#5411567
Regards,
Miguel
Hi,
I published twice and everything works now.
Thank you everyone for the help!
The HTML redirect also works, thanks for that info.
--
Ivan Nikitin
https://niktivan.org
May 3, 2023 3:18 PM, "Ivan Nikitin" <ivan@niktivan.org> wrote:
> Hi,> > I published twice and everything works now.> Thank you everyone for the help!> > The HTML redirect also works, thanks for that info.> -- Ivan Nikitin> https://niktivan.org
You want to remove this line from the non-www. domain as it's refreshing the page
every second :)
<meta http-equiv="refresh" content="0; url=https://niktivan.org/" />
--
Oliver Leaver-Smith
+44 (0) 7450 217 558 | +44 (0) 114 360 1337
oliver@leaversmith.com
TZ=Europe/London
BD3C 73DF 33FF 729A B4B7 2C0B E7BF 2699 1650 3BFB