I’m having the same issue (remote access for 15 seconds before disconnect) and followed the recommendations here but it still wasn’t resolved. Is there an enterprise solution or something I’m missing?
1 Like
There is no single recommendation that applies to everyone. There is currently a timeout / retransmissions and delays issue on connectivity test requests to servers mainly in Australia, New Zealand, Singapore and Malaysia with one or two users with servers in the US having same symptoms.
Other than this specific issue, there may be other factors and we have a troubleshooting support article available here
https://support.plex.tv/articles/200931138-troubleshooting-remote-access/
Would need to see server logs covering the time when remote access drops to establish if it is the timeouts issue - would need to have verbose logs for this specific issue
See https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
so thats whats been happening , i had my isp open up a port today, and i did connect to my plex server thru my phone over mobile inter and i did stream music. then i checked couple of hours later and i couldn’t access the server. checked the setting and it says its not accessible. then did the manually specify port number and now it works again. Its like its dropping the settings that i applied. Also i’m able to stream when it clearly say i’m not reachable out side your network.
I sent you my server logs last week, have you had the chance to look them over?
I have just looked at the logs - throughout the logs the evidence is that nothing is coming through to the server
Could you get me screenshots from the router to show that you do a port forward in place for WAN tcp port 32401 forwarded to local port 32400 to 192.168.1.253,
Some routers do not allow the wan port and local port to be different in a port forward.
Also double check what windows has classed the network connection as. Sometimes they get switched to “Public Network” or “Unidentified Network”. It should be “Private Network”
If you do not select “Manually Specify Port” then a random port gets picked up. Every hour Plex Media Server makes a request to the router to refresh this port mapping. May be this is failing or a different port ends up being used. This has been seen to arise if you have multiple network interfaces and the one that was used for the automatic port mapping dropped out.
Manual Port selection is a safer option. If you wish to go back to the earlier setup, I would need to see some logs when it drops out. Beta 1.19.4 of Plex Media Server which was released today has a lot more diagnostic logging for remote access issues like this - so if you are going to provide logs, wait until you update to 1.19.4
I switched to a manual port , and set Plex to use a certain IP in the settings , it seems to be working for now
Is there a from scratch settings list for router, firmware and PLEX for this release?
same issue. Comcast/Xfinity is the ISP, I have 32400 forwarded from the public to 10.0.0.3 (my local router) and on that (Netgear WNDR4300) I have 32400 forwarded to 172.16.0.11 (my plex system). Config on plex is to enable remote access and use a manually specified port (32400).
I have a system sitting here that is on my wort VPN right next to the plex machine so have been able to flip back and forth easily…
When I disable remote and re-enable, it shows green and accessible, the machine on the work vpn can hit it with no problem, about 15 seconds later, the plex box shows no access and the machine on the vpn can no longer hit plex.
This seems too common an issue for it to be random. This needs to be fixed. Folks pay for the plexpass so they can have full unfettered access to their plex boxes from anywhere. This just makes a compelling case for not giving these guys any more money.
BTW, this worked when I first set it up a few weeks ago, so there is no excuse that its because on of the systems is on my work VPN. The only thing that has changed has been several updates to plex
Do you have xfinity advanced security enabled by chance? It’s a remote access buzzkill for sure.
I’ve been getting the same thing for months with Plex running on ubuntu 19.10 installed via snap plugin manager.
I’ve done all the correct port forwarding, even added firewall entries just in case.
Plex saying not available outside your network. When I click on retry, it says fully accessible outside your network for about 5 to 20 seconds, then goes back to not available outside your network. Plex works remotely, but says streams are indirect.
There is nothing else that I can do on my Plex server or my router…
Please fix this very frustrating issue!!
Okay, so I’ve actually just resolved the indirect play issue for me. Here’s how:
Go to Network and untick Enable Relay. This allows remote direct play again.
Plex still says not available outside your network, but everything is actually working.
Hopefully the dev team will get around the networking issues soon.
1 Like
Two things here that may impact remote access functionality
-
xFinity - They have introduced extra security and created port forwards have a short limited life after which they expire and need user approval - we have a paragraph on xFinity security in our Troubleshooting Remote Access article
-
Double NAT - Plex Media Server will try and establish what the public IP is and it will ask the router through NAT/PMP - if it gets back 172.16.0.1 then that would cause an issue - would like to see logs during remote access setup to see what we get back. Run with the 1.19.4 beta as that has extra logging specifically for remote access issues
See
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
see my post above about logs with debug logging and using the latest 1.19.4 beta
Hola, no pude leer todo el hilo y mi ingles no es tan bueno. Me estaba pasando lo mismo, me andaba el acceso remoto en Win10 y en la misma compu con LXDE linux no agarraba. Desisntale el plex y apague el cortafuego ( nunca habia tenido un linux con cortafuego) y no funciono. Buscando las carpetas que se podrian haber generado ( para desinstalar denuevo pero borrando todo) descubri una carpeta y un archivo .pid: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server
resulto que abri el archivo y tenia un numero y se me ocurrio ( y es la verdad por que no se nada de informatica mas que lo que me dio ser usuaria de Linux) poner ese numero en la configuracion de plex donde dice : “ingresa manualmente el puerto publico”-
Se arrelgo el problema y ya tengo vinculado el plex de la pc al de retropie. Espero esto sirva de algo! saludos
This worked for me. Thanks a lot. I had the problem since yesterday (may 29, 2020) and have been searching all day. First I thought it was a problem with Windows 10 (like always) or with my router or firewall. Now I can reach my content again with my mobile phone and my PlayStation 4. Great!
which solution worked @FelixRothuizen
In Settings, go to Network (then scroll a bit down) and untick Enable Relay. It was that simple.
Thanks, didn’t work for me unfortunately
That is too bad. I hoped it worked for everyone.
