apt-get update leads to:
Das Depot »https://deb.etcher.io stable Release« enthält keine Release-Datei mehr.
N: Eine Aktualisierung von solch einem Depot kann nicht auf eine sichere Art durchgeführt werden, daher ist es standardmäßig deaktiviert.
deepL translates this that way:
“The depot “https://deb.etcher.io stable Release” no longer contains a release file.
N: An update from such a repository cannot be done in a secure way, so it is disabled by default.”
Any ideas?
greetings
Hi,
I am not quite sure about what the status of the debian repository is.
The ‘normal’ way to install etcher is to just download it from https://www.balena.io/etcher/ and it will ask you to update whenever a new update is out. So your best option is probably to remove your installation of etcher via apt-get remove and install the newest release from the website.
Hi,
the release files are still available but not readable. The web team should be able to fix the problem by adjusting the permissions.
Greetings
Hi @tazzy98 and @roluan42, thank you for reporting this issue. We are looking into it and tracking it here as well: https://github.com/balena-io/etcher/issues/3244
We will post an update on that github link as well as here when we resolve the problem.
Facepalm and SMH.
I’m trying not to be surprised. This comes up regularly
See First post, longtime user - install on *ubuntu
and I’m sure others. it always gets fixed fairly quickly. It has been a couple of days now…so, soon.
Hello, the issue https://github.com/balena-io/etcher/issues/3244 has been resolved.
It’s baaaa-aaack.
Hi @heysoundude, so are you experiencing the exact same issue?
It’d be great to have some verbose description 
I guess you are referring to the same issue as reported by other users already as well (but I don’t want to assume): Debian/Ubuntu repository respond with error : invalid key · Issue #3482 · balena-io/etcher · GitHub
Yes, I was getting that same issue again, but it seems to have resolved itself.
Something about certificates as they pertain to release updates on balena’s end is out of sync at times. And it keeps happening, so whether it’s balena’s process or just how it happens to happen (I’ve never had it happen as much as with etcher), I’m leaning towards something on balena’s end/process.
and it happened again, same issue.
is it something to do with keeping up with ubuntu releases? 21.04 dropped just the other day iirc…
Y’all will sort it out I’m sure…in time
Thanks for keeping us current with when you’re seeing these issues! While in the past, we have spot-fixed it, as in the issue linked earlier in this thread, we are making changes to the way that we publish this repository to prevent it from happening in the future. We’ll keep you posted!
We have just deployed a new PPA provider, hopefully that resolves this issue permanently! Let us know if you continue to see this error though, thanks.
yessir, still happening as of 5 min ago.
how can I help sort this with you? will the IP addy it shows be of any assistance?
Hello,
Thanks for reaching out, we have switched to Cloudsmith as a PPA provider now. This change will require folks to use the new endpoints for getting the package. Please checkout the instructions mentioned here New deb|rpm PPA · Issue #3501 · balena-io/etcher · GitHub and let us know if things still don’t work out for you. Do post more context, logs or any errors you are getting when trying to install etcher. Happy to help!