On 2/6/23 14:13, Jared Brogan wrote:
> Yeah, I'm not denying something like that may be happening. I mentioned
> in my original message that this does not happen on every system, so if
> anything a simple note could be appended to the current doc stating it
> could resolve the issue.
> If you (and presumably the rest of the wiki admins/contributors) deem
> this not necessary, then I will not fight that. Just trying to help the
> larger audience.
1) I am not a site admin, so I don't have a say in this.
3) My comment would be that this is the equivalent of 'fixing' a car
engine knock by turning up the radio. There is an underlying issue of
which access to the Postgres repo may only be one part. It would seem to
be the effort should be to fix that underlying issue.
>
> Thanks,
> Jared Brogan
>
> On Mon, Feb 6, 2023 at 4:09 PM Adrian Klaver <adrian.klaver@aklaver.com
> <mailto:adrian.klaver@aklaver.com>> wrote:
>
> On 2/6/23 13:52, Jared Brogan wrote:
> > Here's the output before changing to https and then afterwards:
> > image.png
> >
>
>
> That looks like DNS issues from Azure to me.
>
> In a browser I can do:
>
> http://72.32.157.246:80/pub/repos/apt/
> <http://72.32.157.246:80/pub/repos/apt/>
>
> and get to the repo.
>
> And if in a browser I do:
>
> http://apt.postgresql.org/pub/repos/apt/
> <http://apt.postgresql.org/pub/repos/apt/>
>
> I end up at:
>
> https://apt.postgresql.org/pub/repos/apt/
> <https://apt.postgresql.org/pub/repos/apt/>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
