Can't install balenaEtcher via apt on Ubuntu 20.04.2 LTS

balenaEtcher
1

Hello! I want install balenaEtcher via apt on Ubuntu 20.04.2 LTS. I use this tutorial to do it. Here is my terminal output:

alvinseville7cf@alvinseville7cf-VPCEB4Z1R ~> echo "deb https://deb.etcher.io stable etcher" | sudo tee /etc/apt/sources.list.d/balena-etcher.list
[sudo] password for alvinseville7cf: 
deb https://deb.etcher.io stable etcher
alvinseville7cf@alvinseville7cf-VPCEB4Z1R ~> 
sudo apt-key adv --keyserver hkps://keyserver.ubuntu.com:443 --recv-keys 379CE192D401AB61
Executing: /tmp/apt-key-gpghome.O5DmVP2A2n/gpg.1.sh --keyserver hkps://keyserver.ubuntu.com:443 --recv-keys 379CE192D401AB61
gpg: key 379CE192D401AB61: public key "Bintray (by JFrog) <bintray@bintray.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
alvinseville7cf@alvinseville7cf-VPCEB4Z1R ~> sudo apt update
Hit:1 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:2 http://ru.archive.ubuntu.com/ubuntu focal InRelease
Hit:3 http://ru.archive.ubuntu.com/ubuntu focal-updates InRelease
Get:4 http://ru.archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]
Err:5 https://dl.bintray.com/etcher/debian stable InRelease                    
  403  Forbidden [IP: 3.126.75.62 443]
Reading package lists... Done                 
E: Failed to fetch https://deb.etcher.io/dists/stable/InRelease  403  Forbidden [IP: 3.126.75.62 443]
E: The repository 'https://deb.etcher.io stable InRelease' 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.
alvinseville7cf@alvinseville7cf-VPCEB4Z1R ~ [100]>

How to fix this error?

3

Your issue is the repository. If you search it on the Balena forums, you will find this answer: (use the following link in your browser)

https://forums.balena.io/t/balenaetcher-repository-not-found/308436

Read the entire thread and I think you will find that this is the solution.

1 Like
4

Thanks William, that is correct!

@Alvin - set the apt repo to the new one in that post, and you should be good!