Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #234902 > unrolled thread

URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net

Back to article view | Back to linux.debian.user

Contents

  URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net ISRAEL <bisniscc1@gmail.com> - 2021-05-06 09:10 +0200
    Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net Dan Ritter <dsr@randomstring.org> - 2021-05-06 11:50 +0200
      Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net The Wanderer <wanderer@fastmail.fm> - 2021-05-06 13:10 +0200
        Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net <tomas@tuxteam.de> - 2021-05-06 13:20 +0200
          Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net Andrei POPESCU <andreimpopescu@gmail.com> - 2021-05-06 14:30 +0200
            Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net The Wanderer <wanderer@fastmail.fm> - 2021-05-06 14:40 +0200
              Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net The Wanderer <wanderer@fastmail.fm> - 2021-05-06 14:50 +0200
                Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net David Wright <deblis@lionunicorn.co.uk> - 2021-05-06 16:40 +0200
                  Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net Greg Wooledge <greg@wooledge.org> - 2021-05-06 16:50 +0200
                  Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net Darac Marjal <mailinglist@darac.org.uk> - 2021-05-06 17:10 +0200
                Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net Andrei POPESCU <andreimpopescu@gmail.com> - 2021-05-06 17:50 +0200
              Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net Greg Wooledge <greg@wooledge.org> - 2021-05-06 14:50 +0200
            Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net Dan Ritter <dsr@randomstring.org> - 2021-05-06 15:10 +0200
          Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net Celejar <celejar@gmail.com> - 2021-05-06 17:40 +0200
            Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net <tomas@tuxteam.de> - 2021-05-06 18:00 +0200
        Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net Dan Ritter <dsr@randomstring.org> - 2021-05-06 13:20 +0200
        Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net Charles Curley <charlescurley@charlescurley.com> - 2021-05-06 14:30 +0200
    Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net Calum McConnell <calumlikesapplepie@gmail.com> - 2021-05-20 23:30 +0200

#234902 — URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net

[Multipart message — attachments visible in raw view] — view raw

Very annoying when UPDATE = apt update always fail =

*Err:3 http://deb.debian.org/debian <http://deb.debian.org/debian>
buster/updates InRelease                    *
*  Could not connect to debian.map.fastlydns.net
<http://debian.map.fastlydns.net>:80*

[toc] | [next] | [standalone]

#234904

ISRAEL wrote: 
> Very annoying when UPDATE = apt update always fail =
> 
> *Err:3 http://deb.debian.org/debian <http://deb.debian.org/debian>
> buster/updates InRelease                    *
> *  Could not connect to debian.map.fastlydns.net
> <http://debian.map.fastlydns.net>:80*


Feel free to choose something more convenient for you from the 
list:

https://www.debian.org/mirror/list

-dsr-

[toc] | [prev] | [next] | [standalone]

#234905

[Multipart message — attachments visible in raw view] — view raw

On 2021-05-06 at 05:41, Dan Ritter wrote:

> ISRAEL wrote: 
>
>> Very annoying when UPDATE = apt update always fail =
>> 
>> *Err:3 http://deb.debian.org/debian <http://deb.debian.org/debian>
>> buster/updates InRelease                    *
>> *  Could not connect to debian.map.fastlydns.net
>> <http://debian.map.fastlydns.net>:80*
> 
> 
> Feel free to choose something more convenient for you from the 
> list:
> 
> https://www.debian.org/mirror/list

I think the complaint, insofar as there is one that specific, is that
the mirror auto-selector is choosing a mirror that does not function
correctly (or at least does not do so for some people, without any
obvious reason why it would work for others and not for them). ISTR that
this is the second complaint about this mirror not working correctly
we've seen in the past week or three; whether they are from different
people, or both from the same, I don't know.

(Note that the person making the complaint did not choose to use
debian.map.fastlydns.net; that person chose to use the mirror
auto-selector, deb.debian.org, which in this instance chose the
fastlydns option.)

