Okay try this. Exit PMS and connect to your VPN. Add routes for the myPlex IPs to your routing table manually using this terminal command for each myPlex IP:
sudo route add MY.PLEX.IP.HERE YOUR.GATEWAY.IP.HERE
You'll have to input your admin password. Bear in mind that these routes are not permanent, so don't shut down, log out, or restart. Start PMS, and then try to publish.
@kidamnesiac Continued thanks... not sure what is going on but I can't get it to work.
When I manually add I get this for each IP: "route: writing to routing socket: File exists" which I take to mean it was already in the routing table from AddRoutes
netstat is also confirming that the routes were made
Attempt #1: start VPN, manual add, start PMS, unable to publish
Attempt #2: close VPN and PMS, start PMS, publish successfully, start VPN, unable to access myplex from outside WLAN, un-publish, then unable to re-publish
Very strange. It appears AddRoutes is creating the routes correctly. The only other thing I can figure is that your gateway IP is incorrect. If you're using a router this should be the IP of the router.Ā
Another possibility is that if you're using some kind of specialized VPN client, it could be overriding your network setup. I'm just using the built in VPN client in OS X.
Still another possibility is that myPlex could be using different IPs for different regions. To test this, disconnect your VPN, ping my.plexapp.com at random times over the course of a couple hours, and keep track of the IPs you get. I only found the three I listed but it's possible your PMS is trying to connect to IPs that differ from those I found.Ā
Thank you! This worked perfectly!
When I hover the mouse over the green PIA icon in the tray, it currently displays "Connected - CA Toronto [Port: 24050].
I type that port number into Plex ""Manually specify port", then click "Publish Server". Wait several seconds and it says it is published.
I do not type anything in the "Local Port" box in the PIA client.
I do not have any special setting in my router, like port forwarding, enable UPnP, etc. Although I DID try everything in various forum suggestions for folks who couldn't get Plex to publish...like turn off all security software (especially firewall), etc. nothing helped. It was very frustrating.
I have only 'published' Plex twice, in case I ever wanted to use it. Currently, I just use it at home on a Roku.
Afterthought:
I just tried it this morning and it wouldn't publish, even after 5-6 tries with the above settings! I was trying to think what was 'different' the first two times that it worked?
Previously, I also had Vuze running (torrent-file sharing software), so I ran it and BAM...Plex would publish.
In Vuze, tools/options/connection there are two boxes to type in listening port number port. Then 'advanced network settings' ...see attached files.
Maybe Vuze is opening up the port, which allows Plex to publish?
I really don't know...but the three times that I have been able to publish, Vuze was running.
EDIT:
Further 'experimenting' reveals...if Vuze is running I can publish, but NOT without Vuze running.
I hope this is helpful.
NOTE:
Others with this same problem.
https://www.privateinternetaccess.com/forum/index.php?p=/discussion/comment/3148#Comment_3148
https://www.privateinternetaccess.com/forum/index.php?p=/discussion/comment/3823#Comment_3823Maybe submit a ticket to PIA Support?
Any updates to this?
Unless one has a static private ip-address from VPN provider, I do not think it will work to use the VPN-providers port routing options.
Your port will open, but the pms will have the same ip as most users of the same VPN server.
It is possible to route specific apps/services outside VPN, resulting in getting the normal ISPās IP-address for specific services etcā¦ Another option is to route only certain apps/services to go through the VPN.
Have not had the time yet to properly test myself.
I'm running a VPN with Plex successfully. Ā My experience tells me it depends on your VPN service and port forwarding the 32400 port in your router. Ā I use HideMyAss (HMA), previously using OcataneVPN did not work. Ā Hope that helps someone.
Okay. Through some helpful suggestion on Plex Chat, I pinged my.plexapp.com repeatedly and collected IPs. If I find any more I'll update this list, but as of now adding static routes on my server machine that point the following IPs to my default gateway allows myPlex to bypass my VPN and resolve my server's IP correctly. I hope this helps some of you.
184.169.174.153
184.169.137.36
184.169.154.22
Just wanted to say thank you. Adding static routes for these IPs (example on Windows 7: route -p add 184.169.174.153 192.168.1.1) solved the issue for me when connected to VyprVPN.
Just wanted to say thank you. Adding static routes for these IPs (example on Windows 7: route -p add 184.169.174.153 192.168.1.1) solved the issue for me when connected to VyprVPN.
worked for me also! finally. it depends on your vpn. this fix did not work with me on btguard but, does on PIA
Myplex shows it cannot connect to server, but I can connect remotely. This wasnāt possible before, not sure what has changed! Using PIA.
Sent from my iPad using Tapatalk HD
Myplex shows it cannot connect to server, but I can connect remotely. This wasn't possible before, not sure what has changed! Using PIA.
Sent from my iPad using Tapatalk HD
No. it is not connecting through myplex. it is connecting through your ip. So it wont be encrypted by myplex.
My real ip is hidden by the vpn, so Iām unsure how it is connecting. I could never connect while on the road in the past, and Iāve done nothing different to my network settings at home.
Sent from my SPH-L710 using Tapatalk
Just wanted to say thank you. Adding static routes for these IPs (example on Windows 7: route -p add 184.169.174.153 192.168.1.1) solved the issue for me when connected to VyprVPN.
I have to add the route on every reboot, on my Win 2008 r2 server, as for some reason the the -p option will add the route and it shows up in ROUTE PRINT, but TRACERT verifies it's not working.
I use one line: route add 184.169.0.0 mask 255.255.0.0 172.20.10.2
This takes effect immediately and seems to cover all the IP's of the PlexApp cluster.
Rob
Not sure how I did this, but plex is currently bypassing my VPN.Ā
Everything else I run on my PC seems to behind the VPN but plex server for whatever odd reason is not.Ā
Which is fine with me because the speeds and latency is better. I also use PIA, and have their client running.Ā
When I remote into my HTPC and do a IP check via chrome it does show the VPN's IP. However, when I go into plex via my browser at work it shows my ISP's IP. I'm not 100% how I got this to work. I didn't do anything special in my router, however I did have issues with plex not publishing the server,
and I think I did something in the firewall settings to exclude PMS from it. Ā I believe I might of done this because I couldn't publish the server behind the VPN. I'll research it some more when I get home and let you guys know, but I know it's possible within windows. You don't need to mess around with router settings.Ā
Did the my plex Ā IP's change. Ā I added two additional IPs:
50.18.54.61
54.241.4.240
Add another:
50.18.248.98
Did the my plex IP's change. I added two additional IPs:
50.18.54.61
54.241.4.240
Add another:
50.18.248.98
Should these replace the old IP's? Or should they be in addition to ->
184.169.174.153
184.169.137.36
184.169.154.22
Edit: Ended up replacing the old IP's with new ones and haven't had any issues. Thanks!
Here's my Route Add's
route add 184.169.0.0 mask 255.255.0.0 172.20.10.2
route add 50.18.170.0 mask 255.255.255.0 172.20.10.2
route add 50.18.248.0 mask 255.255.255.0 172.20.10.2
route add 50.18.54.0 mask 255.255.255.0 172.20.10.2
route add 54.205.33.0 mask 255.255.255.0 172.20.10.2
route add 54.241.4.0 mask 255.255.255.0 172.20.10.2
they have changed again 50.18.174.123 , 54.241.249.32, 184.72.57.129
Hey guys,
I was banging my head against a desk for a longtime over this issue. I used a bunch of different VPN services that did not give desired results. I finally looked into virtual machines and normal VPN providers such as PIA. On a forum from another site, someone mentioned that VMs use a different "nic" or something like it which means you can have your VPN active on your VM and have normal traffic on your host PC. I tired it using OS X as my host and Windows 8.1 running on parallels. (warning: I cannot confirm this trick will work using something like VMWare Workstation on a windows PC). Anyways, I have PMS on my mac forwarded to 32400 and works perfect and I have my VM protected using VPN and listening to shared folders from my Mac for automated services which I wont mention, lol. I also checked mutiple times on whatsmyip on both simultaneously had my actual ISP IP on my mac and my VPN IP on my VM.
hope it helps
Plex.tv's IP seems to be changing more often now.Ā I wrote this script to change firewall/VPN routes and have it set to run ever few hours.Ā Be advised that everytime the script runs it writes to a txt file so keep your disk's read/write cycles in mind.Ā Ā I have the script running from my router (Tomato Shibby).Ā It requires the 'bind' ipkg and the txt file location and iptable rules will need to be changed per your setup.Ā Hope this helps some other people out!
#!/bin/sh DNS="/opt/myplex/plexdns.txt"#Read txt file and delete old rules
while read line
do
iptables -t mangle -D PREROUTING -d ā$lineā -j MARK --set-mark 1
iptables -D FORWARD -s 192.168.1.7 -d ā$lineā -j ACCEPT
done < $DNS#Clear txt file
cat /dev/null > $DNS#Record new IPās and disregard duplicates
echo $(dig plex.tv +short) >> $DNS
result=dig @8.8.8.8 plex.tv +short
grep -q ā$resultā $DNS || echo ā$resultā >> $DNS
result=dig @209.244.0.3 plex.tv +short
grep -q ā$resultā $DNS || echo ā$resultā >> $DNS#Create new rules
while read line
do
iptables -t mangle -A PREROUTING -d ā$lineā -j MARK --set-mark 1
iptables -I FORWARD -s 192.168.1.7 -d ā$lineā -j ACCEPT
done < $DNS
