Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I created Let's Encrypt certificate through my ASUS router, and in the router GUI it shows it as valid. But I get the certificate invalid message when I connect over https, and when I check the certificate on sslshopper, it shows the wrong certificate name as router.asus.com, like it was self-generated. Do you guys know how to fix this? Is it a problem on ASUS side of things? Thank you.
Thanks for the reply. I actually figured it out, for some reason it wouldn't forward port 443, probably used by some service. I tried forwarding from different external port and put port in the url and it works and certificate is recognized.
Thanks for bringing this up. I am actually not trying to access router, but to access Home Assistant running on a Raspberry Pi on the network. So I would only forward the port for Home Assistant. My plan is to have only Home Assistant running on the Pi, nothing else, so shouldn't be that big of a risk. What do you think? Any advice? Thanks.
Thanks man. I couldn't go the add-on way this time, I'm running my HA in virtual environment. But, my plan is to get one more raspberry pi and have it just running HASSOS, so then I'll be able to go this route. I'm really new to all this stuff, just wanted to see what the fuss was all about, I didn't realize I'll get so obsessed with Home Assistant