do you have your own cert in use?
May I have your logs ZIP?
I shutdown the server, deleted the two certificates. Then restarted. After a few minutes both certificates re-appeared, as expected. Sadly, problem remains. How do I send you my logs?
your PM.
duh. on it.
To answer your question, no, Iām not currently using my own certs. Although I was thinking about using my own again, since yours arenāt working. I used to use my own, but havenāt for a year or soā¦ Maybe Iāll do an experiment today and see if that worksā¦
-d
you canāt use your own certs to talk to plex.tv
You can only use your own certs in addition to plex.tv
I will give this a reset for you.
I was hoping that we could use your situation as one of the cases weāre trying to capture but Iām not sure if itās there yet.
I need to see what your server does in those first 2 minutes after startup as it registers and settles with MyPlex.
can you tolerate it being down a few more minutes?
shutting down now. Just boofed a few recording, but I donāt really give a rip.
If we solve this, its all worth it.
Thanks!
-d
give it a restart.
wait 2 minutes.
pull logs ZIP
send in the PM
I will look quick and reset if not the exact case we need captured (likely not)
so i installed the pluginā¦now i see the new server
Hi,
Iāve restarted my PMS and downloaded the logs. Theyāre attached here. Is there anything more I need to do? Plex Media Server Logs_2020-10-11_16-21-54.zip (3.6 MB)
Your server is connecting to Plex.tv and publishing itself as it should.
Plex.tv can see it is reachable (return code = 1 == True)
Go to those devices which cannot see it and, if TVās / device apps, āresetā and pin them again to the server.
Oct 11, 2020 16:13:18.141 [9052] DEBUG - PubSub: Got notified of reachability for async identifier 54afaeac-9179-4aeb-a2dc-68c8644e72d2: 1 for 59.102.41.120:32400 (responded in 1588 ms)
Oct 11, 2020 16:13:18.141 [9052] DEBUG - MyPlex: reachability check - current mapping state: 'Mapped - Publishing'.
Oct 11, 2020 16:13:18.141 [9052] DEBUG - MyPlex: mapping state set to 'Mapped'.
Oct 11, 2020 16:13:18.146 [9052] DEBUG - Auth: authenticated user 1 as ProfessorChaos14
Thank you! Not sure what did it but itās now accessible.
Iām currently on 1.20.3.3421 on my Synology DiskStation. For the past 3 updates, Iāve had no remote access. Wired and wireless on my network, everything works perfectly. If I turn wifi on my iPhone off and try to access my Plex server, Iām still able to access under my account. however, everyone Iām sharing with is unable to access my server. Iāve tried restarting my server and having the people Iām sharing with logout and log back in and see if they can try to connect again. No success. Everything was working perfectly up until about 3 updates ago. Iāve even double checked that my router hasnāt magically changed and the port is still being forwarded as well as UPnP being turned on. All good there. Iām attaching my logs. Hopefully you, or someone, can see something that I canāt.
Sorry, @ChuckPaā¦
I just saw a reply from you on another post. If its the same answer, please disregard.
You really might want to not configure your adapters this way. It will confuse DSM.
Oct 12, 2020 07:55:52.102 [0x7f28c520e780] DEBUG - NetworkInterface: Notified of network changed (force=0)
Oct 12, 2020 07:55:52.102 [0x7f287ae6b700] DEBUG - NetworkInterface: Watching for changes on the interfaces.
Oct 12, 2020 07:55:52.102 [0x7f28b0587700] DEBUG - HTTP requesting GET http://plex.tv/pms/:/ip
Oct 12, 2020 07:55:52.102 [0x7f287a88f700] DEBUG - HTTP requesting GET https://plex.tv/api/v2/user?includeSubscriptions=1&includeProviders=1
Oct 12, 2020 07:55:52.104 [0x7f28c520e780] DEBUG - Detected primary interface: 192.168.1.150
Oct 12, 2020 07:55:52.104 [0x7f28c520e780] DEBUG - Network interfaces:
Oct 12, 2020 07:55:52.104 [0x7f28c520e780] DEBUG - * 1 lo (127.0.0.1) (loopback: 1)
Oct 12, 2020 07:55:52.105 [0x7f28c520e780] DEBUG - * 3 eth0 (192.168.1.150) (loopback: 0)
Oct 12, 2020 07:55:52.105 [0x7f28c520e780] DEBUG - * 4 eth1 (192.168.1.151) (loopback: 0)
Oct 12, 2020 07:55:52.105 [0x7f28c520e780] DEBUG - * 1 lo (::1) (loopback: 1)
Oct 12, 2020 07:55:52.105 [0x7f28c520e780] DEBUG - * 3 eth0 (2600:6c40:4500:1093:211:32ff:fec5:e35) (loopback: 0)
Oct 12, 2020 07:55:52.105 [0x7f28c520e780] DEBUG - * 3 eth0 (fe80::211:32ff:fec5:e35%eth0) (loopback: 0)
Oct 12, 2020 07:55:52.105 [0x7f28c520e780] DEBUG - * 4 eth1 (2600:6c40:4500:1093:211:32ff:fec5:e36) (loopback: 0)
Oct 12, 2020 07:55:52.105 [0x7f28c520e780] DEBUG - * 4 eth1 (fe80::211:32ff:fec5:e36%eth1) (loopback: 0)
Oct 12, 2020 07:55:52.105 [0x7f28c520e780] DEBUG - Creating NetworkServices singleton.
Oct 12, 2020 07:55:52.105 [0x7f28c520e780] DEBUG - NetworkServices: Initializing...
Oct 12, 2020 07:55:52.105 [0x7f28c520e780] DEBUG - NetworkService: Creating new service.
Oct 12, 2020 07:55:52.105 [0x7f28c520e780] DEBUG - NetworkService: Got notification of changed network (first change: 1)
Any traffic inbound on 151 will be seen on 150. PMS listens on 150 (the default but PMS will respond on either of the two because both are on the same subnet. This is not desired for Remote Access.
As counterpoint to "past 3 updates ", I only offer that itās always been this way because :
- That how TCP/IP works
- Thatās how DSM constructs the route tables (source of the remote access woes) during startup.
If anything, this is more directly linked to DSM updates than PMS updates but I do advise either making a proper subnet or bonding the two into a single adapter
My remote access stopped working a little bit more than a week ago as well.
So, I did bond the two network interfaces into one to see if that helped. No difference yet. I checked for updates to DSM and updated from 6.2.3-25423 to 6.2.3-25423 Update 2. I had been on the 6.2.3-25423 release since May and my Plex serverās remote access was reachable up until a couple weeks ago so, Iām already thinking a DSM update will not do anything at this point. After the DiskStation restarted, I tried logging into the server to see if anything changed and still nothing.
When I have the āManually specify public portā option deselected (auto-generates a public port), I get the MyPlex: attempted a reachability check but we're not yet mapped. warning.
When I manually specify the public port, I get the HTTP error requesting GET https://XXX-XXX-XXX-XXX.X.plex.direct:28294/identity (60, SSL peer certificate or SSH remote key was not OK) (SSL certificate problem: unable to get local issuer certificate) warning.
btw: A couple of days have gone by since you āresetā me, and Iām still not up and running. Remote access continues to be broken 
-d
I can only reset the certificate and thatās not a 100% guarantee. It might not be certificate related.
Are you 100% certain that nothing else has changed?
Everything restarted since then? (including modem/router)
Restart (start up) the server. I see it offline now for 19 hours.