The only options I see offhand (though I'm sure I'm missing some) are A:
that the debian.map.fastlydns.net mirror is in fact not functioning
correctly for anyone at present, or B: that for some reason the
complainer's Internet access is being blocked/filtered in a way which
prevents access to that mirror without preventing access to e.g. this
mailing list.

In case A, either the people who run that mirror need to fix whatever's
wrong with it, or it needs to be removed from the auto-selector's list.

In case B, either the blocking is a mistake (in which case someone -
possibly the mirror maintainers, possibly the complainer - needs to
reach out to whoever's doing the blocking and get them to correct that
mistake), or it's intentional (in which case the complainer is off-base,
and needs to either switch to a different Internet access - which might
be impossible, depending on the circumstances - or stop using the
auto-selector and choose a mirror that isn't being blocked).

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#234906

[Multipart message — attachments visible in raw view] — view raw

On Thu, May 06, 2021 at 07:00:02AM -0400, The Wanderer wrote:

[...]

> The only options I see offhand (though I'm sure I'm missing some) are A:
> that the debian.map.fastlydns.net mirror is in fact not functioning
> correctly for anyone at present, or B: that for some reason the
> complainer's Internet access is being blocked/filtered in a way which
> prevents access to that mirror without preventing access to e.g. this
> mailing list.

FWIW, I get a connect, but the page's content is something like

 | Fastly error: unknown domain: debian.map.fastlydns.net. Please check that this domain has been added to a service.
 | 
 | Details: cache-hhn11565-HHN

