Newbie Struggling to Set Up Remote Access to WAN Server

[drpickles 0]

I'm sure you folks are tired of troubleshooting for the plebs who can't figure out what stupid mistake they're making when setting up their WAN server. I've followed a bunch of different tutorials on how to host a DNS and redirect it to my Emby WAN server. I'm pretty sure I hit all the major beats as far as port forwarding the device IP address on my router, redirecting my DNS to the device IP address, putting the DNS information into the Emby Network tab, but I still can't access my WAN through either Emby Connect or typing my DNS in the address bar. Please help me because I feel like I'm coming undone. Also, please excuse me for any incorrect terms or information I may have given. I'm still learning all of this as fast as I can. Thank you so much for your patience.

[Q-Droid 989]

Start simple then move to the next step after each is working. That Virtual Server List image doesn't look quite right. For a basic setup the public and private ports should match: 8096 public -> 8096 private, same for 8920 -> 8920.

1. Check with canyouseeme.org. Does the detected IP address on the site match your router WAN IP? 
    - If not then check with your ISP to see if they're using CGNAT.
    - If they don't use CGNAT make sure you don't have double-NAT. Like your own router behind the ISP router.
    
2. If the WAN IP is good then forward port 8096 WAN/public to 8096 LAN/private server IP.
    - Check connection from a browser to emby using http://WAN IP:8096.
    - Some routers don't allow NAT loopback/hairpinning. You can always try a mobile browser not connected to the LAN or WiFi.
    - If it doesn't work keep at it until you can get it working.
    
3. Get DNS setup to resolve to your WAN IP, not LAN.
    - Check connection again from a browser to emby using http://DNS name:8096.
    - If DNS doesn't work but IP does then get the name to IP resolution working before moving on.
    - Setting up URL redirects from the DNS provider can cause problems with Emby apps. Probably should avoid if you can.

4. Check connection from browser to emby using https://LAN IP:8920.
    - It should connect but throw a site/certificate error - Not Secure. You can click through to connect.
    - If it doesn't connect then check your certificate file to make sure it and the password are correct and emby can access the file.
    - Keep at it until you can get it working.
    
5. Forward router port 8920 WAN/public to 8920 LAN/private server IP.
    - Check connection from a browser to emby using https://DNS name:8920.
    - Some routers don't allow NAT loopback/hairpinning. You can always try a mobile browser not connected to the LAN or WiFi.
    - Keep at it until you can get it working.
    
6. Check the emby dashboard and make sure the access (LAN/WAN) details are correct.
    - Adjust as needed.

7. Close/remove the 8096 port forwarding on your router, you don't need it for WAN access.

8. If it's working now then scrap all of it and setup a reverse proxy. Just kidding...but not really. Consider that your next project. Caddy is popular and easy to setup with Emby.

 

Edited May 6, 2025 by Q-Droid

[drpickles 0]

Okay thank you so very much for your help! So far I've fixed everything up to having my DNS redirect to the WAN IP. The WAN IP works by itself with the 8096 but I haven't gotten the WAN IP with 8920 or the DNS with either 8920 or 8096 to work yet. I'll keep at it for now but again thank you so very much for helping me. It's nice to know I at least have access to my server outside of my LAN now.