You had noted:
You can change the apt sources.list to use 'https' instead of
'http' to potentially avoid some problems with external interference
(although, some interference is considered good interference, so this
isn't a default in Debian for now). A VPN would indeed eliminate far
more of potential external interference, but for now that seems like
overkill.
==========
I got a Debian installation together ( archived ssd ) and edited
the "/etc/apt/services.list" file. I then did "sudo apt update" which
listed 187 items. I followed this with "sudo apt upgrade" which
miraculously downloaded and installed all 187 items. After rebooting
this machine with "shutdown -r now" {amazing after the amount of time I
had put in these last 2-3 months} it worked properly. I then did a
"sudo apt install a2ps", a " sudo apt install gv" and a "sudo apt
install aptitude". I followed this with "sudo aptitude" and selected
"openssh server" with the shift/+ followed by g and g. After this
completed installation and I had exited from aptitude and rebooted I
tested this by doing "ssh orville@andy". After logging in to andy I did
"ssh orville@elmer" and was able to log in to elmer.
While this is not an extensive test it seems that all on Debian
was now working.
==========
Unless I understand why this happened I will continue to consider
a VPN.
==========
The current “/etc/apt/sources.list” file on elmer --- the current Debian
makchine.
orville@elmer:/etc/apt$ cat sources.list
# See https://wiki.debian.org/SourcesList for more information.
deb https://deb.debian.org/debian bullseye main
deb-src https://deb.debian.org/debian bullseye main
deb https://deb.debian.org/debian bullseye-updates main
deb-src https://deb.debian.org/debian bullseye-updates main
deb https://security.debian.org/debian-security/ bullseye-security main
deb-src https://security.debian.org/debian-security/ bullseye-security main
==========
Xubuntu with unmodified “/etc/apt/sources.list and unmodified
“/etc/apt/sources.list.distUpgrade”
root@andy:/etc/apt# apt update
Err:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:2 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Connection failed [IP: 91.189.91.39 80]
Err:3 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Connection failed [IP: 91.189.91.38 80]
Err:4 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Connection failed [IP: 91.189.91.39 80]
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: Failed to fetch
http://us.archive.ubuntu.com/ubuntu/dists/jammy/InRelease Connection
failed [IP: 91.189.91.39 80]
W: Failed to fetch
http://us.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease
Connection failed [IP: 91.189.91.38 80]
W: Failed to fetch
http://us.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease
Connection failed [IP: 91.189.91.39 80]
W: Failed to fetch
http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease
Temporary failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old
ones used instead.
Xubuntu with all “http://” replaced with “https://”
root@andy:/etc/apt# apt update
Err:1 https://security.ubuntu.com/ubuntu jammy-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:2 https://us.archive.ubuntu.com/ubuntu jammy InRelease
Temporary failure resolving 'us.archive.ubuntu.com'
Err:3 https://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Could not connect to us.archive.ubuntu.com:443 (91.189.91.39). -
connect (111: Connection refused) Cannot initiate the connection to
us.archive.ubuntu.com:443 (2001:67c:1562::15). - connect (101: Network
is unreachable) Could not connect to us.archive.ubuntu.com:443
(91.189.91.38). - connect (111: Connection refused) Cannot initiate the
connection to us.archive.ubuntu.com:443 (2001:67c:1562::18). - connect
(101: Network is unreachable)
Err:4 https://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Cannot initiate the connection to us.archive.ubuntu.com:443
(2001:67c:1562::15). - connect (101: Network is unreachable) Cannot
initiate the connection to us.archive.ubuntu.com:443
(2001:67c:1562::18). - connect (101: Network is unreachable)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: Failed to fetch
https://us.archive.ubuntu.com/ubuntu/dists/jammy/InRelease Temporary
failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch
https://us.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease Could
not connect to us.archive.ubuntu.com:443 (91.189.91.39). - connect (111:
Connection refused) Cannot initiate the connection to
us.archive.ubuntu.com:443 (2001:67c:1562::15). - connect (101: Network
is unreachable) Could not connect to us.archive.ubuntu.com:443
(91.189.91.38). - connect (111: Connection refused) Cannot initiate the
connection to us.archive.ubuntu.com:443 (2001:67c:1562::18). - connect
(101: Network is unreachable)
W: Failed to fetch
https://us.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease
Cannot initiate the connection to us.archive.ubuntu.com:443
(2001:67c:1562::15). - connect (101: Network is unreachable) Cannot
initiate the connection to us.archive.ubuntu.com:443
(2001:67c:1562::18). - connect (101: Network is unreachable)
W: Failed to fetch
https://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease
Temporary failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old
ones used instead
==========
The same procedure was tried on a plain Ubuntu machine. It
produced very similar results.
The "Some index files failed to download. They have been ignored,
or old ones used instead" is not a real attention grabber as an error
message and Is pretty much all that might be easily visible with more
common update methods.
==========
Tim,
This resolution is MYSTERIOUS to me. If you have ideas as to why
it might have worked I would appreciate your input. While a similar
approach fails with Ubuntu and Xubuntu is not so mystifying ... It
would appear that their distribution is just not able to deal with
"https://"; unlike Debian.
I will now try a clean install of Debian ... I expect some
problems and should have added infornation for you by early next week.
Much thanks,
WILLIAM O RICHMOND
wor...@windstream.net
