On Thu, Apr 25, 2019 at 01:06:26PM +0300, Claudio Chinicz wrote: > Hi All, > > I'm getting the following error message: > > root@debian-9:/home/user# apt-get update > Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease > Ign:2 https://deb.qubes-os.org/r4.0/vm stretch InRelease > Ign:3 https://deb.debian.org/debian stretch InRelease > Err:4 http://dl.google.com/linux/chrome/deb stable Release > 500 Unable to connect > Err:5 https://deb.qubes-os.org/r4.0/vm stretch Release > Received HTTP code 500 from proxy after CONNECT > Ign:6 https://deb.debian.org/debian-security stretch/updates InRelease > Err:7 https://deb.debian.org/debian stretch Release > Received HTTP code 500 from proxy after CONNECT > Err:8 https://deb.debian.org/debian-security stretch/updates Release > Received HTTP code 500 from proxy after CONNECT > Reading package lists... Done > E: The repository 'http://dl.google.com/linux/chrome/deb stable Release' > does no longer have a Release file. > 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. > E: The repository 'https://deb.qubes-os.org/r4.0/vm stretch Release' does no > longer have a Release file. > 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. > E: The repository 'https://deb.debian.org/debian stretch Release' does no > longer have a Release file. > 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. > E: The repository 'https://deb.debian.org/debian-security stretch/updates > Release' does no longer have a Release file. > 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. > > Have anyone faced the same issue? Any ideas how to solve it? > > Thanks, > > Claudio >
Hi Claudio The important is the error messages - everything else is consequential. 500 is an internal server error. Combined with connect error suggest there's something wrong with your proxy or your connection. If you are using sys-whonix could be intermittent fault on Tor network. Try again later. If not, look closely at proxy configuration, and check qube where proxy is running. (Look in /etc/qubes-rpc/policy/qubes.UpdatesProxy if you're not sure.) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20190425121806.eottc52zine4a27a%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