The HTTP code is 500 (had to resort to curl to get that. Browsers
are getting more useless at each minor version, it seems :-(

So I'd go with (A). The fastlydns folks gotta something to fix.

Cheers
 - t

[toc] | [prev] | [next] | [standalone]

#234909

[Multipart message — attachments visible in raw view] — view raw

On Jo, 06 mai 21, 13:16:36, tomas@tuxteam.de wrote:
> On Thu, May 06, 2021 at 07:00:02AM -0400, The Wanderer wrote:
> 
> [...]
> 
> > The only options I see offhand (though I'm sure I'm missing some) are A:
> > that the debian.map.fastlydns.net mirror is in fact not functioning
> > correctly for anyone at present, or B: that for some reason the
> > complainer's Internet access is being blocked/filtered in a way which
> > prevents access to that mirror without preventing access to e.g. this
> > mailing list.
> 
> FWIW, I get a connect, but the page's content is something like
> 
>  | Fastly error: unknown domain: debian.map.fastlydns.net. Please check that this domain has been added to a service.
>  | 
>  | Details: cache-hhn11565-HHN
> 
> The HTTP code is 500 (had to resort to curl to get that. Browsers
> are getting more useless at each minor version, it seems :-(
> 
> So I'd go with (A). The fastlydns folks gotta something to fix.

Maybe this helps (though it might be outdated):

    https://deb.debian.org

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#234911

[Multipart message — attachments visible in raw view] — view raw

On 2021-05-06 at 08:28, Andrei POPESCU wrote:

> On Jo, 06 mai 21, 13:16:36, tomas@tuxteam.de wrote:
>
>> On Thu, May 06, 2021 at 07:00:02AM -0400, The Wanderer wrote:
>> 
>> [...]
>> 
>> > The only options I see offhand (though I'm sure I'm missing some) are A:
>> > that the debian.map.fastlydns.net mirror is in fact not functioning
>> > correctly for anyone at present, or B: that for some reason the
>> > complainer's Internet access is being blocked/filtered in a way which
>> > prevents access to that mirror without preventing access to e.g. this
>> > mailing list.
>> 
>> FWIW, I get a connect, but the page's content is something like
>> 
>>  | Fastly error: unknown domain: debian.map.fastlydns.net. Please check that this domain has been added to a service.
>>  | 
>>  | Details: cache-hhn11565-HHN
>> 
>> The HTTP code is 500 (had to resort to curl to get that. Browsers
>> are getting more useless at each minor version, it seems :-(
>> 
>> So I'd go with (A). The fastlydns folks gotta something to fix.
> 
> Maybe this helps (though it might be outdated):
> 
>     https://deb.debian.org

That's the mirror auto-selector which the original complainant here was
using, and which apparently chose debian.map.fastlydns.net as the mirror
to be used, which led to the error which was the subject of the complaint.

IOW, I think that site is part of the problem (in that it has a broken
mirror listed), but I don't see how it could help. Is there a part of
your suggestion I'm not understanding?

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#234912

[Multipart message — attachments visible in raw view] — view raw

On 2021-05-06 at 08:40, Greg Wooledge wrote:

> On Thu, May 06, 2021 at 08:33:47AM -0400, The Wanderer wrote:
>
>> On 2021-05-06 at 08:28, Andrei POPESCU wrote:
>>
>> > Maybe this helps (though it might be outdated):
>> > 
>> >     https://deb.debian.org
>> 
>> That's the mirror auto-selector which the original complainant here was
>> using, and which apparently chose debian.map.fastlydns.net as the mirror
>> to be used, which led to the error which was the subject of the complaint.
>> 
>> IOW, I think that site is part of the problem (in that it has a broken
>> mirror listed), but I don't see how it could help. Is there a part of
>> your suggestion I'm not understanding?
> 
> I believe the suggestion was that you actually *go* to that web page
> in your web browser and read what it says.  It's fairly short.

I did, and I didn't see how it was helpful, thus my question.

> To be fair, though, it'll basically reiterate advice that was
> already given in this thread ("try a different mirror").

Which might help in the immediate term, but doesn't get the actual
problem fixed, that problem being either with the mirror or with the
configuration of the redirector to include that mirror.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#234919

On Thu 06 May 2021 at 08:43:22 (-0400), The Wanderer wrote:
> On 2021-05-06 at 08:40, Greg Wooledge wrote:
> > On Thu, May 06, 2021 at 08:33:47AM -0400, The Wanderer wrote:
> >> On 2021-05-06 at 08:28, Andrei POPESCU wrote:

> >> > > On Thu, May 06, 2021 at 07:00:02AM -0400, The Wanderer wrote:
> >> > > > ISTR that
> >> > > > this is the second complaint about this mirror not working correctly
> >> > > > we've seen in the past week or three; whether they are from different
> >> > > > people, or both from the same, I don't know.

Six days ago, and 11 timezones apart.

> >> > Maybe this helps (though it might be outdated):
> >> > 
> >> >     https://deb.debian.org
> >> 
> >> That's the mirror auto-selector which the original complainant here was
> >> using, and which apparently chose debian.map.fastlydns.net as the mirror
> >> to be used, which led to the error which was the subject of the complaint.
> >> 
> >> IOW, I think that site is part of the problem (in that it has a broken
> >> mirror listed), but I don't see how it could help. Is there a part of
> >> your suggestion I'm not understanding?
> > 
> > I believe the suggestion was that you actually *go* to that web page
> > in your web browser and read what it says.  It's fairly short.
> 
> I did, and I didn't see how it was helpful, thus my question.

I went there too, once I realised that it was a reference to be
browsed, rather than something to do with one's sources.list.¹

> > To be fair, though, it'll basically reiterate advice that was
> > already given in this thread ("try a different mirror").

I thought the page rather full of gobbledegook, talking about SRV
records and CDN instances. As for trying a different mirror, the only
occurrence of "mirror" is "This service provides mirrors for the
following Debian archive repositories".

And the instance chosen, "cdn-fastly.deb.debian.org" is not actually
among these mysterious SRV records, "_http._tcp.deb.debian.org",
"prod.debian.map.fastly.net" and "dpvctowv9b08b.cloudfront.net" that
we're not even told how to obtain.

> Which might help in the immediate term, but doesn't get the actual
> problem fixed, that problem being either with the mirror or with the
> configuration of the redirector to include that mirror.

Yes, more useful might be a page something like one of these:
https://packages.debian.org/buster/amd64/base-files/download
that might get you back on your feet.

¹ Now after reading
  https://lists.debian.org/debian-user/2021/05/msg00238.html
  I'm not even sure about that. I was under the impression,
  from this list, that https was best avoided in favour of http.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#234921

On Thu, May 06, 2021 at 09:34:58AM -0500, David Wright wrote:
> ¹ Now after reading
>   https://lists.debian.org/debian-user/2021/05/msg00238.html
>   I'm not even sure about that. I was under the impression,
>   from this list, that https was best avoided in favour of http.

Under ideal circumstances, it is.  Plain HTTP can be proxied and cached,
and therefore is far more efficient when admins go out of their way to
make it so.  There's also slightly less overhead, so even in the most
vanilla setups, it's a *tiny* bit more efficient.

The problem is, a lot of hosts are stuck with broken Internet setups,
intentionally or otherwise.  In some of those situations, using HTTPS
instead of plain HTTP can work around the brokenness and get you the
packages.  It's not ideal, but it's reality.

My workplace is one of those intentionally broken setups.  So, don't
think it can't happen to you.

[toc] | [prev] | [next] | [standalone]

#234922

[Multipart message — attachments visible in raw view] — view raw

On 06/05/2021 15:34, David Wright wrote:
> [cut]
> I thought the page rather full of gobbledegook, talking about SRV
> records and CDN instances. As for trying a different mirror, the only
> occurrence of "mirror" is "This service provides mirrors for the
> following Debian archive repositories".
>
> And the instance chosen, "cdn-fastly.deb.debian.org" is not actually
> among these mysterious SRV records, "_http._tcp.deb.debian.org",
> "prod.debian.map.fastly.net" and "dpvctowv9b08b.cloudfront.net" that
> we're not even told how to obtain.

SRV records are a DNS record type. That is, when you want to know what
IPv4 address example.org maps to, you ask for an A record; when you want
to know what IPv6 address it maps to, you ask for an AAAA record. DNS
holds much more than just IP address records, though. You can ask it
"What servers handle the mail for the domain example.org?" (MX records),
"What is the geographical location of example.org?" (LOC records) and
"What are the SSH host keys of example.org, so that I don't have to
hassle users about trusting fingerprints?" (SSHFP records).

SRV records answer the question "Where is the ... service for ....
located?" They are a more sophisticated response than a CNAME because
they contain quite a bit of information. Firstly, SRV records should
follow a defined format. "Everyone knows" that to get to the web server
on example.org, you open port 80 at www.example.org, don't they? But
what if you don't want to host it there? With an SRV record at
_http._tcp.example.org (HTTP is always served over TCP, but the format
is always _service._protocol.name), you can point it elsewhere.

The content of an SRV record consists of a string with four
space-separated fields: Priority, Weight. Port and Target. Priority and
Weight are used together, and any client which handles SRV records is
supposed to read them all to provide weighted load-balancing. Port and
Target are the most interesting parts here, though. With these, you can
tell a suitable client that the "HTTP" service for "example.org" is
actually on port 8080 of "dev.example.org" and, the client will connect
there instead of port 80.

Now, SRV records aren't magic. Many protocols either predate the idea of
SRV records, or just don't use it. Some protocols mandate its use. In
the case of HTTP, though, it would appear that the choice to use SRV
records is a client choice. If the User Agent performs an SRV lookup
(like _newer_ apt/apt-get versions do), then they can be redirected.
Otherwise, they will make the assumption to use the well-known addresses.

For more information, please re-read
https://en.wikipedia.org/wiki/SRV_record

[toc] | [prev] | [next] | [standalone]

#234934

[Multipart message — attachments visible in raw view] — view raw

On Jo, 06 mai 21, 08:43:22, The Wanderer wrote:
> On 2021-05-06 at 08:40, Greg Wooledge wrote:
> 
> > On Thu, May 06, 2021 at 08:33:47AM -0400, The Wanderer wrote:
> >
> >> On 2021-05-06 at 08:28, Andrei POPESCU wrote:
> >>
> >> > Maybe this helps (though it might be outdated):
> >> > 
> >> >     https://deb.debian.org
> >> 
> >> That's the mirror auto-selector which the original complainant here was
> >> using, and which apparently chose debian.map.fastlydns.net as the mirror
> >> to be used, which led to the error which was the subject of the complaint.
> >> 
> >> IOW, I think that site is part of the problem (in that it has a broken
> >> mirror listed), but I don't see how it could help. Is there a part of
> >> your suggestion I'm not understanding?
> > 
> > I believe the suggestion was that you actually *go* to that web page
> > in your web browser and read what it says.  It's fairly short.
> 
> I did, and I didn't see how it was helpful, thus my question.
> 
> > To be fair, though, it'll basically reiterate advice that was
> > already given in this thread ("try a different mirror").
> 
> Which might help in the immediate term, but doesn't get the actual
> problem fixed, that problem being either with the mirror or with the
> configuration of the redirector to include that mirror.

It explains how it's set up, hints that the method used (SRV records) 
might not be supported by all software and provides a workaround.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#234913

On Thu, May 06, 2021 at 08:33:47AM -0400, The Wanderer wrote:
> On 2021-05-06 at 08:28, Andrei POPESCU wrote:
> > Maybe this helps (though it might be outdated):
> > 
> >     https://deb.debian.org
> 
> That's the mirror auto-selector which the original complainant here was
> using, and which apparently chose debian.map.fastlydns.net as the mirror
> to be used, which led to the error which was the subject of the complaint.
> 
> IOW, I think that site is part of the problem (in that it has a broken
> mirror listed), but I don't see how it could help. Is there a part of
> your suggestion I'm not understanding?

I believe the suggestion was that you actually *go* to that web page
in your web browser and read what it says.  It's fairly short.

To be fair, though, it'll basically reiterate advice that was already
given in this thread ("try a different mirror").

[toc] | [prev] | [next] | [standalone]

#234914

Andrei POPESCU wrote: 
> On Jo, 06 mai 21, 13:16:36, tomas@tuxteam.de wrote:
> > On Thu, May 06, 2021 at 07:00:02AM -0400, The Wanderer wrote:
> > 
> > [...]
> > 
> > > The only options I see offhand (though I'm sure I'm missing some) are A:
> > > that the debian.map.fastlydns.net mirror is in fact not functioning
> > > correctly for anyone at present, or B: that for some reason the
> > > complainer's Internet access is being blocked/filtered in a way which
> > > prevents access to that mirror without preventing access to e.g. this
> > > mailing list.
> > 
> > FWIW, I get a connect, but the page's content is something like
> > 
> >  | Fastly error: unknown domain: debian.map.fastlydns.net. Please check that this domain has been added to a service.
> >  | 
> >  | Details: cache-hhn11565-HHN
> > 
> > The HTTP code is 500 (had to resort to curl to get that. Browsers
> > are getting more useless at each minor version, it seems :-(
> > 
> > So I'd go with (A). The fastlydns folks gotta something to fix.
> 
> Maybe this helps (though it might be outdated):
> 
>     https://deb.debian.org
> 

I received a note from the thread originator saying that they
had changed from http to https and things were working now.

-dsr-

[toc] | [prev] | [next] | [standalone]

#234928

On Thu, 6 May 2021 13:16:36 +0200
<tomas@tuxteam.de> wrote:

> On Thu, May 06, 2021 at 07:00:02AM -0400, The Wanderer wrote:
> 
> [...]
> 
> > The only options I see offhand (though I'm sure I'm missing some) are A:
> > that the debian.map.fastlydns.net mirror is in fact not functioning
> > correctly for anyone at present, or B: that for some reason the
> > complainer's Internet access is being blocked/filtered in a way which
> > prevents access to that mirror without preventing access to e.g. this
> > mailing list.
> 
> FWIW, I get a connect, but the page's content is something like
> 
>  | Fastly error: unknown domain: debian.map.fastlydns.net. Please check that this domain has been added to a service.
>  | 
>  | Details: cache-hhn11565-HHN
> 
> The HTTP code is 500 (had to resort to curl to get that. Browsers
> are getting more useless at each minor version, it seems :-(

In Firefox,  "Tools / Browser Tools / Web Developer Tools / Network"
shows the 500 status code.

Celejar

[toc] | [prev] | [next] | [standalone]

#234936

[Multipart message — attachments visible in raw view] — view raw

On Thu, May 06, 2021 at 11:39:27AM -0400, Celejar wrote:
> On Thu, 6 May 2021 13:16:36 +0200
> <tomas@tuxteam.de> wrote:
> 
> > On Thu, May 06, 2021 at 07:00:02AM -0400, The Wanderer wrote:
> > 
> > [...]
> > 
> > > The only options I see offhand (though I'm sure I'm missing some) are A:
> > > that the debian.map.fastlydns.net mirror is in fact not functioning
> > > correctly for anyone at present, or B: that for some reason the
> > > complainer's Internet access is being blocked/filtered in a way which
> > > prevents access to that mirror without preventing access to e.g. this
> > > mailing list.
> > 
> > FWIW, I get a connect, but the page's content is something like
> > 
> >  | Fastly error: unknown domain: debian.map.fastlydns.net. Please check that this domain has been added to a service.
> >  | 
> >  | Details: cache-hhn11565-HHN
> > 
> > The HTTP code is 500 (had to resort to curl to get that. Browsers
> > are getting more useless at each minor version, it seems :-(
> 
> In Firefox,  "Tools / Browser Tools / Web Developer Tools / Network"
> shows the 500 status code.

Yes, thanks :)

I knew there had to be some way to get there. Doing "curl -ki ..." is
so much simpler :)

Me? I'd expect the browser showing the HTTP response code on its own --
at least when it is unexpected (i.e. 4xx, 5xx but not necessarily 2xx,
3xx).

But that might, at the end, get us smarter users. The Horrors.

Cheers
 - t

[toc] | [prev] | [next] | [standalone]

#234907

The Wanderer wrote: 
> On 2021-05-06 at 05:41, Dan Ritter wrote:
> 
> > https://www.debian.org/mirror/list
> 
> In case A, either the people who run that mirror need to fix whatever's
> wrong with it, or it needs to be removed from the auto-selector's list.
> 
> In case B, either the blocking is a mistake (in which case someone -
> possibly the mirror maintainers, possibly the complainer - needs to
> reach out to whoever's doing the blocking and get them to correct that
> mistake), or it's intentional (in which case the complainer is off-base,
> and needs to either switch to a different Internet access - which might
> be impossible, depending on the circumstances - or stop using the
> auto-selector and choose a mirror that isn't being blocked).

In all of these cases, the fastest solution from the perspective
of this particular person is to choose a different mirror from
the list.

If they come back and say "none of them work", that's useful
information.

If they come back and say "this particular one worked", that's
also useful information.

-dsr-

[toc] | [prev] | [next] | [standalone]

#234910

[Multipart message — attachments visible in raw view] — view raw

On Thu, 06 May 2021 07:00:02 -0400
The Wanderer <wanderer@fastmail.fm> wrote:

> The only options I see offhand (though I'm sure I'm missing some) are
> A: that the debian.map.fastlydns.net mirror is in fact not functioning
> correctly for anyone at present, or B: that for some reason the
> complainer's Internet access is being blocked/filtered in a way which
> prevents access to that mirror without preventing access to e.g. this
> mailing list.

I also have had problems with debian.map.fastlydns.net. That leads me
to suspect A. I simply ignored it until it went away.

Anyone else?


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#235438

[Multipart message — attachments visible in raw view] — view raw

You may have noticed that you didn't get any responses.  Your message was
caught by my spamfilter, and was furthermore not very clear.

As for your error, it seems likely that there is an error with the
internet connection.  Why and how I cannot tell you, as there is not
enough information

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web