[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Guix on Android, getaddrinfo, failure in name resolution
From: |
白い熊 |
Subject: |
Re: Guix on Android, getaddrinfo, failure in name resolution |
Date: |
Tue, 15 Jan 2019 17:26:02 +0000 |
On January 15, 2019 5:13:26 PM UTC, "白い熊" <address@hidden> wrote:
>One thing now that I'm thinking — looking at the error output — could
>this be somehow associated with https ufiticil? I see that all the
>files from all the substitutes “guix pull” is trying to download are
>from https:// locations. The first item that it's trying to download
>for the update are certificates from letsencrypt.org
>
>Could it be that hostnames are resolved fine — which they are, as I can
>ping successfully any of the sites it's trying to access — but not the
>https:// locations?
>
>Is this possible? Can it be tested? I don't think you can nslookup or
>whatever an https:// location right? What if guix can't access secure
>sites? Is that possible?
This shouldn't be the case either — I just tried connecting to letsencrypt.org
on port 443 by openssl — no problem. So that's not generating the getaddrinfo
error…
--
白い熊
- Guix on Android, getaddrinfo, failure in name resolution, 白い熊, 2019/01/15
- Re: Guix on Android, getaddrinfo, failure in name resolution, Julien Lepiller, 2019/01/15
- Re: Guix on Android, getaddrinfo, failure in name resolution, 白い熊, 2019/01/15
- Re: Guix on Android, getaddrinfo, failure in name resolution,
白い熊 <=
- Re: Guix on Android, getaddrinfo, failure in name resolution, Julien Lepiller, 2019/01/15
- Re: Guix on Android, getaddrinfo, failure in name resolution, 白い熊, 2019/01/15
- Re: Guix on Android, getaddrinfo, failure in name resolution, Julien Lepiller, 2019/01/15
- Re: Guix on Android, getaddrinfo, failure in name resolution, 白い熊, 2019/01/15
- Re: Guix on Android, getaddrinfo, failure in name resolution, 白い熊, 2019/01/16
Re: Guix on Android, getaddrinfo, failure in name resolution, Ludovic Courtès, 2019/01/19