Help with remote access through docker

[jahagafut 5]

For the life of me I can't get remote access to work, I can remotely access through my tailscale ip but I want to be able to easily access my server on a Roku or similar when working on the road. 

I'm using Ubuntu Server 24.04, I've installed emby in a docker, it's running in host mode on port 8096, I also run adguardhome in a docker in host mode with the dockers dns set to 1.1.1.1, I have systemd/resolved.conf configured for dns:127.0.0.1 and DNSStubListener=no. I have my ISP modem in bridge mode to a TP-Link be550 router, I've reserved the I.P 192.168.4.2 for my server and I'm trying to access through the IP that Emby is providing as my WAN, which I've also confirmed is my public IP. I've ran ufw allow 8096. Oddly it did work yesterday when I first redeployed my system after changing network card. I have my routers DNS set to my servers ip to use my adguardhome DNS and secondary DNS as a second copy of adguardhome I have running on home assistant OS on another pc with an adguard sync docker on the primary. Setting the router DNS back to default doesn't solve the issue. Any ideas?

Spoiler

Spoiler

 

[Luke 42077]

Hi, are you able to connect from other devices inside the network?

[jahagafut 5]

Yes I can connect from several devices in the house using the LAN address, and yesterday after redeploying my server I was able to connect for a moment through WAN, I've tried rebooting and redeploying emby

[jahagafut 5]

I just tried disabling adguard, setting Ubuntu DNS settings back to default, setting router DNS settings back to default, and no luck. I even tried setting the emby dockers DNS to 1.1.1.1

[jahagafut 5]

I've resolved the issue. In emby network settings I disabled upnp for port forwarding, then in my router I went to port forwarding and specified the service type as http, and forwarded the port. I can now access remotely and with my dynamic dns provided by my router I'm able to connect using a URL instead of ip.