Can't sign-in in PMS 0.9.x / Can't connect to my PMS from PS3

General Discussions
1

Hello,

I’m running PlexMediaServer 0.9.9.10 on a NAS, and have PMP client version 2.13.3 running on my Playstation3 (v1.41).

My PMP won’t connect to my PlexMediaServer. It can’t see it. Now, it’s my understanding that both server and client needs to be signed into plex.tv. I’ve already properly did so on my client PS3, entered the PIN on https://plex.tv/link and all, all good. But when I try to sign into Plex on the server, under Settings / Server, I get “There was a problem signing in to Plex.”. Even so, my plex user does show up under “Users”, but I don’t know what’s that all about (Im new to Plex).

Looking at my Plex Server logs, I see the following error which I think is a problem when I try to sign-in the server:

Mar 30, 2017 16:49:40 [0x4d5ff490] ERROR - Error issuing curl_easy_perform(handle): 35
Mar 30, 2017 16:49:40 [0x4d5ff490] WARN - Error issuing request to: https://plex.tv/users/sign_in.xml (35, SSL connect error) (error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure)

So… any advice ? Anyone else having this issue? And why do I absolutely need to sign into the internet to simply play my media on my NAS ? What happens if my internet provider is down? I can’t play my media then? Is there a workaround for this?

Thank you,
Pat

2

Also, in case it matters, I do see my Playstation3 device under Settings / Devices… Soooo… Puzzled here.

4

What was the point of PMS 0.9.x then? How was it used, if not with the PMP client? And unfortunately, this still doesn’t answer the problem about not being able to sign-in to plex.tv through the server settings page. That error has anything to do in occurrence with my PlayStation… It’s a whole other issue (one which I thought/wonder still if it isn’t the cause of my PS3 not being able to see my Plex NAS server…).

I’d love to upgrade Plex on it, but you’ve got it right: it’s ARMv5 so cannot find more recent versions…

Thanks again for any help…

Pat

5

I’m having a very similar problem

OS: Debian Jessie, freshly installed yesterday and fully up to date.
Plex version (downloaded today on plex.tv, chose amd64 ubuntu version): plexmediaserver:amd64 1.4.4.3495-edef59192

This same ssl error (bad record mac) is coming back when plex tries to hit basically anything on https on plex.tv it seems - this happens when I try to sign into the web interface of my server, when plex is trying to get converters for different codecs… all the time.

I am pretty sure this is the root cause of all my problems.

Plex Media Server.log:Mar 30, 2017 23:17:05.290 [0x7fcb5d3fd700] WARN - HTTP error requesting GET https://plex.tv/api/codecs/h264_decoder?build=linux-ubuntu-x86_64&deviceId=bcf91d48-759a-4a11-a15b-13d357fc756f&oldestPreviousVersion=1.4.4.3495-edef59192&version=7f7c2d3-1195 (0, No error) (error:140943FC:SSL routines:ssl3_read_bytes:sslv3 alert bad record mac)

I’m not sure what SSL library plex uses, but when I use curl or wget to hit these APIs, it does fine without any errors and reasonable xml coming back, so I think the problem lies within how plex uses TLS?

8

trumpy81: > @trumpy81 said:

Like I said, 0.9.x.x is very old now, we have reached version 1.5.2 (for Plex Pass members) already and a lot of things have changed in that time.

Since your NAS is ARMv5 you have no recourse other than to install PMS on a PC/Mac/Linux box or update your NAS to a newer model that is supported by Plex.

Plex no longer offer older versions for download. We have requested that older version downloads be reinstated, but that has fallen on deaf ears so far.

ARMv5 processors are simply not powerful enough to run the latest versions of PMS in a reliable manner, that is why support for the ARMv5 and other processors were dropped over 12 months ago.

See this article: https://forums.plex.tv/discussion/212842/armv5-powerpc-and-readynas-ros4-no-longer-supported-starting-with-plex-media-server-0-9-17-0#latest

trumpy81, thank you for your reply, but this doesn’t answer any questions, really. I am aware that 0.9.x is an old version, but yet, it must have been used with “some client”, somehow… I’ve got no answer for that. If I could find which client then perhaps I could make it work… But regardless, again, this error doesn’t occur when trying to connect my PMP client to my PMS server. It happens when I try to login into Plex by going to Settings / Server, and trying to authenticate from there.

The error it’s generating is a Curl SSL error, return code 35. This curl return code means:

“CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.”

