Expired key issue?

[tdiguy 99]

I am having issues updating emby, i think i found the underlying issue.

This was the original error:

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://download.opensuse.org  Release: The following signatures were invalid: KEYEXPIRED 1500755520

 

W: Failed to fetch http://download.opensuse.org/repositories/home:/emby/xUbuntu_14.04/Release

 

W: Some index files failed to download. They have been ignored, or old ones used instead.

 

So I ran: 

pi@raspberrypi:~ $ apt-key list

 

I noticed: 

2015-05-14 [expired: 2017-07-22]

uid                  home:emby OBS Project <home:emby@build.opensuse.org>

 

so i tried running:

apt-key adv --keyserver keys.gnupg.net --recv-keys <key inserted here>

but i got:

"home:emby OBS Project <home:emby@build.opensuse.org>" not changed

gpg: Total number processed: 1

gpg:              unchanged: 1

 

I am not really sure what to do from here as a work around. When i try doing sudo apt-get install emby it says its at current rev.

 

[rdameron 0]

I have suddenly received the same error. I also tried to update the key and got the additional error communication failed, unknown pubkey alogrithm.

 

The expiration date for the key is listed as yesterday 2017-7-22.

 

Does anyone know why the key won't update?

[Luke 42077]

It's being looked into. Thank you for your patience.

[rdameron 0]

I am using Ubuntu 16.04 and is causing an internal error because the key has expired so it keeps locking up my kodi. So until there is a fix this shuts down my use of kodi and emby and since we use that as our only TV/Movie source this is a problem. I would very much appriciate any info as soon as anyone has any. Thanks.

[Luke 42077]

I am using Ubuntu 16.04 and is causing an internal error because the key has expired so it keeps locking up my kodi. So until there is a fix this shuts down my use of kodi and emby and since we use that as our only TV/Movie source this is a problem. I would very much appriciate any info as soon as anyone has any. Thanks.

 

Hi, this key has nothing to do with Kodi. The only thing it is doing is preventing you from updating to the new release of Emby Server. You should be able to continue to run the previous release you were running on without any problems. Please let us know if this helps. If you still have an issue, then please see how to report a problem. Thanks !

[rdameron 0]

Hi, this key has nothing to do with Kodi. The only thing it is doing is preventing you from updating to the new release of Emby Server. You should be able to continue to run the previous release you were running on without any problems. Please let us know if this helps. If you still have an issue, then please see how to report a problem. Thanks !

 

Just for the record that should be true in theory however in practice when the interl error occours it throws a the error flag which causes a memory issue and locks up kodi making it unresponsive and causing the system to become unstable as the memory can no longer be released until the system is restarted.

[rdameron 0]

Ok maybe this will help other people out with the same issue I had. I found that by disabling all automatic downloading and or installing of the updates stops the system errors and the system now seems to be running stable but still has the expired key issue.

[thatoneguy99 33]

This worked for me. Just follow the key part of the install for whatever version you're on. https://software.opensuse.org/download.html?project=home%3Aemby&package=emby-server

 

 

Sent from my phone!

[siteripper2 0]

Hello,

 

I also have the problem that on XBOX or Android App it says that I need to upgrade to Premium (though I got a lifetime subscription for 3.x). That error occured a few days ago.

 

When I try to upgrade the repository I also get this error:

 

An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://download.opensuse.org/repositories/home:/emby/xUbuntu_16.04 Release: The following signatures were invalid: KEYEXPIRED 1500755520

 

I hope this will be fixed soon

[henryford 11]

Just for the record that should be true in theory however in practice when the interl error occours it throws a the error flag which causes a memory issue and locks up kodi making it unresponsive and causing the system to become unstable as the memory can no longer be released until the system is restarted.

What? You should totally look into that because there is no way this should happen because a signature on a package in the repositories expired. Apt will not lock up your memory because of an expired signature - what are you doing in Kodi that this would lock it up?

[tdiguy 99]

This worked for me. Just follow the key part of the install for whatever version you're on. https://software.opensuse.org/download.html?project=home%3Aemby&package=emby-server

 

 

Sent from my phone!

I can confirm at least for me using the commands from this section:

wget -nv http://download.opensuse.org/repositories/home:emby/Debian_Next/Release.key -O Release.key

sudo apt-key add - < Release.key

sudo apt-get update

 

Updated the key

2015-05-14 [expires: 2019-09-16]

uid                  home:emby OBS Project <home:emby@build.opensuse.org>

 

I can now update.

 

Thank you.

Edited July 24, 2017 by tdiguy

[Luke 42077]

OBS keys expire every two years so what you will need to do is go back to the download page of our website and do the first part of the installation process again, the part where you setup an OBS key. After that you will be able to update. Thanks.

[markofealing 0]

Just upgraded Emby on Ubuntu 16.04 using tdiguy's suggestion above

 

wget -nv http://download.opensuse.org/repositories/home:emby/Debian_Next/Release.key -O Release.key

sudo apt-key add - < Release.key
sudo apt-get update

 

Worked okay

[Luke 42077]

Thanks for the feedback.

[tdiguy 99]

Just to be sure i give credit where credit is due i had followed the suggestion from 

thatoneguy99

 

I simply posted an excerpt from the directions on the link he posted. Ultimately the devs already had the solution to this issue posted. 

[Luke 42077]

Thanks for the feedback. 

[thatoneguy99 33]

Haha. I appreciate that. I actually found the solution this in an old thread. Someone was having problems with the install and the key update was the issue. Tried it and it worked.

 

 

Sent from my phone!