Jump to content
bobdob

Emby Premiere key is missing or invalid.

Recommended Posts

bobdob

I am adding emby server to shield and ran into a few problems . I was able to activate my emby premiere key a few times and it worked.

 

I was having a problem using xml.gz file and it was taking up tons of space in my TEMP folder so I did a few uninstalls and re installs before i figured out the problem.

 

Now the thing is emby wont accept my premiere key on the shield only.

 

I removed the key on my PC and re added it no problem just the shield doesn't like it. Did i get blocked from the sever for to many attempts?

embyserver.txt

Share this post


Link to post
Share on other sites
ebr

Hi.  No it looks like a network configuration issue.  All outbound requests are failing.

	System.Net.Http.HttpRequestException: System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception. ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. ---> Mono.Btls.MonoBtlsException: Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED

Share this post


Link to post
Share on other sites
bobdob

It works on same network when i remove key from 2 other servers

Share this post


Link to post
Share on other sites
bobdob
Posted (edited)

This is from same network works no problem
 
something else is going on

 

it worked earlier and i havent changed anything 

embyserver (1).txt

Edited by bobdob

Share this post


Link to post
Share on other sites
ebr

Right, the issue is undoubtedly in the configuration on the Shield.

Share this post


Link to post
Share on other sites
bobdob

When i first tried like i said it worked until a few installs and un installs.

 

I just tried it on another shield that has never had the emby server on it. It doesn't work either.

Share this post


Link to post
Share on other sites
bobdob

AND with no changes made it worked this morning  :mellow:

Share this post


Link to post
Share on other sites
ebr

Yep, this was the same global SSL issue that was causing problems on the Roku.  We were able to work around it last night.

 

Thanks.

Share this post


Link to post
Share on other sites
seacoug

Yep, this was the same global SSL issue that was causing problems on the Roku.  We were able to work around it last night.

 

Thanks.

 

Can you please quit telling people that this is a problem with their network and elaborate.  I was one of the people who posted this in the Roku forum and you would have me wasting a lot of time on troubleshooting that is not related to the problem. 

Share this post


Link to post
Share on other sites
ebr

Can you please quit telling people that this is a problem with their network and elaborate.  I was one of the people who posted this in the Roku forum and you would have me wasting a lot of time on troubleshooting that is not related to the problem. 

 

Very sorry but every single instance of this issue before yesterday has been due to local network configuration.

 

What happened yesterday was a global thing with certain old systems (the Roku being one of them and some flavors of the system under which our server runs on platforms like Android and Synology being the other).

 

Roku, themselves, fixed the issue for them and we were able to work around it for the other server platforms.

 

Thanks.

Share this post


Link to post
Share on other sites
seacoug

In other words the Roku client needed to be updated.  I don't think you would be supervised to learn that this functionality returned without me changing anything on my firewall or router.  

Share this post


Link to post
Share on other sites
Luke

It was not our app but The Roku firmware that needed the update.

Share this post


Link to post
Share on other sites
seacoug

So that it was congruent with your server right?

Share this post


Link to post
Share on other sites
ebr

So that it was congruent with your server right?

 

No.  This issue had absolutely nothing to do with our code.  It was related to the age of the Roku OS.

Share this post


Link to post
Share on other sites
ebr

If you would like complete details here is the nitty gritty from UC Berkeley: https://calnetweb.berkeley.edu/calnet-technologists/incommon-sectigo-certificate-service/addtrust-external-root-expiration-may-2020

 

The Roku OS was using OpenSSL 1.0.0 (very old).

 

And Mono (the system under which our server runs on Android and Synology - only) is also apparently using a similarly old version of the networking protocol.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...