PMS is off. I have it running on the only user account on the Mac.
If you open a terminal session,
then cd "~/Library/Application Support/Plex Media Server/Cache"
followed by ls -la
Are all the files owned by your username and do they all have minimally -rw-r–r-- permission ?
Yes. Everything is -rw-r—r— or better.
Ok… that is good so far.
Next,
cd ..
cat Preferences.xml
Look through that XML for PlexOnlineToken="something".
Make sure there is actual hashed text between the quotes.
PlexOnlineUsername=“Your Username”
PlexOnlineEmail=“Your account email”
it’s ~/Library/Preferences/com.plexapp.plexmediaserver.plist on Mac, but I found the PlexOnlineMail and PlexOnlineUsername and they are correct.
I have no clue why PMS isn’t working correctly for you.
I’m a linux guy (desktops, servers, and NAS boxes).
As a test,
Is it possible to rename “Library” to “Library.save”
and then setup a TEMPORARY server to see if there is something else wrong?
If there’s something wrong in your PMS files, the new server instance will start and be claimable with ease.
The only thing I’d recommend is giving it a friendly name of “TEST” so as not to confuse with the saved “production” one.
Thank you for the help. I will see if there is a Mac forum thread. I found this one through google, and didn’t realize it was linux until after we started chatting.
that being said, logging out on my devices has allowed them to connect initially. If the app restarts, it seems to lose access unless I log out and back in. So I do think there is still a certificate issue of some sort.
Thanks again. It’s late here, and I will look at this again another day.
Recently, I have been unable to connect to my plex server via my custom URL - When I check the cert info in Chrome, I get the following:
Can you re-issue this cert?
If you look at who it’s issued to, (your Synology NAS),
and confirm who issued it , (Synology)
then you need to go and update the certificate yourself.
That does look like a Let’s Encrypt certificate given it expired after 90 days.
Seems like every day or two, the server becomes effectively unusable, necessitating a restart. (Videos wont load, some users cant view library, etc) Checking the logs, i seem to get dozens of messages like this, from a variety of addresses
Jul 26, 2022 06:30:59.085 [7780] DEBUG - CERT: incomplete TLS handshake from [::ffff:95.xxx.xx.115]:60626: wrong version number
As well as, a bit later, some bad HTTP requests:
Jul 26, 2022 06:32:29.594 [7820] ERROR - Error parsing HTTP request: ¼eQó2àwŠ7Œ,˜‹róµØMvj8(£ã¤åBc¤ª³Ùçvâ<Gæóãᾪ<²9E¼)æC%£{.ú
«Õ¦ìm˜$²È¿x&£ÙHop!ë‚(ÿ@ñò±›X–ã¶Xœ.–
YH‹+…§É§xsRe1I¯ò9Yo2v™ÅçÙŽSå$S ªUë˜Æ«H"/ X ”µ;ÅǼ˜~på£;o©R/GU¹ù~(“ÜK0ž÷'uÌf<D×j¨Í½ÎöPJŸèÑÏ–Á¡šo÷x\¸…!ò³î¬zš¿êÜ–Ê¢.”h¾·KJiÓ>nCÃ%8Ìv8¢L8ô‚!ñ¯ý#ü”`ôÏ<óPFX9#†â«Ó Ž"§Ÿ_a῾¼yrúÕês“Á1mOXÍ[„Áç±\¯Õ§,ÇR×’>x½•A¿~XQœ§9ÆJ˜(’›åí0òf…éäa;>Ö(Èؽ¯ß•—=a£Ž¡IûWGıŽï vààÙ³h©åžå‡„bíâËÒ·9eSÄKbÖŒ
4‘8P_þÁÅGü_Ì!³Aýþm&Æ,¼½ÑÎËȺW‹Îö戛Ï$R<Û
5 ºÂiîŒbÆØF^²CÔÂBˆI¯À¿
Uploaded my logs, “Plex Media Server 1.log” just after Jul 26, 2022 06:30:48.080 shows the above
I have a moderate number of users, so seeing a number of IP addresses isn’t out of the norm for me.
Restarting the server resolves the issue immediately. Hoping to find a fix other than setting up a job to detect failure and forcing a restart.
Thanks so much!
I’m sorry, your logs do not match the date.
We need 2022 
Welp i feel like an idiot.
Here’s the current one
Plex Media Server Logs_2022-07-26_10-15-07.zip (4.4 MB)
There are problems on the source (sender) side.
Jul 26, 2022 03:47:10.101 [7820] DEBUG - CERT: incomplete TLS handshake from [::ffff:XX.XXX.XXX.XX]:47367: tlsv1 alert unknown ca
Jul 26, 2022 03:47:15.925 [7820] DEBUG - CERT: incomplete TLS handshake from [::ffff:ZZ.ZZ.ZZ.ZZZ]:52939: wrong version number
Jul 26, 2022 03:47:17.544 [7820] DEBUG - Request: [YY.YY.YYY.YYY:58935 (WAN)] I (30 live) #2e8380 Signed-in
Jul 26, 2022 03:47:17.544 [7820] ERROR - Error parsing HTTP request: \F2\AE H\81\D3a-\E6Nݧ\9Ee\9BdԮ\83F\B2\F2\C7}\E6\94\00\B8C\BA\86\95\82\B2\90\83Op\EAxYL!\CD\F3<\E4
p}Evt$
1RS\88\8D\C98c&\96+r\87\E2\8D\C2\EF|\E1e\E6D(\9A\E1\B2\FE\94I|=!DO\FCq\F5\8AdtA@\A2_Xl\CCW'\E2\BF! x \B5ju\BD\EC\AE<\ED\D7Pc\D2䁍X)\i\BDqm\C1\F5\FA\A6\FAԕ\9A\9A\80P=\CB\F0y\86\C4o·4=[]j&\80\9F<X\E0\A7\FEa\94a\B8Nމ\BB\80\8D/\97F֕8\A42BC@\BB\9B\82\92\BA\9E\D9\DBBދ蘖*\E9\9D3Y\F6\91].\AA\A3\83:\DA4N\810O\A1\E9Fe\9F#\E6\A6\C5\C1\87@\D6L\F8\86\E4\A9`\E3|<\E5_\C8\C1\A0쐚Yz\9C\EDb\9B\97\8D
x\E4eS#\C4Y\E9z7/T\F4\AE\A7y\AD\F9G\DDu\A1L\F2\A3M}/\AF\F8\82\E3O\98\B2GAXC\B1di}O\FDو\9A\F7ļ\E02\D5)\8A\BA\00\FEe\89^\98\D3ɩ\85\B2\B6 \B3Ke\DE|\C6a\FA\AD\E8J]As\DC
\E2\A0tOMH\AC
The errors are self explanatory.
-
TLSv1 - Unknown CA (The Certificate Authority is unknown). This will happen when a self signed certificate is used (not allowed – cannot be verified publicly)
-
Wrong version number - The TLS version is too old/unknown
The error text which follows show what it tried to do with what it got – which is jibberish.
Given you have other clients which are successful , I point the problem to those specific clients . You service is fine.
Thanks for having a look. Strange that it works fine for them for a day or two then dies all at once for a number of clients. I will test further next time it happens and confirm whether it actually still works for me or not.
Appreciate it!
2 posts were split to a new topic: Nvidia Shield Pro - Cert errors - usage
6 posts were split to a new topic: PMS and unsavory hosts
Thanks for the advice, and sorry for the late reply!
Yes, it’s the Plex app on Shield TV (Pro) and Plex Server on Shield TV (Pro).
It turns out that the certificate thing happens on and off. I can fix it by resetting the server and sometimes even by just restarting it, but it’ll always be back.
I did exactly what you suggested right out of the gates. Clean install. Update. Plex, then the streaming services. Also tried adding an exception for DNS rebind protection in the router - to no avail (though I might have used the wrong thing there).
We mostly use the Shield for Plex and sometimes for watching shows, but there are hardly any apps running at any given time.
There’s also now an additional issue with it constantly getting stuck while scanning library files, so I’m pretty close to just giving up on the Shield and using something less convenient as a Plex server. Would like to at least try the reset first, though, to see if the certificate stuff can be figured out.
If I may get technical here.
- Remember, the shield is a player (by design)
- The storage in the Shield Pro is, obviously, SSD and it’s not that large.
- Most importantly, there are no published spec on its TBW endurance.
- From what I’ve seen, when the SSD starts coughing errors (it’s used up), the device is done – UNLESS – you’re willing to get parts and do all the crazy work to perform a factory setup of the SSD (clone, block for block mirror, as much as you can from old to new then reinstall fresh – assuming the critical info wasn’t damaged)
For all these crazy reasons, I don’t use the Shield Pro as a server.
It’s nice for light, occasional, usage because of its convenience.
I would not use it as the main, daily-driver, server.
i’m also now getting the same error message as many others on this thread.
i’m able to PLAY content but i get this log line when i try to download media to my phone or tablet.
CERT: incomplete TLS handshake from aa.bb.cc.dd:eeeee: sslv3 alert bad certificate
so far i’ve tried
- downgrading (from 1.28.0.5999 to 1.27.2.5929
- disabling ipv6 (i wanted it off anyway)
- restarting PMS
- removing cert-v2.p12 (and confirming a new one was downloaded
- checking file and dir permissions (all owned by plex user, most files 0644, some 0600)
my cert looks fine to me when i check it with openssl s_client | openssl x509 (and with browser) but maybe something is off?
Is that coming from a player?
If so (which I suspect it is), which player ?
If a TV, please share make , model, and year.
