21.0 release update fails, authenticity error

Get help, report and discuss bugs.
Post Reply
cestlebon
Posts: 21
Joined: 11 Apr 2017, 20:01

21.0 release update fails, authenticity error

Post by cestlebon » 07 May 2019, 19:36

As the subject says, when I run the updater (20->21) I get this error:

Image

Running on a Synology DS918+ NAS (Intel).

I tried the update two times. So is the signature incorrect or the package...?

hugbug
Developer & Admin
Posts: 7386
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: 21.0 release update fails, authenticity error

Post by hugbug » 07 May 2019, 19:53

I've just tested it and it updated fine.

Could it be that your system has some sort of HTTPS interception? Many Windows antivirus do that but I've not heard about this for Linux.

You can install manually, into the same directory. All settings will be preserved.

cestlebon
Posts: 21
Joined: 11 Apr 2017, 20:01

Re: 21.0 release update fails, authenticity error

Post by cestlebon » 07 May 2019, 20:02

There's no https inspection going on so it's not clear what's going on.

I just downloaded the file on my Windows PC and calculated the checksum with total commander and it's different from what's listed the installer:

697b40778dcdc537b981afd23c6b634b *nzbget-21.0-bin-linux.run

but I guess that's to be expected because that's about the payload.

No problem with doing a manual install but I'm a bit curious why the signature doesn't match. Is the MD5 value which I calculated correct?

hugbug
Developer & Admin
Posts: 7386
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: 21.0 release update fails, authenticity error

Post by hugbug » 07 May 2019, 20:22

If you are still not updated we can check if the files coming OK (in that case the verification itself is broken).

In file install-update.sh in nzbget directory (near nzbget-binary) comment out lines 80-81 which remove downloaded installer and signature files.

Then (on a computer) download nzbget-21.0-bin-linux.run and nzbget-21.0.sig.txt and compare them with files downloaded by install-update.sh.

cestlebon
Posts: 21
Joined: 11 Apr 2017, 20:01

Re: 21.0 release update fails, authenticity error

Post by cestlebon » 07 May 2019, 20:54

Both files turn out to be identical so I guess that it's not a corrupted download.

EDIT: and the checksum listed in the signature file is identical to what I calculated and posted earlier.

hugbug
Developer & Admin
Posts: 7386
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: 21.0 release update fails, authenticity error

Post by hugbug » 07 May 2019, 21:02

I'll try to reproduce. Which version was 20.0 exactly? What CPU architecture (saved in file installer.cfg)?
Is file pubkey.pem present in nzbget directory? Please compare with https://github.com/nzbget/nzbget/blob/d ... pubkey.pem.
Thanks.

cestlebon
Posts: 21
Joined: 11 Apr 2017, 20:01

Re: 21.0 release update fails, authenticity error

Post by cestlebon » 07 May 2019, 21:13

That must have been the problem, the file pubkey.pem was not present in the nzbget folder. I recreated it from the github repo and now the installer works. :)

Thanks!

Post Reply

Who is online

Users browsing this forum: sanderj and 6 guests