![]() However yes running it all on one machine does cause some looping issues, i remember testing a setup where I had a pritunl self hosted vps running on the same docker server as emby etc and i was unable to access it which made sense after a while. Im not fully understanding who you are hiding your Ip from, is it your mobile operator when you stream or the content of said stream. I presume you are using a windows machine so the following is based on that assumption. The bad part is that 2 computers are needed and they will use tons of electricty if left on 24/7.Īny suggestions how to achieve bypassing the vpn so emby would not be protected and work remotely on the same server? Emby did work remotely and was protected by the vpn through tvheadend. I opened the router using the new emby port number and this computers assigned ip address only. For testing purposes, I installed emby on another computer and changed the port number. The problem is that I have both emby and tvheadend installed on the same server and the vpn is protecting both. If I could make emby bypass the vpn, then I believe that it will work remotely. It works flawlessly and the tvheadend m3u is protected by ipvanish when any client is played. Basically, I am using emby as a client that is receiving the m3u through tvheadend's playlist. ![]() Would this setup protect my original ip address and mask it to something else if I play a stream with Tailscale. ), as well as there are some alternate solutions. IPVanish does not support port forwarding. The local network ip address work fine and are protected by the vpn.Ĭan someone tell me what I need to change to make ipvanish work with emby remotely? When I try logging on remotely using the ipvanish ip address, access is timed out. The emby dashboard is displaying the ipvanish ip address with port 8096, and the local IP address. My server has an assigned Ip address and ports 80 are opened on the router. The Vpn is working fine and the ip address is masked as it should. ![]() I am using the openvpn Ipvanish certificate configuration. I useTvheadend's ip m3u and it's xmltv ip as my sources. My setup is using Ubuntu 20.04 as a dedicated server with both tvheadend and emby installed only. I was enjoying the remote features while working out at the gym until recently when I turned the vpn on. I have been using emby since November and everything works great within my local network. I just realized that my ipvanish vpn was not running and I turned it on. But it's paid for.Hello everyone, I hate to be a bother, but I am out of ideas. This essentially connects the route for you through good old port 443 (HTTPS) and does the routing for you. You could also look at something like LOGMEIN, but it's paid for. Should get a login prompt to your desktop and log in.Īs you can see there are lots of steps to get this up and running but this should work.Open your home computer fire up remote desktop client and type your work's external IP address.Check windows internal firewall allows external connections to remote desktop on both your home and work desktops.Enable remote desktop connections on your work computer (this should already be enabled seeing as you do this anyway though VPN).Add a rule to NAT or portforwarding of TCP/UDP 3389 to the internal ip address of your work computer. ![]() If you require steps you would need to specify your router or firewall above so I can try and help with that. Then what you would need to do is just type on your home laptop your work router's IP address through remote desktop client or using remote desktop manager. Set up portforwarding of TCP/UDP port of 3389 which is RDP port number.
0 Comments
Leave a Reply. |