![]() ![]() SSL works based on these names, so accessing via IP will give you the red warning. The important thing is to check what names it is configured to ("common name" and also "subject alternative name") - you should check from your browser. > but either I set it up incorectly but cannot reach the synology after setting the cert as default. The only problem was, that I had to store it as trusted on all my machines. (not to expose manufacturer) 192.168.1.123 and it should work just fine from your local network (until the IP changes - assigned by router, or you loose internet access and the dns would not be cached - this can be temporarily solved with a hosts file).įor me self-signed works fine, but I use a local DNS (something like nas.lan) which is a feature of my router. ![]() ![]() DNS can point to any IP, it could be a local one too. > to use a subdomain to reach my synology on my internal network let's encrypt) - where it wants to touch the IP the DNS points to. But it does relate to free DNS verification procedure (e.g. does not necessarily need to relate to it's DNS. > do not want the synology to be accessed from outside my home. There are a few questions here, I will try to answer them separately: ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |