i3: debian.sur5r.net is down again - can't update my system
I’m submitting a…
[x] Other (Please describe in detail)
Current Behavior
It already happened in #2713.
Err:93 http://debian.sur5r.net/i3 bionic/universe amd64 i3lock amd64 2.11-1~~bionic1
Could not connect to debian.sur5r.net:80 (46.237.250.143). - connect (111: Connection refused) Could not connect to debian.sur5r.net:80 (2001:470:9e42:0:221:5eff:fe56:cdba), connection timed out
...
Err:1 http://debian.sur5r.net/i3 bionic/universe amd64 i3lock amd64 2.11-1~~bionic1
Could not connect to debian.sur5r.net:80 (46.237.250.143). - connect (111: Connection refused) Could not connect to debian.sur5r.net:80 (2001:470:9e42:0:221:5eff:fe56:cdba), connection timed out
E: Failed to fetch http://debian.sur5r.net/i3/pool/universe/i/i3lock/i3lock_2.11-1~~bionic1_amd64.deb Could not connect to debian.sur5r.net:80 (46.237.250.143). - connect (111: Connection refused) Could not connect to debian.sur5r.net:80 (2001:470:9e42:0:221:5eff:fe56:cdba), connection timed out
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Reproduction Instructions
apt update
apt upgrade
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 21 (10 by maintainers)
Fixed. Also, I’m increasing the redundancy again. Had to shut down one old machine several months ago with no immediate replacement available.
Debian repositories have no dynamic parts, so serving them is possible with static hosters.