Also me I have the same problem, I tried on Debian and on Fedora but it seems related to the signature of repository because yesterday it worked without problems.
Maybe the signature is expired with the start of new year?

Also have this problem. Might be similar to #3511?

Also similar to #3665

Same thing with opensuse repo

Same thing with Debian 11 - amd64

Duplicate of #3665

Same thing with Ubuntu 20.04 Focal (amd64)

[mcraa] This issue has attached support thread https://jel.ly.fish/87e3b9da-a9d0-4f8b-a325-aec8a397d5da

Thanks for developing Balena Etcher and providing it to the general public free of charge, and for also hosting an apt repository.

This said, please consider your options to stabilize this (apt repository) service - it would be much appreciated to see a repository which works for more than ~ six months. Thank you.

same issue in Linux Mint 20.02 package Repository doesn't work

Thanks for developing Balena Etcher and providing it to the general public free of charge, and for also hosting an apt repository.

This said, please consider your options to stabilize this (apt repository) service - it would be much appreciated to see a repository which works for more than ~ six months. Thank you.

This is my 1st time having this issue, but considering I've never used Etcher on this particular machine, so I'm strongly considering just removing it and the repo.

The same here too.... Ubuntu 21.10 (AMD64)

E: Failed to fetch https://dl.cloudsmith.io/public/balena/etcher/deb/ubuntu/dists/impish/InRelease  402  Payment Required [IP: 54.230.114.10 443]
E: The repository 'https://dl.cloudsmith.io/public/balena/etcher/deb/ubuntu impish 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.

Happy to say the repo didn't throw any errors for me today. 👍

Happy to say the repo didn't throw any errors for me today. 👍

I'll see what the cron email output for the job that relies on # apt update to complete without errors gives on my affected machine.

UPDATE

Resolved.

Thanks very much!

Thanks @ABCMoNa for the kind words, and everyone for reporting the issue.
As you may found out from similar issues, cloudsmith has a monthly limit of downloads what etcher reached in the current period.
We contacted them and they added 20% to our limit for now, we will work with them together to make your experience smoother in the future.

That's great news @mcraa 👍
You can probably close #3511 and #3665 too?

Why not just use Launchpad, like nearly every other software project uses for its PPA...? Still getting this error.

20220109T122432Z: crystamped@mab:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.3 LTS
Release:	20.04
Codename:	focal
20220109T122439Z: crystamped@mab:~$ sudo apt update | egrep ^E

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Err:11 https://dl.cloudsmith.io/public/balena/etcher/deb/ubuntu focal InRelease
E: Failed to fetch https://dl.cloudsmith.io/public/balena/etcher/deb/ubuntu/dists/focal/InRelease  402  Payment Required [IP: 65.8.249.91 443]
E: The repository 'https://dl.cloudsmith.io/public/balena/etcher/deb/ubuntu focal InRelease' is no longer signed.
20220109T122528Z: crystamped@mab:~$ 

@mcraa Please provide a status update on this. Thanks.

so, whats the solution?sudo apt update
[sudo] password for me:
Get:1 https://download.docker.com/linux/debian bullseye InRelease [43.3 kB]
Hit:2 http://deb.debian.org/debian bullseye InRelease
Get:3 http://security.debian.org/debian-security bullseye-security InRelease [44.1 kB]
Get:4 http://deb.debian.org/debian bullseye-updates InRelease [39.4 kB]
Err:5 https://dl.cloudsmith.io/public/balena/etcher/deb/debian bullseye InRelease
402 Payment Required [IP: 13.226.97.127 443]
Reading package lists... Done
E: Failed to fetch https://dl.cloudsmith.io/public/balena/etcher/deb/debian/dists/bullseye/InRelease 402 Payment Required [IP: 13.226.97.127 443]
E: The repository 'https://dl.cloudsmith.io/public/balena/etcher/deb/debian bullseye InRelease' 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.

