Good to hear it isn't something on our end. Thanks for the update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888058
Title:
Got “Authentication failed” while running do-release-upgrade from
After refreshing Squid cache by the commands above the upgrade works normally
on both archive.ubuntu.com and ru.archive.ubuntu.com .
So it was my personal problems with my squid-deb-proxy server.
I'm sorry for the buzz.
** No longer affects: apache2 (Ubuntu)
--
You received this bug
There is something wrong with archive.ubuntu.com. But
ru.archive.ubuntu.com works normally.
You can compare command outputs below:
```
http_proxy=http://192.168.3.222:8000 wget --server-response --no-cache -c
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888058
Title:
Got “Authentication failed” while running
I'm not sure why this is a problem now as the old archive servers were
doing the same thing. In any case, I've added the following to apache2
configs:
| AddType application/pgp-signature .gpg
Testing without:
> GET
> /ubuntu/dists/focal-updates/main/dist-upgrader-all/current/focal.tar.gz.gpg
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1888058
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For 18.04 LTS -> 20.04 LTS:
```
$ sudo apt update
Hit:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports