Server Version#: 1.28.2.6106
Player Version#:
Suddenly, the server is not accessible outside my LAN. It has been working for years so I don’t think its an internal issue. Perhaps related to the password issues? Had some trouble reclaiming the server, but internally to my network, everything works fine.
Any suggestions? Shall I download logs and post them?
thank you
Hi mkopel,
Same problem.
Anyone could help us with any suggestions to solve this ?
Thanks
This happened to me as well - said my external IP was some 10.x IP - and NO way to fix it.
After trying to repair, and reinstalling Plex, i was left with a smoking crater and no Plex. It would crash on trying to start it!
Took uninstalling, and clearing the directory in \program files for Plex - a Reinstall, then stop Plex and manually restore the DB (you do back up your DB, right?). Plex is back on 1.28.1.6104!
BEWARE the 8/29 update (aka 1.28.2.6106)!
you mean the 1.28.2.6106 is the cause of this crash ?
yeah same, am on Nvidia shield and its been down for over a week now (since last update)
Well, it was the cause of the remote access no longer working.
Me trying to repair it via Plex tool, and then reinstall - well that crashed it into a smoking ruin
Please try first and simply restart the Plex Media Server
We sadly did have an issue last night, that lasted about 2 hours, and caused a PMS to not find it’s public address => No remote access
It not finding the IP was one part - the next part of the issue is it would find it as a 10.x.x.x IP, which doesn’t exist on my local network, nor is Internet routeable.
Both these issues started after the latest 1.28.2.6106 update - as soon as it was reverted to 1.28.1.6104, it worked perfectly.
That happened for a very limited time during the fix process
You should be able to upgrade now
Thanks for the info.
With others saying they’ve been down for well longer than the two hour service outage you are citing, and I certainly was as well - going to pass on Plex updates for a bit. Don’t want to risk blowing up my Plex server again. Although am now proficient at DB restoration, which Plex makes very easy, so that was appreciated.
after restarting plex on my synology NAS, I see the same issue. The strange thing is that I can reach the server on LTE on my phone, but the server settings still says it is not reachable from the outside, so I am confused by what is going on. here is a screen grab.
any ideas?
You do have a funny public port in use here 
I suggest you manually specify a port, and make sure you have a rule on your firewall for that
for years I have not had to specify a port. Why should I start now? Has something changed with plex that makes that necessary?
please let me know if there is anything further I can try. Or if logs or any other data would help debug the issue.
thank you.
Edit :: suddenly, that odd ip is now labeled as “fully accessible outside your network”, is that an issue?
Edit2 :: actually, it is going up/down. but still accessible outside the network, so odd.
Please make certain DEBUG logging is enabled and VERBOSE is disabled.
If they are, Grab the logs download now please.
Let’s see what it’s doing.
It’s STRONGLY recommended to set a manual port, with a Port Forwarding rule on your router
That way, you also make sure you’re not using the default 32400 port, which from a security site is slightly better
here are the logs, thank you for taking a look.
Plex Media Server Logs_2022-08-30_13-14-45.zip (3.4 MB)
with manual port it has the same behavior, it states it does not have access to the outside, but it works from LTE. Additionally, the ip is the same odd ip but with the new port number.
Thank you for the logs.
In all the logs you just gave me, at no time did reachability test (where plex.tv confirms Remote Access port forwarding is open) succeed
Reachability :0 = False (closed)
Reachability :1 = True (open)
Please observe:
[chuck@lizum user.1219]$ grep responded *
Plex Media Server.1.log:Aug 30, 2022 08:48:42.482 [0x7fdd5f523b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier 7d368fba-5f87-474c-93ea-cdf25ca9db18: 0 for :0 (responded in 32 ms)
Plex Media Server.1.log:Aug 30, 2022 08:49:09.030 [0x7fdd5f523b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier 5ebcf475-0048-4012-956e-3ff25a40f221: 0 for :0 (responded in 584 ms)
Plex Media Server.1.log:Aug 30, 2022 08:56:32.867 [0x7fdd5f523b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier 7704a461-f3a1-424b-8224-63b471e2e363: 0 for :0 (responded in 158 ms)
Plex Media Server.1.log:Aug 30, 2022 08:59:40.178 [0x7fdd5f726b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier 46d1db59-b5ce-400e-a76d-18cee4485638: 0 for :0 (responded in 1495 ms)
Plex Media Server.1.log:Aug 30, 2022 09:00:02.255 [0x7fdd5f523b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier 09fb3cd4-dc21-480c-a827-c199204709f1: 0 for :0 (responded in 4669 ms)
Plex Media Server.1.log:Aug 30, 2022 09:00:16.130 [0x7fdd5f726b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier 82e76126-a93e-4827-81fa-e4171192a1cc: 0 for :0 (responded in 237 ms)
Plex Media Server.1.log:Aug 30, 2022 09:48:42.068 [0x7fdd5f523b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier 50421157-58ee-465a-a3d2-9be62a2c6ea1: 0 for :0 (responded in 851 ms)
Plex Media Server.1.log:Aug 30, 2022 13:01:29.616 [0x7fdd5f523b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier bb0f37f4-9371-416e-9202-218cb052f1b6: 0 for :0 (responded in 73080 ms)
Plex Media Server.2.log:Aug 30, 2022 08:47:15.021 [0x7f49fae6eb00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier 0aa4bb2d-4afc-4265-b780-3a5a8166269d: 0 for :0 (responded in 162 ms)
Plex Media Server.2.log:Aug 30, 2022 08:47:35.068 [0x7f49fae6eb00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier 5cb52f84-9b40-42c0-8970-41dc0b07bff1: 0 for :0 (responded in 154 ms)
Plex Media Server.3.log:Aug 30, 2022 08:45:20.742 [0x7f8c0f998b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier ac347248-3005-4d86-bec9-843ee168ebff: 0 for :0 (responded in 413 ms)
Plex Media Server.3.log:Aug 30, 2022 08:45:45.510 [0x7f8c0f998b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier 59f3c547-f8de-4eca-86eb-58e095444212: 0 for :0 (responded in 161 ms)
Plex Media Server.4.log:Aug 30, 2022 07:39:10.012 [0x7f8c0fb9bb00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier 67922b67-cfe7-4eb7-a7af-5d12f9fc4c70: 0 for :0 (responded in 16257 ms)
Plex Media Server.4.log:Aug 30, 2022 08:00:24.029 [0x7f8c0f998b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier be0bd193-6299-4fa3-97c0-a403d5b1b3ab: 0 for :0 (responded in 8384 ms)
Plex Media Server.log:Aug 30, 2022 13:13:56.694 [0x7fdd5f726b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier a3b096a5-0142-4d34-9379-39ec5400e8d5: 0 for :0 (responded in 264 ms)
Plex Media Server.log:Aug 30, 2022 13:14:19.945 [0x7fdd5f523b00] DEBUG - [EventSourceClient/pubsub/184.105.148.82:443] PubSub: Got notified of reachability for async identifier e09203eb-5291-4028-9061-9527f1cf3c73: 0 for :0 (responded in 852 ms)
[chuck@lizum user.1220]$
The manual port forwarding you have in place is not working as expected.
I suspect the green toggling you were seeing is Plex/web’s optimistic display of green in hope the port is open. The indicator will quickly turn red again when the port test completes.
Are you forwarding your manually selected external port (TCP) to the LAN IP of the PMS system at port 32400 ?
If this is working CanYouSeeMe.org will also be able to confirm the port is open.
Also in the logs, all references to port are port="0". No outbound manual port number is being assigned (which is not normal).
Might you consider flipping to UPnP… Let it fail , then flip back to manual ?
I have tried flipping from upnp to manual and back again, but that does not make a difference. i will check the port forwarding carefully to make sure the correct port it open. thank you for the suggestions.
I bit the bullet and rebooted my router. All is working as expected now, with or without manual port.
thank you for the help.
