Server Version#:1.32.6.7371
Player Version#:1.75.0.3920-8b50876d
Remote access suddenly stopped working over a wek ago. Please let me know what logs I need to send to help. I suspect its a certificate issue with plex. Please help I have exhausted all options.
You’re not the first to report this problem.
Certificates are usually OK (unless you see specific certificate errors in the logs)
Current confirmation of the problem, and a temporary workaround, is to downgrade to the previous version or even down to 1.32.5.7210 if you have it handy.
If changing version does not resolve the issue, your DEBUG log files ZIP will be needed to see specifically what’s happening when PMS starts.
I will try to downgrade but I do not have that version available. Do you have the apk installer for asustor Nas handy by chance? ALso what would be the best way of downgrading on asustor nas?
I suspect you’re wanting the 64 bit Intel version ?
(Let me know if not).
It’s been a while since I did it.
Do you have “manual install” for the APK?
I believe you Manual Install on top of the version already installed.
(do not install)
yes that works thank you.
Manually installing on top of current version does not work. Says newer version is already installed.
Should I keep the preferences.xml file and replace it in new install folder to save configuration or just start completely fresh with new settings?
Do whichever you are most comfortable with.
On some NAS platforms (Synology is one), you can safely uninstall and the installer finds your data when you reinstall and uses it again.
I haven’t used the AS6704 in our lab in some time and don’t remember what is best practice.
Running old version now. Started working for a few minutes then back to red. I just reinstalled over same plex shared folder. I can provide logs or start fresh install. Which files from logs zip do you need?
I peeped the console after reinstall and said warning with this message: [CERT] TLS connection from [::ffff:10.0.0.176]:50598 came in with unrecognized plex.direct SNI name ‘10-0-0-116.8110d27e013d42219deefbe923621548.plex.direct’; using installed plex.direct cert
OK… That is the client using the OLD server cerficiate.
Fully stop and restart the player/client app.
Also, since your LAN is IPv4, you can turn off IPv6 in Settings - Server - Network
Just checked your certificate.
A fresh (new) certificate was created when you reinstalled.
Worked for about 10 minutes, but still getting the same warning message about CERT in console. remote access is red 
Damn. There is nothing I can do on the weekend at this hour.
I will see what I can do tomorrow.
If you have an older APK to downgrade to, you can try it… keep going down until you get it stable.
There is a regression somewhere we’re tracking
I appreciate the help, I will try downgrading more. I got a new router coming in a few days, so hoping that fixes it.
Hopefully this helps as well
Plex Media Server Logs_2023-08-12_23-03-10.zip (1.9 MB)
Were you hovering the mouse over the Remote Access tab?
I ask because your logs were firing off tests very much out of control.
There should be one per 15 minutes
Aug 12, 2023 23:03:00.421 [139978550663992] DEBUG - Completed: [10.0.0.176:51775] 200 PUT /myplex/refreshReachability (7 live) #6bf TLS GZIP 0ms 195 bytes (pipelined: 15)
[chuck@lizum ~.2003]$ grep -i reacha /tmp/reach | grep '0 for'
Aug 12, 2023 22:58:08.028 [139978550663992] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier b70f996f-a139-4098-a80a-afcf344f1718: 0 for XX.XXX.XXX.XX:18311 (responded in 5165 ms)
[chuck@lizum ~.2004]$ grep -i reacha /tmp/reach | grep '1 for'
Aug 12, 2023 22:51:32.950 [139978550663992] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier e7f6ecd1-9690-47c6-ad69-7d558a107c1f: 1 for XX.XXX.XXX.XX:18311 (responded in 697 ms)
Aug 12, 2023 22:51:59.123 [139978548554552] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier 10098ff6-fbe3-4bdd-a1d7-5d07b2e2b79b: 1 for XX.XXX.XXX.XX:18311 (responded in 73 ms)
Aug 12, 2023 22:52:27.641 [139978548554552] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier 169605b0-c871-4ff1-8498-2423eb51edc8: 1 for XX.XXX.XXX.XX:18311 (responded in 172 ms)
Aug 12, 2023 22:53:20.279 [139978548554552] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier fc62c22f-2d07-47ee-908b-23300110fe39: 1 for XX.XXX.XXX.XX:18311 (responded in 173 ms)
Aug 12, 2023 22:53:36.330 [139978548554552] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier d9935704-01bc-4f59-a478-d1b4029c9324: 1 for XX.XXX.XXX.XX:18311 (responded in 718 ms)
Aug 12, 2023 22:54:07.221 [139978548554552] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier 53816e1d-1490-4a6f-9151-863baa790599: 1 for XX.XXX.XXX.XX:18311 (responded in 151 ms)
Aug 12, 2023 22:54:38.480 [139978550663992] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier 0715df2f-9b24-49cd-a13c-7108228798bd: 1 for XX.XXX.XXX.XX:18311 (responded in 181 ms)
Aug 12, 2023 22:55:00.985 [139978548554552] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier 4d101f81-f434-49fb-98b5-d8c135f6513e: 1 for XX.XXX.XXX.XX:18311 (responded in 167 ms)
Aug 12, 2023 22:55:32.924 [139978550663992] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier 538011ca-4978-48c6-8ddd-0e4456b85095: 1 for XX.XXX.XXX.XX:18311 (responded in 169 ms)
Aug 12, 2023 22:55:49.183 [139978550663992] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier c8fd6d27-3024-42f3-928b-3bf340827a4c: 1 for XX.XXX.XXX.XX:18311 (responded in 805 ms)
Aug 12, 2023 22:57:28.162 [139978548554552] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier b529a949-8d60-4121-8e19-a8055eabc65c: 1 for XX.XXX.XXX.XX:18311 (responded in 182 ms)
Aug 12, 2023 22:57:47.580 [139978548554552] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier e4e7808d-a965-4914-b1ac-a2bf5049c6ca: 1 for XX.XXX.XXX.XX:18311 (responded in 185 ms)
Aug 12, 2023 22:59:43.293 [139978548554552] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier a778608e-c6d4-4fd0-bd4b-84a55c11be05: 1 for XX.XXX.XXX.XX:18311 (responded in 178 ms)
Aug 12, 2023 22:59:58.513 [139978550663992] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier 5e9fb3f9-0294-4bf6-89ab-f87fdd85e273: 1 for XX.XXX.XXX.XX:18311 (responded in 174 ms)
Aug 12, 2023 23:00:47.171 [139978550663992] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier 3148d2f1-c57c-4804-a66c-a0a22e865e2a: 1 for XX.XXX.XXX.XX:18311 (responded in 184 ms)
Aug 12, 2023 23:01:11.032 [139978550663992] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier 7edacb5e-e782-47c0-8042-2d554933c51e: 1 for XX.XXX.XXX.XX:18311 (responded in 172 ms)
Aug 12, 2023 23:02:33.969 [139978548554552] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier 467605dc-abd3-4160-88b0-e250616085d2: 1 for XX.XXX.XXX.XX:18311 (responded in 21 ms)
Aug 12, 2023 23:02:53.325 [139978548554552] DEBUG - [EventSourceClient/pubsub/66.175.222.206:443] PubSub: Got notified of reachability for async identifier 40e495f7-4ef5-410a-a41b-e44330556192: 1 for XX.XXX.XXX.XX:18311 (responded in 179 ms)
[chuck@lizum ~.2005]$
I was on the remote access tab yes
You were driving it crazy. It was constantly retesting.
You shouldn’t do that but maybe that’s the problem ?
I need to investigate what Plex.tv does if constantly asked to check connectivity.
So the certificate is not the issue? I also checked the UPnP port thru canyouseeme.org and it says closed. So maybe the router is blocking connection somehow? Manual port forward does not work either
If you verified the manual port forward configuration and could confirm there’s nothing wrong with it but it’s still not working, maybe it’s time to contact your ISP to check if they’re blocking specific ports from being “exposed”.
So I installed a new router, was working for a few minutes as usual after a restart, thew ports were open, then stopped working. I’ve checked windows firewall and running no antivirus.
If you verified the manual port forward configuration and could confirm there’s nothing wrong with it but it’s still not working, maybe it’s time to contact your ISP to check if they’re blocking specific ports from being “exposed”.
I called isp and they have no idea what this means. Should I just fresh install plex on the NAS? I’m out of ideas
DMZ or turning off router firewall is the same story. This is frustrating
Plex will display the remote access status as „green“/working while it’s still checking the status. This can take some time and is causing quite a bit of confusion… if the remote access status is briefly green and then switching to red after a few seconds (up to a minute or so): consider your remote access isn’t working to begin with.
As you’re dealing with the ISP… ignore Plex for a moment and focus only on the manual port forward.
If you configured that on your router but cannot access/see it from outside your home network, they can help with that!
Either they’re blocking some port, keep you behind a CGNAT (treating their backend like a home network to save IPv4 addresses) or give you a pointer if the manual port forwarding isn’t done correctly.
Don’t tinker with those unless you know exactly what you do!!
