Question:I got a Synology NAS many years ago. To access the control panel, I have to use this address on the browser, but it gets me always a warning, because no certificate locally, obviouslyWhat is the right course of action?>local DNS override in router for quickconnect?>/etc/hosts on every device?>self-signed certificate?>something else entirely?
>>107085641>What is the right course of action?Ignore the warning
pay us goy and we're gonna generate a globally recognized certificate for your pretty NAS :)
>>107085641it's a way the use to control normies with fear, it's just http mode since ssl is meaningless in localhost
>>107085641nginx reverse proxy with a let's encrypt cert, you don't need an internet facing server if you use a DNS challenge.
>>107085641Ignore the warning. As long as your router is configured right, you're fine, as those are IP addresses that are part of the always-local-network range; they can't be routed to directly over the public internet.If you're paranoid, might be worth using a private browsing session, just so that session cookies can't get propagated to random drive-by hacks.
>>107085666fpbp. The HTTPS connection is still providing encryption, just not authentication. That's a private IP address, so presumably you're at your home with the NAS. The threat of someone breaking into your home or spoofing your WiFi to MitM you is pretty slim. If you insist, set up a local certificate authority. What you see is already a self-signed certificate.
>>107085641Use http and port 5000 if it bothers you so much.
>>107085641Follow-up question: Should browsers harass users about not using HTTPS on reserved private IP blocks like 192.168.0.0/16?
>>107086424Yes.
