Hi @BigWheel, I’m having this issue as well. Could you please reset my certificate?
@richlawson reset. I think you will need to restart
Thanks! That fixed it for me.
I have exhausted everything possible in my network to resolve this remote access issue to include, reinstalling plex, resetting password, upnp on/off/auto/disabled, windows firewall on/off, port 32400 manually forwarded to static assigned server, another set of eyes on my config, now the other person is complaining that since they started looking at my issue, they now notice their server is doing the same thing and nothing resolves it. It used to work without issue. Am I missing something ??
@greasedpig I reset your cert. may want to restart
1 Like
5 posts were merged into an existing topic: Can’t sign into web app
3 posts were split to a new topic: Can’t sign into web app
@BigWheel Can you reset mine too?
So sorry for the delayed response, but this did the trick ! My flopping server stopped flopping !
1 Like
@youcube are you still having issues? can you restart your server
I am still getting the “cannot connect to server securely” error. I can connect locally insecurely via http://LocalserverIP:32400/web. I deleted the cache, restarted the server but still getting the same error. On other devices via app, there is no such problem.
this is via https://app.plex.tv you mean?
it does not look like remote access is enabled on your server does that fail when you try or did you just not need/want remote access. I did reset your cert so seems like something else is amiss.
I seem to be having this issue now. Here is what I found in the logs. Can you help?
Feb 03, 2022 18:03:58.658 [10828] DEBUG - CERT: incomplete TLS handshake from 127.0.0.1:51030: sslv3 alert bad certificate
Feb 03, 2022 18:04:03.963 [10824] WARN - [CERT] TLS connection from 192.168.1.125:28636 came in with unrecognized plex.direct SNI name ‘192-168-1-124.4385a369d66c432db2e3f5421c01548e.plex.direct’; using installed plex.direct cert
Feb 03, 2022 18:04:03.971 [10828] DEBUG - CERT: incomplete TLS handshake from 192.168.1.125:28636: sslv3 alert certificate unknown
Feb 03, 2022 18:04:03.986 [10824] WARN - [CERT] TLS connection from 192.168.1.1:28637 came in with unrecognized plex.direct SNI name ‘97-113-114-105.4385a369d66c432db2e3f5421c01548e.plex.direct’; using installed plex.direct cert
Feb 03, 2022 18:04:03.995 [10828] DEBUG - CERT: incomplete TLS handshake from 192.168.1.1:28637: sslv3 alert certificate unknown
Feb 03, 2022 18:04:04.233 [10824] WARN - [CERT] TLS connection from 127.0.0.1:51032 came in with unrecognized plex.direct SNI name ‘184-105-148-84.4385a369d66c432db2e3f5421c01548e.plex.direct’; using installed plex.direct cert
Feb 03, 2022 18:04:04.397 [10828] DEBUG - CERT: incomplete TLS handshake from 127.0.0.1:51032: sslv3 alert certificate unknown
@dTardis just reset for your server that ends in 17. You may need to restart server.
Will do. Thank you!
OK I seem to be back in business! Thank you for the quick turnaround.
Is there anything I need to do in the future to avoid this happening again?
not sure if anything you did. Did the IP address of computer change?
It shouldn’t have. Things are fairly static on my network…
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
