The repository 'https://dl.bintray.com/openhab/apt-repo2 stable Release' is not signed. (Raspberry pi 3)

[Schelli (Marc)]

Mine is working again as well, thx for the quick fix.

[John_McC (John Mccracken)]

Hi,

I am getting this error now, is there a way to fix, i am using Rasp Pi 4?

pi@raspberrypi:~ $ sudo apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Ign:3 https://dl.bintray.com/openhab/apt-repo2 stable InRelease
Get:4 https://dl.bintray.com/openhab/apt-repo2 stable Release [6,051 B]
Ign:5 https://dl.bintray.com/openhab/apt-repo2 stable Release.gpg
Reading package lists… Done
E: The repository ‘https://dl.bintray.com/openhab/apt-repo2 stable Release’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
pi@raspberrypi:~ $

[Thomas_Schwieters]

I’m having the same issue. Raspi 3, installation is already few months old and apt update always worked up to today.

Get:11 https://dl.bintray.com/openhab/apt-repo2 stable Release [6,051 B]
Ign:12 https://dl.bintray.com/openhab/apt-repo2 stable Release.gpg
Reading package lists… Done
E: The repository ‘https://dl.bintray.com/openhab/apt-repo2 stable Release’ is no longer signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Is it a problem with the repository?

[marcel_erkel]

The APT/RPM 'testing' (Milestone) repository has moved

Hi all, Due to some space restrictions on the Bintray repository, we are now using Artifactory as our main testing (milestone) repository. Don’t worry, all previous milestones are available in Artifactory if you need them, so downgrading will still work after the move if you need it. The following is only relevent to those wanting the latest milestone releases. If you’re on the old Bintray repo for testing, simply run the commands: You’ll need to update your source lists to accomedate the cha…

Edit: Ah… you’re running stable. Then the link above does not apply.

You did read this?

APT Repo Public Key Expiration & Update

All, Our public key for the APT repos (snapshot/milestones/releases) expires today. We have just extended its validity until 2023 (thanks @theo!), but you will have to make sure that your Linux installation is aware of the new key, otherwise your will have problems when updating openHAB through apt. All you need to do execute: wget -qO - 'https://bintray.com/user/downloadSubjectPublicKey?username=openhab' | sudo apt-key add - Best regards, Kai

[dbghb (db)]

That worked with another recent problem. Does not help now.

[marcel_erkel]

This seems to be the problem. Ben is aware.

APT Repo Public Key Expiration & Update

Is there something else going on with the repo tonight? Unfortuantely there is… at the moment, Bintray can’t sign the repository, which is why you get this error. Hopefully this will be fixed when the right person can get to the problem, but if not I will get a workaround to you as soon as I can.

[John_McC (John Mccracken)]

Hi,

Can I add this line to one of the config files on the SD card when openhabian is doing first boot ?

wget -qO - ‘https://bintray.com/user/downloadSubjectPublicKey?username=openhab’ | sudo apt-key add

[podarok (Andrii Podanenko)]

Looks like key is not working in armbian(ubuntu 19.04)
I’ve managed adding trusted to deb sources list

Force update from unsigned repository Ubuntu 16.04

[avanshee (Avantika)]

E: The repository ‘https://dl.bintray.com/openhab/apt-repo2 stable Release’ is no longer signed.

This is the error I am getting while using the command sudo apt-get update
I did try the above mentioned execution:
wget -qO - ‘https://bintray.com/user/downloadSubjectPublicKey?username=openhab’ | sudo apt-key add
But unfortunately, apt-get update throws the same error again, could you share any solution to this?
I am on a RPi stretch

[marcel_erkel]

There are problems with the repository on bintray. Burkart posted the solution in the other topic to use the repository on jfrog:

@Burkart_Poneleit

echo ‘deb https://openhab.jfrog.io/openhab/openhab-linuxpkg stable main’ | sudo tee /etc/apt/sources.list.d/openhab2.list
sudo apt update

[UlfK (Ulf Kosack)]

Is the repo on jfrog.io a workaround or for permanently use?

Thanks
Ulf

[Raducanu_Radu]

Again not work ?

[djDomino (Kresimir Dzoic)]

I have the same problem…For the first time installed openhab to Raspberry 3 B and on installing mosquitto have this problem. Not signed. Tryed with some others commands but not sucess and for me because I’m beginner in Linux this is pain.

[Jan_Richter]

Still the same here.

[WolfgangJ]

Just did work for me - thanks Marcel !

[PrestigeWorldwide (Mike)]

Could someone please let us know if jfrog.io is temporary or permanent as @UlfK asked? That way we know we need to revisit this some time soon to revert the changes.

[Benjy (Ben Clark)]

I would say for now that using jfrog for stable releases should be a temporary measure.

[fire-fly (TS Chia)]

I am running on ubuntu 18.04
Edited /etc/apt/sources.list.d/openhab2.list.
1st attempt using:-
deb https://openhab.jfrog.io/openhab/openhab-linuxpkg stable main
2nd attempt using:-
deb [arch=amd64] https://openhab.jfrog.io/openhab/openhab-linuxpkg stable main.

Both attempts have the same error message " ‘http://repos.azul.com/azure-only/zulu/apt stable InRelease’ doesn’t support architecture ‘i386’"

[marcel_erkel]

Your Azul repo location does not match with what is listed on this page.

Check your /etc/apt/sources.list file and any files in /etc/apt/sources.list.d/ to locate where you have defined the Zulu repository location and update accordingly.

Then do sudo apt update to activate the new repository location.

[fire-fly (TS Chia)]

Hi
I commented off deb-src http://repos.azul.com/azure-only/zulu/apt stable main in /etc/apt/source.list.
Problem solved.