Remote access with VPN

[AleMonti 1]

Hello all,

I have a Raspberry Pi 4 that's been running as a seedbox for a while now. It runs Transmission through Wireguard with Mullvad VPN. Torrents are downloaded on a disk shared locally with Samba, so when I want to watch something I hook up my laptop to the TV, go to the shared folder, and play the video file. Works perfectly fine for me.

Now that Mullvad is ditching the port forwarding support and I will have to switch VPN providers, I thought it might be the perfect time to upgrade my setup. I want to use Emby to share my library with my father, who doesn't live with me and it's not very tech-savvy. The Emby app on his smart TV would be perfect for his use case. I thought this would be an easy task given that I'm already able to access Transmission's web interface remotely, but I can't seem to get it to work.

My setup is as follows. I have opened a few ports on the VPN's website, let's say 5xxxx, 5yyyy, and 5zzzz. The seedbox public IP is aaa.aaa.aaa.aa. 5xxxx is used by Transmission to connect with peers, and 5yyyy is the interface port. To log in locally I use 192.168.1.128:5yyyy, and remotely aaa.aaa.aaa.aa:5yyyy. So I tried the same with Emby on the 5zzzz port. But no matter what I've tried, I'm not able to connect remotely via aaa.aaa.aaa.aa:5zzzz. What's happening here?

I understand that is not needed, and probably overkill, to route Emby's traffic through the VPN, but I wasn't able to have it bypass the VPN tunnel either. The ideal solution that comes to my mind is setting up two docker containers, but I'm not familiar with it at all and I would have to import all my torrents again into the client. It might be worth the hassle in the future if my father gets to use Emby regularly, but for now I'm just trying to test it out in the easiest way possible. 

Any help would be very appreciated!

Thanks

[AleMonti 1]

After some more trial and error I've managed to get it working. I've just set the port (5zzzz) in the settings for both local and private. I don't know why it didn't work before, I was probably messing up somewhere else. I'm now able to easily access remotely via aaa.aaa.aaa.aa:5zzzz, sorry for the useless post.