You are right that link doesn't work. When I first installed certificates I discovered one included the full chain of trust and the other didn't. I installed the wrong one and latter and discovered the full chain of trust worked better.For a few years, I have successfully self hosted my own personal website (http, not secure) on an RPi5, using Apache as web server. I then changed broadband provider from BT (copper wire with dynamic IP) to brsk (fibre optic with static IP) and at the same time, tried to change from http to https. To this end, I used Letsencrypt to install a certificate on my webserver, something Letsencrypt says has been successful. However, I cannot now access the website externally (localhost works fine). Inputting http://robinboardman.me.uk into my Chrome browser just loads the login page for my Icotera router.
I have spent a long time searching the internet for answers but when one doesn't know the correct question to ask, it's hard to get a useful answer. One suggestion was to use SSLLabs to test the site, a summary of the feedback being "Certificate name mismatch. Alternate names not found in the certificate. We were able to retrieve a certificate for this site, but the domain names listed in it do not match the domain name you requested us to inspect." Other feedback is that the certificate is self-signed. Whilst I understand the words , I don't know what to do about to make the website work.
I am sure there are others out there who use an RPi to self host a website (mine really is basic) so I was wondering if anyone has any thoughts on the above and/or advice to give. Just where to start looking would be a help.
Like so many things, https is overcomplicated for no good reasons and for many bad ones. Sorry I can't help more. I hope you get it resolved.
Statistics: Posted by ejolson — Fri Nov 14, 2025 4:17 am