apt-get update timing out

[Noah]

Hi there,

Thank you for all the knowledge shared and super helpful responses.

Okay I have an RG SR515 router at the edge.  Guess what?  Here is what I 
figured out.

2 of 5 Ubuntu bare metal servers could not reach port 80 of the ubuntu 
archive hosts and after more looking into it the hosts could not reach 
port 80 to any offnet server.  Used the nc (netcat), curl, and nmap to 
verify this.  But they could reach port 80 of hosts on the local subnet.

I could no longer reach the admin panel of my RG router.

Here is what I did:

1) factory reset the RG
2) re-installed my saved config from a month ago.
3) port 80 on upstream hosts are reachable again.

So my edge router lost it's mind.
Kray kray.

Thanks again



On 11/20/21 5:51 AM, Peter Silva wrote:
> This is probably not your problem, but fwiw:
> 
> On a corporate network with some firewalls and such, We ran into this 
> recently in docker containers... The main linux host can access the 
> repositories just fine, and the docker networking looks completely 
> normal, even the DNS resolves fine, but it fails to connect to 
> archive.canonical.com <http://archive.canonical.com>.  no repositories, 
> means we can't install anything, so we can't diagnose what is going on, 
> because the image is just base ubuntu (that one is supposed to add 
> packages to.)
> Here is a sample Dockerfile:
> 
> FROM ubuntu:focal
> RUN apt-get update && apt-get upgrade && sleep infinity
> 
> That's it, it gives the same could not connect to archive.ubuntu.com:80 
> <http://archive.ubuntu.com:80> (but gets to security.canonical.com 
> <http://security.canonical.com> just fine...)
> This is on an ubuntu bionic real host.  We're in Canada, and a 
> work-around was discovered:
> 
> FROM ubuntu:bionic
> RUN sed -i 's/archive/ca.archive/g' /etc/apt/sources.list && apt-get 
> update && apt-get upgrade
> 
> explicitly putting the canadian archive in there fixes the problem.  The 
> cause seems to be some security
> device on the corporate gateway, because when I do it outside our 
> corporate network, it works fine.
> Then I noticed that the enclosing host goes to us.archive.canonical.com 
> <http://us.archive.canonical.com> and not archive.com 
> <http://archive.com> ... so it seems
> messed up on our corporate network. but... Can anyone explain the reason 
> why this would fail?
> I don't understand the mechanism.
> 
> Thanks.
> 
> 
> 
> On Sat, Nov 20, 2021 at 8:30 AM Colin Law <clanlaw at gmail.com 
> <mailto:clanlaw at gmail.com>> wrote:
> 
>     On Sat, 20 Nov 2021 at 13:06, Noah <noah-list at enabled.com
>     <mailto:noah-list at enabled.com>> wrote:
>      >
>      >
>      > Hi,
>      >
>      > It'd be wonderful to get a better understanding of a good
>     solution please.
>      >
>      > Apt-get update timing out.  Are the archive hosts blocking port 80?
>      >
>      > sudo apt-get update
>      > Err:1 http://archive.ubuntu.com/ubuntu
>     <http://archive.ubuntu.com/ubuntu> focal InRelease
>      >    Could not connect to archive.ubuntu.com:80
>     <http://archive.ubuntu.com:80> (91.189.88.152),
> 
>     Is this a permanent or intermittent problem?
> 
>     What do you see in a browser if you browse to
>     http://archive.ubuntu.com/ubuntu <http://archive.ubuntu.com/ubuntu>
>     on the failing machine.  Have you got
>     multiple machines at your site?  If so are you seeing that on all of
>     them?
> 
>     What do you see if you ping archive.ubuntu.com
>     <http://archive.ubuntu.com>?
> 
>     Where in the world are you?  There may be a better mirror you could use.
> 
>     Colin
> 
>     -- 
>     ubuntu-users mailing list
>     ubuntu-users at lists.ubuntu.com <mailto:ubuntu-users at lists.ubuntu.com>
>     Modify settings or unsubscribe at:
>     https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>     <https://lists.ubuntu.com/mailman/listinfo/ubuntu-users>
> 
>