We moved the name servers back to Cloudflare. Apparently his ISP's DNS servers aren't configured right and were still caching info that should have been flushed. dig the domain and see it at Google again. I then did some testing from my house and the dns record would not resolve. A ping or tracert was correct but nothing made sense. From reviewing Emby setup to the tunnel to the router. I of course didn't know this and when things didn't work that did previously I spent time looking at the wrong items. As part of earlier setup we/I moved the names servers from Google to Cloudflare so that we could use Cloudflare's Argo tunnel to work around his CGNAT. Through miscommunication or something he had moved the names servers back to Google thinking that might help. We wasted nearly two whole nights working on a solution for him that I've done a dozen + times just not on Synology and I was like a dog chasing his tail going in circles as nothing seemed to worked that previously did. Then when the keyboard opens it's even worse especially if I was in the middle of typing or running something as I'm nearly paralyzed for 20 to 30 seconds before I can see what's going on. Then from that small screen I have to SSH into the Synology which is doable but unpleasant to say the least. AndrewDub2044 only has a tablet to remote into which is a challenge on my side as it's a tiny screen and every time the tablet's virtual keyboard is opened I loose half my screen and need to wait for it to normalize before I can do anything again. This is super hard for a few reasons but we are nearly done. PS I can remote in and give you a hand with the setup and it won't take long but let's discuss first your needs. Once you answer those questions it would be easy to point you to a more specific solution. Get a legit cert and only use that and save yourself the grief!!!īesides Emby do you have any other apps you need to access remotely? Do you need access to your household LAN from remote?ĭo you have any other devices or computers running anything that is available remotely? You can't just redirect Emby traffic like most other sites as it needs a custom setup (which you can't do with the built in proxy). Now Synology doesn't get to reroute my traffic.Īlternately you setup your own reverse proxy which can be nginx to forward things but you control the settings used so Synology can't change them on you. So Emby receives on port 8920 but marks all packets being sent as 443. So with those settings in Emby I have the gateway router set to WAN IP:443 -> Emby IP:8920. If I want to use anything other than Emby I VPN in and have access. One is Emby's secured ports of 8920 (local setting) & 443 (remote setting) and my VPN.

How you go about this depends on how many apps you have running on Synology that need remote access? I have internally maybe 50 or so web apps but I only have two things directly exposed to the Internet. BTW, it's very hard hard to work around this built in proxy in Synology as any changes you make to the system get reset by it usually on restart and for sure during any DSM updates. You have a couple choices to make on what you want to be available remotely from your NAS. That to me appears like you set emby up to use port 443 and/or 80 but Synology Proxy's built in nginx proxy is catching it and redirecting to the dashboard.

Pia vpn synology