Jump to content

Stable 4.0.2.0 - Now Available for All Supported Synology / XPEnology Systems


solabc16
Go to solution Solved by solabc16,

Recommended Posts

solabc16
Hello All
 
The latest release of Emby Server (4.0) is now available, thanks again - and as always, to the collective efforts of the many people involved.
 

Please feel free to leave any brief comments and feedback here.

 

If you have a specific issue, have a look in the forum and if you can't find what you're looking for, feel free to open a new topic.

 

Best

- James

 

Link to comment
Share on other sites

solabc16

Hello @@WeidnerJ

 

We do get (very) occasional reports of this happening, which are sometimes caused by a failure to validate the packages signature.

 

The first thing to check is that the Emby LLC certificate exists in Package Center.

DSM -> Package Center -> Settings -> Certificate

Running behind a VPN or where there are restrictions on Internet access can also be a factor.

 

Let me know on the above first and we can take it from there.

 

Best

- James

Link to comment
Share on other sites

WeidnerJ

Hello @@WeidnerJ

 

We do get (very) occasional reports of this happening, which are sometimes caused by a failure to validate the packages signature.

 

The first thing to check is that the Emby LLC certificate exists in Package Center.

DSM -> Package Center -> Settings -> Certificate

Running behind a VPN or where there are restrictions on Internet access can also be a factor.

 

Let me know on the above first and we can take it from there.

 

Best

- James

 

 

Not using VPN of any type on my NAS, and using Google Fiber as my ISP.  At one time the certificate did work, that is how I initially got it installed.

 

5c6ddcf450cd6_Capture3.jpg

Edited by WeidnerJ
Link to comment
Share on other sites

WeidnerJ

 

Hello @@WeidnerJ
 
That looks sensible, are you running behind a VPN or have any other restrictions in place?
 
Best
- James

 

 

No I am not.  My NAS isn't running VPN on it, and using Google Fiber as my ISP.  No difference since the last time that I updated (that I know of).  

Link to comment
Share on other sites

solabc16

Ok @@WeidnerJ, curious.

 

As a workaround you can try temporarily switching the setting "Allow installation of packages published by" from "Synology Inc. and trusted publishers" to "Any publisher".

 

Be sure to switch it back once the install has completed. Let me know how you get on.

 

Best

- James

Link to comment
Share on other sites

WeidnerJ

That worked.  Thank you.  

Ok @@WeidnerJ, curious.

 

As a workaround you can try temporarily switching the setting "Allow installation of packages published by" from "Synology Inc. and trusted publishers" to "Any publisher".

 

Be sure to switch it back once the install has completed. Let me know how you get on.

 

Best

- James

Link to comment
Share on other sites

solabc16

Thanks for the update @@WeidnerJ, glad to hear you're up and running -  I'm hopeful we'll eventually track down the underlying cause.

 

However, it's tricky, as it only seems to affect a very small minority of users and even then, it may happen only once.

 

I take it up until this point, you've had no issues?

 

Best

- James

Link to comment
Share on other sites

WeidnerJ

Correct, no other issues other than unable to update that one time.  

Thanks for the update @@WeidnerJ, glad to hear you're up and running -  I'm hopeful we'll eventually track down the underlying cause.

 

However, it's tricky, as it only seems to affect a very small minority of users and even then, it may happen only once.

 

I take it up until this point, you've had no issues?

 

Best

- James

Link to comment
Share on other sites

  • 1 month later...

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...