Continue getting HTTP 402 Payment Required. With regards to #3501, is Cloudsmith a good option?
Alternatives that might be a better option: Bytesafe - free for public open source projects, Open Build Service, Launchpad PPA and Fedora Copr, Pulp - OSS and self hosted.

Those 20% – #3672 (comment) – didn't last long, or so it would seem ;-) Looks like the interest in Balena Etcher's .deb packages keeps increasing :-)

(In addition to the suggestions for alternatives to Cloudsmith perhaps just the remark that a .deb repository can also – without exactly requiring rocket science – be hosted as a static website on any webspace, as I think it is the case for .rpm repositories, too; but of course something like that might already have been considered...)

@GlenCooper , @rschr figured it right.

Thanks for all the recommendations, we considered and still considering multiple solutions.

The downloads in this period now more than 2.5x of the last months.
The total downloads size of the last 3 days is close to the average of the past months.
However we are happy that etcher is getting more popular, but this sudden growth - even taking into account the new release -, is kind of suspicious.

Maybe lots of people got a new SBC for Christmas? 🤣

The total downloads size of the last 3 days is close to the average of the past months.

I haven't checked my RSS feeds in a while, but it could be that some very popular blog or Reddit post recommended or linked to Etcher.

Maybe lots of people got a new SBC for Christmas? 🤣

Perhaps, but I think fundaementally speaking a sudden increase in downloads should never be an issue for a repo.

The total downloads size of the last 3 days is close to the average of the past months.

Exactly 3 days ago, there was a new Linux Mint point release (20.3 "Una"). And the interest in that new version was so massive that the project's servers went to their knees with data rates dropping to two-digit kbit-per-second figures or even connection refusals. Something I've never seen before with a new Mint release.

Coincidence?

Usually people would have simply upgraded which is an exceptionally smooth procedure for a point release, but maybe a lot of downloaders did fresh installs and still a large part of them immediately installed etcher, too?

Still an issue for me.

just a kind suggestion... why don't you do a similar thing to https://pmateusz.github.io/linux/2017/06/30/linux-secure-apt-repository.html or just use launchpad and its alternatives

The download limit got doubled for now, hopefully it is enough at least for another 3 days.

@mcraa the same problem is back again.

thanks for the ping, but I don't have the power any more to act on this
cc @aethernet

Hey @thundron and @aethernet , its happening again, same issue on Ubuntu 22.04 LTS:

E: Falhou ao buscar https://dl.cloudsmith.io/public/balena/etcher/deb/ubuntu/dists/jammy/InRelease  402  Payment Required [IP: 108.139.134.25 443]
E: O repositório 'https://dl.cloudsmith.io/public/balena/etcher/deb/ubuntu jammy InRelease' já não está assinado.
N: Atualizações a partir de tal repositório não podem ser feitas de forma segura e estão, portanto, desativadas por definição.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

Same on Debian x86_64:
...
Err:X https://dl.cloudsmith.io/public/balena/etcher/deb/debian bullseye InRelease 402 Payment Required [IP: 52.85.92.37 443]
...
E: Failed to fetch https://dl.cloudsmith.io/public/balena/etcher/deb/debian/dists/bullseye/InRelease 402 Payment Required [IP: 52.85.92.37 443] E: The repository 'https://dl.cloudsmith.io/public/balena/etcher/deb/debian bullseye InRelease' 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.
...

@XMA2l Fix.

See the sticky issue: #4059

If you're here looking to delete this bloatware

ls /etc/apt/sources.list.d

Lists all the PPAs. Look for these:
balena-etcher.list
balena-etcher.list.save

sudo rm -i /etc/apt/sources.list.d/balena-etcher.list.save
sudo rm -i /etc/apt/sources.list.d/balena-etcher.list

The above should work with this update blocking from balena
But you can also run this to clean balena out
sudo apt purge balena-etcher

Can finally update my machine after a month :')