![]() All of the above with MacOS firewall disabled. ![]() All of the above with different PIA VPN locations among the ones that support port-forwarding.Ħ. In the Asus GUI additionally specify the destination local port as 8096.ĥ. Same as #2 but leave the Emby remote port as the default 8096.Ĥ. Scanning the new public-facing IP shows the new port (and 8096) is not open.ģ. ![]() Enable port-forwarding in the PIA VPN client change the Emby server remote http port to the port the VPN is forwarding (this is a read-only assigned port in PIA) forward the new port to the server's local IP address via the Asus GUI. Forward 8096 to the server's local IP address via the Asus GUI.Ģ. These are the things I've tried and have all failed:ġ. When I connect the server to the VPN and scan the server's new public-facing IP, 8096 isn't open. With other protocols, PIA’s results were quite impressive, but it was no competitor against the faster Surfshark VPN. Surfsharks download speed was 262.6 Mbps vs PIAs 124.0 Mbps. When my server is not connected to the PIA VPN, I can scan the server's public-facing IP (from another computer) for open ports and I see 8096 is indeed open. Overall, Surfshark wins the speed comparison with better speed results, especially with the WireGuard protocol. * Emby server has a manually-assigned IP via the Asus GUI to its MAC address. * Internet is cable to an ISP-supplied modem, WAN port to Asus RT-AC68U, ethernet to the Emby server. * Emby server 4.2.0.40 on MacOS 10.12.6 Sierra and also running PIA 1.1.1 Anyone else successfully doing this with PIA? My setup is: I've seen some helpful posts regarding this by some advanced users, notably and but I'm having no luck.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |