Has anybody experienced the error message as follows:
Error on updating whonix-gw-16:
ID: update
Function: pkg.uptodate
Result: False
Comment: Failed to fetch tor-https://deb.debian.org/debian/dists/bullseye/InRelease Invalid response from proxy: HTTP/1.0 500 Unable to connect Server: tinyproxy/1.10.0 Content-Type: text/html Connection: close
[IP: 127.0.0.1 8082]
Yes, I see a similar error as well. My version is a fresh install of 4.2 rc4 with whonix 17 and the first update already fails.
Fail to fetch InRelease: tor+https://deb.kicksecure.com bookworm InRelease from tor+https://deb.kicksecure.com/dists/bookworm/InRelease
Updating whonix-workstation-17
Fail to fetch InRelease: tor+https://deb.kicksecure.com bookworm InRelease from tor+https://deb.kicksecure.com/dists/bookworm/InRelease
Fail to fetch InRelease: Index of /r4.2/vm/ bookworm InRelease from https://deb.qubes-os.org/r4.2/vm/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian bookworm InRelease from tor+https://deb.debian.org/debian/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian bookworm-updates InRelease from tor+https://deb.debian.org/debian/dists/bookworm-updates/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian-security bookworm-security InRelease from tor+https://deb.debian.org/debian-security/dists/bookworm-security/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian bookworm-backports InRelease from tor+https://deb.debian.org/debian/dists/bookworm-backports/InRelease
Fail to fetch InRelease: tor+https://fasttrack.debian.net/debian bookworm-fasttrack InRelease from tor+https://fasttrack.debian.net/debian/dists/bookworm-fasttrack/InRelease
Fail to fetch InRelease: tor+https://deb.whonix.org bookworm InRelease from tor+https://deb.whonix.org/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.kicksecure.com bookworm InRelease from tor+https://deb.kicksecure.com/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian bookworm InRelease from tor+https://deb.debian.org/debian/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian bookworm-updates InRelease from tor+https://deb.debian.org/debian/dists/bookworm-updates/InRelease
Fail to fetch InRelease: Index of /r4.2/vm/ bookworm InRelease from https://deb.qubes-os.org/r4.2/vm/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian-security bookworm-security InRelease from tor+https://deb.debian.org/debian-security/dists/bookworm-security/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian bookworm-backports InRelease from tor+https://deb.debian.org/debian/dists/bookworm-backports/InRelease
Fail to fetch InRelease: tor+https://fasttrack.debian.net/debian bookworm-fasttrack InRelease from tor+https://fasttrack.debian.net/debian/dists/bookworm-fasttrack/InRelease
Fail to fetch InRelease: tor+https://deb.whonix.org bookworm InRelease from tor+https://deb.whonix.org/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.kicksecure.com bookworm InRelease from tor+https://deb.kicksecure.com/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian bookworm InRelease from tor+https://deb.debian.org/debian/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian bookworm-updates InRelease from tor+https://deb.debian.org/debian/dists/bookworm-updates/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian-security bookworm-security InRelease from tor+https://deb.debian.org/debian-security/dists/bookworm-security/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian bookworm-backports InRelease from tor+https://deb.debian.org/debian/dists/bookworm-backports/InRelease
Fail to fetch InRelease: Index of /r4.2/vm/ bookworm InRelease from https://deb.qubes-os.org/r4.2/vm/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://fasttrack.debian.net/debian bookworm-fasttrack InRelease from tor+https://fasttrack.debian.net/debian/dists/bookworm-fasttrack/InRelease
Fail to fetch InRelease: tor+https://deb.whonix.org bookworm InRelease from tor+https://deb.whonix.org/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.kicksecure.com bookworm InRelease from tor+https://deb.kicksecure.com/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian bookworm InRelease from tor+https://deb.debian.org/debian/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian bookworm-updates InRelease from tor+https://deb.debian.org/debian/dists/bookworm-updates/InRelease
Fail to fetch InRelease: tor+https://fasttrack.debian.net/debian bookworm-fasttrack InRelease from tor+https://fasttrack.debian.net/debian/dists/bookworm-fasttrack/InRelease
Fail to fetch InRelease: Index of /r4.2/vm/ bookworm InRelease from https://deb.qubes-os.org/r4.2/vm/dists/bookworm/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian-security bookworm-security InRelease from tor+https://deb.debian.org/debian-security/dists/bookworm-security/InRelease
Fail to fetch InRelease: tor+https://deb.debian.org/debian bookworm-backports InRelease from tor+https://deb.debian.org/debian/dists/bookworm-backports/InRelease
Fail to fetch InRelease: tor+https://deb.whonix.org bookworm InRelease from tor+https://deb.whonix.org/dists/bookworm/InRelease
E:Failed to fetch tor+https://deb.debian.org/debian/dists/bookworm/InRelease Could not connect to 127.0.0.1:8082 (127.0.0.1). - connect (113: No route to host), E:Failed to fetch tor+https://deb.debian.org/debian/dists/bookworm-updates/InRelease Unable to connect to 127.0.0.1:8082:, E:Failed to fetch tor+https://deb.debian.org/debian-security/dists/bookworm-security/InRelease Unable to connect to 127.0.0.1:8082:, E:Failed to fetch tor+https://deb.debian.org/debian/dists/bookworm-backports/InRelease Unable to connect to 127.0.0.1:8082:, E:Failed to fetch tor+https://fasttrack.debian.net/debian/dists/bookworm-fasttrack/InRelease Could not connect to 127.0.0.1:8082 (127.0.0.1). - connect (113: No route to host), E:Failed to fetch tor+https://deb.kicksecure.com/dists/bookworm/InRelease Could not connect to 127.0.0.1:8082 (127.0.0.1). - connect (113: No route to host), E:Failed to fetch tor+https://deb.whonix.org/dists/bookworm/InRelease Could not connect to 127.0.0.1:8082 (127.0.0.1). - connect (113: No route to host), E:Failed to fetch https://deb.qubes-os.org/r4.2/vm/dists/bookworm/InRelease Could not connect to 127.0.0.1:8082 (127.0.0.1). - connect (113: No route to host), E:Some index files failed to download. They have been ignored, or old ones used instead.
Do you have internet working in non-whonix qubes? If yes then is sys-whonix connected to tor network successfully? You can check it in sys-whonix Tor control panel.
I tried to check the connectivity but obviously my knowledge is not enough:-(
tor-control-panel in sys-whonix won`t start with “qt.qpa.xcb: could not connect to display”
Maybe that has todo with the disposable terminal…
In anon-whonix I can open web-pages in firefox.
In the meantime I removed the templates (gw+ws) and reinstalled it. With the Qubes-Updater I run into the same problem.
However this time I also tried “sudo dnf update” and “sudo dnf upgrade” inside the template and that works. Now I think that is a problem in the qubes-updater.
Start it using GUI through Qubes menu or at least using normal terminal in sys-whonix and not disposable.
What’s your Whonix update proxy in Qubes Global Config?
Ahh, I completely missed the service-tab in the “New” start menu. 
Now there is an entry for sys-whonix and also tor-control-panel of course. → Tor is connected to the tor network.
The Whonix update proxy is set to sys-whonix.
Did you use dnf or apt? Are you talking about whonix-workstation-17?
apt
After you reinstalled the templates does apt update command work in template? Does Qubes-Updater work or not?
apt update works, qubes updater doesn’t work for tor templates.
Does updating your non-whonix templates using Qubes-Updater work?
What if you select default update proxy in Qubes Global Config to use sys-whonix?
Will your debian/fedora templates be able to update successfully?
The update of the other templates (all fedora based) and dom0 works well with qubes updater.
Then I set the default update proxy to sys-whonix.
The update of the fedora templates still works well (no updates found though).
And now also the whonix-gateway-17 update runs with qubes updater.
I don`t know what happened now.
Thank you very much for your help and time for me to get some sleep…
In my experience, it is very common for Linux updates to fail temporarily and succeed on another attempt (sometimes a short time later, sometimes only a long time later). Updating over Tor might make such failures more frequent, but they also happen without Tor, and they also happen with Fedora and Debian (not just Whonix). The easiest thing to do when an update fails is simply to try it again, or wait a while and try it again. More often than not, one of the subsequent attempts will succeed, even though you didn’t change anything on your end. I guess they’re just temporary network or server problems.
Thank you again for your help and the time you put in.
I think these errors are (or at least can be) more than a temporary network or server problem. When you say “sometimes only a long time later”, how long are we talking about? My Whonix gateway and workstation would not update for over a week. I would receive a list of the no path to host errors each time I attempted to update them. I tried multiple times a day during this time to update them, and never got it to work.
Finally I deleted all Whonix qubes, and reinstalled them per the instructions from Whonix. After doing this they now update as they should.
Oh, yes, they certainly can be. I just mean that it’s quite common, in my experience.
In my experience, subsequent attempts anywhere between immediately and one day are usually successful for a temporary problem external to my own machine. If a problem recurred two days in a row or more, I’d report and/or try to fix it. Over a week is too long.