External & Internal Networking Issues

[smody121 3]

They're all on a bridge, I have zero host containers.

I tried using this guide: https://drfrankenstein.co.uk/access-your-self-hosted-services-remotely-using-wireguard-vpn-on-a-synology-nas/

and have set up a WireGuard VPN tunnel, but now kind of stuck on how to connect all of this together to open access to Emby, so working on that now.

[Luke 42077]

OK let us know how you get on. Thanks.

[smody121 3]

I'm in business. A little embarrassed as this seems like a simple fix, but it was due to my misunderstanding of internal vs. external IP addresses. I also forgot that I changed the default Emby Port number from 8096 to another port number.

I could not connect to the Emby server because I was not using the proper IP addresses and port numbers. I followed the Emby/Gluetun guides properly, but it was this video (3:09) that properly explained what was happening with DNS which was causing the disconnect for me all this time and reminded me that I changed the local Emby port number in my docker container setup.

What I needed to fix:

1. Port forward the Emby server's PORT NUMBER, the IP address was of my NAS. I was confusing myself on which IP address to use (Emby's external/internal from the dashboard, the NAS, my desktop, etc.), ended up being the NAS IP address and the local Emby port number I used when setting up the docker container in DSM. Simple as that.
2. When trying to connect to the Emby app (or via a web browser for that matter, tested successfully as well), using the newly created WireGuard VPN tunnel created via this guide. Once I had finished with the guide, I had created a new DDNS Hostname through DSM, which is the URL I used to connect directly to my Emby server through that tunnel, with a colon and my local Emby port number at the end. I closed and reopened my Emby app, and was able to manually connect to the server by using the exact same URL and port number as well.

This setup does not provide a tunnel to my entire NAS, it's a specific tunnel to the Emby server only (I believe). That will be a different problem to solve for a different day (and forum!) but just want to thank anyone who came in and tried to help this noob learn his way through all this.

[seanbuff 1313]

2 hours ago, smody121 said:

I'm in business. A little embarrassed as this seems like a simple fix, but it was due to my misunderstanding of internal vs. external IP addresses. I also forgot that I changed the default Emby Port number from 8096 to another port number.

Great news on getting it all working! well done.

2 hours ago, smody121 said:

just want to thank anyone who came in and tried to help this noob learn his way through all this

and thank you for circling back and updating your thread with the solution in your case, always appreciated.