This error DID occur before in the past to others, bearly over 2 years ago. This post shows the exact same problem: https://forums.plex.tv/discussion/124650/unable-to-login-to-plex-from-server-setting/p1

As it turns out, 2 years ago, some Chris C Plex employee answered that post stating that: “SSLv3 was turned off on some of our hosted servers, which caused the issue with signing Plex Media Servers into your Plex account”

Sorry but, I’m tempted to think it is Plex that is messing around the certificates and ■■■■! Seeing how they removed archives for older versions, I wouldn’t be surprised if it’s them intentionally breaking it as to force people to upgrade! What a wonderful world we live in: consume, consume, consume…

So, I do not believe this case to be resolved :frowning:

9

UPDATE: Trying a simple curl get using SSL3 on https://plex.tv/users/sign_in.xml page the server is trying gives me this:

root@datahub:~# curl -v --sslv3 https://plex.tv/users/sign_in.xml

  • Trying 52.214.149.31…
  • TCP_NODELAY set
  • Connected to plex.tv (52.214.149.31) port 443 (#0)
  • ALPN, offering http/1.1
  • Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
  • successfully set certificate verify locations:
  • CAfile: /ffp/etc/ssl/cert.pem
    CApath: none
  • SSLv3 (OUT), TLS handshake, Client hello (1):
  • SSLv3 (IN), TLS alert, Server hello (2):
  • error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
  • Curl_http_done: called premature == 1
  • Closing connection 0
    curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure

It’s the exact same error as in the “Plex Media Server.log” !

The same thing happens with wget:

root@datahub:~# wget -v --secure-protocol=SSLv3 https://plex.tv/users/sign_in.xml
–2017-03-31 12:43:40-- https://plex.tv/users/sign_in.xml
Resolving plex.tv… 54.77.213.127, 52.214.149.31, 52.210.223.97, …
Connecting to plex.tv|54.77.213.127|:443… connected.
OpenSSL: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
Unable to establish SSL connection.

I’ve tried this on both my NAS, and MAC OS X. Same results (obviously). So, this really lets me think that it is Plex that’s messing around with their SSL implementation on their servers…

11

@trumpy81 said:
What part of NO LONGER SUPPORTED do you not understand?

Do you really expect support for that version of the software and your NAS which has not been supported for over 12 months?

It’s time to move on, sorry, but that’s just how it is.

Well, you’re kind of a d** by talking to me like that! I am not asking for official support from Plex staff… I am on an internet FORUM! And guess what… it IS the internet, so people do keep track of older sh**t! And again, that version of PMS must’ve been used with SOME Plex Client… even that wasn’t answered for!

As for the PMS server part, it’s an SSLv3 error! The fact is: it won’t connect using SSLv3 on the plex.tv servers, because, I believe, Plex changed something on their end…

So, trumpy81 / Plex Ninja, unless you’re going to tell me something different than “upgrade your NAS, go spend 500$ on a new plastic box”, just please, do not reply… Even though, yes, I did appreciate your first reply, honestly.

13

@trumpy81 said:
Plex no longer uses SSLv3 for sign in, this has been documented in the forums and various other places, which is basically what I have been trying to tell you, your version of PMS will no longer work. You can bang your head against the wall all you like, but it wont change anything.

Upgrading your NAS is not the only advice I gave you, but you seem to have chosen to ignore that, I’m sorry, I wish things were different, but I don’t have a magic wand to fix it for you. I can only tell you how things are, what you do with that information is up to you.

If you are a Linux/programming guru, then by all means keep trying to fix the issue, I’m sure there would be others who would appreciate your ‘fix’, but until then, there is nothing anyone can do for you.

Well, now, I have a real answer: “Plex no longer uses SSLv3 for sign in”… And no, this was not what you were telling me! Yes, I am IT, and therefore being given a “your device is no longer supported” simply doesn’t suit me. As it turns out, yes Plex DID, in fact, change their authentication method on their website, as I expected! Seems to me like it’s now using TLSv1, and has turned off SSLv3! Bummer …

If you knew this, trumpy81, you simply could have said this instead of all this talk for nothing. Otherwise, one like myself, just assumes Plex decided to longer offer old versions for downloads. You cannot go and just say “you’re no longer supported”, or if you do, well complement the answer by adding “therefore removed the older authentication method, and that is why you cannot login…”.

As for your other advice, I haven’t ignored them. The thing is, I do not have a tower running Linux/Windows/Whatever on which I could install the latest Plex server. I’d love too, but sh**t me, I left my old towers back in Canada 3 years ago when moving to Europe. All I’ve got with me now is my good old NAS, my MAC laptop, and a PlayStation3… (apparently, sucks to be me I guess). So, seems like you were advising to either throw in money for a new tower running Linux or whatever, or upgrading my NAS. Comes down to that :wink:

All that login problems being said, I still wonder: what client DID connect to PMS0.9.x still? Perhaps I could find a version that would connect to it, IF we can connect to it WITHOUT internet / without having to authenticate to the Plex.tv website. Now, I believe the latter should be possible, no? I did see an option in the Plex: “Settings / Server / Network: List of networks that are allowed without auth”. Just guessing this would be it, no? If not, and if I’m told Plex HAS to sign into the website to play your own, local media, then, I raise my middle finger to Plex, cause that would just be plain stupid: what if you’re internet provider is down? Can’t watch your movies?

Thanks for any help regarding this last point.

Regards, Pat

14

Having tested again with curl -v --sslv3 (which yes did fail like trumpy81 said) and openssl s_client (which surprisingly, worked fine - I guess plexmediaserver doesn’t use the system openssl then…), I don’t get the exact same error message as ravenlost.

So I will take your advice and post on the linux forum. Perhaps someone can help me there.

However, if a fresh install that I literally just downloaded yesterday from plex.tv on a fresh operating system I installed 2 days ago can have ssl errors trying to sign in, I will hazard a guess that maybe ssl errors are coming from something plex did, even if it effects different versions of plex different ways. Again, I have no idea really because I don’t know how Plex builds their non-open software. Hopefully somebody can point out a fix.

15

If I may enlighten?

SSLv3-anything is no longer supported in any way. There is no compatibility / no fix.

This is because of the encryption vulnerabilities published about ssl v3.
As one such reference: https://access.redhat.com/articles/1232123 (Kindly note the date)

SSLv3 was removed and PMS + Plex.tv upgraded to TLS.

Not to sound cold, there is no ‘fix’ if one is using a server which is too old to speak TLS to Plex.tv

16

As one final clarification (apologies for omitting).

PMS 0.9.16.6 is the lowest version which operates with current infrastructure. While not complete, it does have proper basic functionality. Anyone using such a version is well advised to upgrade before full database compatibility is lost (too many migrations)

17

@ChuckPA said:
If I may enlighten?

SSLv3-anything is no longer supported in any way. There is no compatibility / no fix.

This is because of the encryption vulnerabilities published about ssl v3.
As one such reference: POODLE: SSLv3 vulnerability (CVE-2014-3566) - Red Hat Customer Portal (Kindly note the date)

SSLv3 was removed and PMS + Plex.tv upgraded to TLS.

Not to sound cold, there is no ‘fix’ if one is using a server which is too old to speak TLS to Plex.tv

Thank you ChuckPA. And is there a way I can find out starting which version of PMS did support TLS? I just read on another forum a version history:

0.9.11.1
Oct 15, 2014
New
Added Hebrew translation.
Fixes
(Linux) A crash on Linux when media directory permissions were wrong.
Rapid seeking could lead to video playback stopping.
Improved reliabilty around publishing network connections.
Use TLS instead of SSLv3 when talking to plex.tv…

Don’t know if it’s the true thing, but now seems like I have to find THAT particular build, for ARMv5, compiled against GLIBC 2.5 (found some other ones, up to v. 0.9.16.6, but they were compiled with GLIBC 2.7… so it won’t run on my setup).

Also, I’d still love to know if it is possible to use PMS 0.9.x / and client without authentication to the plex.tv site?

Thanks !! Pat

18

First off… ARMv5 was discontinued as of 0.9.17.0 when PPC processors were. The highest ever created was 0.9.16.6. Since 1.0.0, all older versions have been removed and are no longer available. This is true of the Downloads page currently. You have Plex Pass and Public (both current) but nothing more. This was a management decision.

IF you manage to get lucky and find what you’re looking for, great. Unfortunately, there is nothing we can do nor are there any binaries, urls, or anything we could link to if we were even allowed.

EDIT: In closing, 0.9.16.6 is the minimum level… Barely minimum. Soon, it will be too old and no longer be supportable in any way.

19

I just wanted to come back to this thread and say I figured out a work around for my issue. See my other thread at https://forums.plex.tv/discussion/265701/openssl-errors-when-plex-media-server-tries-to-talk-to-plex-api-or-download-codecs/p1?new=1 if you want to know more.

20

I think this thread has served its usefulness.

Thanks.