Re: not working with ssl/ipv6?
"Darshit Shah" <[email protected]> Thu, 28 Mar 2024 09:16:38 +0100
| Newsgroups | gmane.comp.web.wget.general |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Mar 27, 2024, at 22:05, Brian Vargo wrote: > Should probably include this: > $ wget --version > GNU Wget 1.21.2 built on linux-gnu. > $ ufw down; wget > http://ftp.us.debian.org/debian/pool/main/f/foliate/foliate_4.~really3.1.0-0.1_all.deb > #no firewall > sudo: ufw: command not found > --2024-03-27 16:45:23-- > http://ftp.us.debian.org/debian/pool/main/f/foliate/foliate_4.~really3.1.0-0.1_all.deb > Resolving ftp.us.debian.org (ftp.us.debian.org)... 2600:3402:200:227::2, > 2600:3404:200:237::2, 2620:0:861:2:208:80:154:139, ... > Connecting to ftp.us.debian.org (ftp.us.debian.org > )|2600:3402:200:227::2|:80... > > I see this isn't over ssl, just 80. But it's IPV6. Is there some way to > turn that off (for now until I figure out why IPv4 requests work and the > others don't? You can use the `-4` option to force IPv4 only mode. > > Suggestions on where else I should start looking for the problem with IPv6? > (*sigh*) Firewall's not the issue as you can see unless there's some IP > tables thing I didn't do. > No idea. But as an additional anecdote, I also seem to have troubles with IPv6 connectivity to github servers in particular. > also what resolver is feeding it IPv6 addresses instead IPv4 addresses? I > could stop it there too... > Your default system resolver. We just make a libc getaddrinfo() call > > On Wed, Mar 27, 2024 at 2:01 PM Tim Rühsen <[email protected]> wrote: > >> On 3/27/24 17:32, Brian Vargo wrote: >> > I've not been able to use wget on ssl with github and debian. I ^C'ed >> out >> > of the gitusercontent one (it would have timed out) and the second one is >> > just a random example: >> > >> > ``` >> > $ wget >> > >> https://raw.githubusercontent.com/MohamedBassem/hoarder-app/main/docker/docker-compose.yml >> > --2024-03-27 12:27:25-- >> > >> https://raw.githubusercontent.com/MohamedBassem/hoarder-app/main/docker/docker-compose.yml >> > Resolving raw.githubusercontent.com (raw.githubusercontent.com)... >> > 2606:50c0:8000::154, 2606:50c0:8002::154, 2606:50c0:8003::154, ... >> > Connecting to raw.githubusercontent.com >> > (raw.githubusercontent.com)|2606:50c0:8000::154|:443... >> > ^C >> >> Works fine for me on Debian. >> Did you check your network / firewall? >> >> $ wget >> >> https://raw.githubusercontent.com/MohamedBassem/hoarder-app/main/docker/docker-compose.yml >> --2024-03-27 >> <https://raw.githubusercontent.com/MohamedBassem/hoarder-app/main/docker/docker-compose.yml--2024-03-27> >> 18:49:21-- >> >> https://raw.githubusercontent.com/MohamedBassem/hoarder-app/main/docker/docker-compose.yml >> Resolving raw.githubusercontent.com (raw.githubusercontent.com)... >> 2606:50c0:8002::154, 2606:50c0:8003::154, 2606:50c0:8000::154, ... >> Connecting to raw.githubusercontent.com >> (raw.githubusercontent.com)|2606:50c0:8002::154|:443... connected. >> HTTP request sent, awaiting response... 200 OK >> Length: 1251 (1.2K) [text/plain] >> Saving to: ‘docker-compose.yml’ >> >> docker-compose.yml >> 100%[=======================================================>] 1.22K >> --.-KB/s in 0s >> >> 2024-03-27 18:49:21 (42.8 MB/s) - ‘docker-compose.yml’ saved [1251/1251] >> >> >> $ wget --version >> GNU Wget 1.24.5 built on linux-gnu. >> >> -cares +digest -gpgme +https +ipv6 +iri +large-file -metalink +nls >> +ntlm +opie +psl +ssl/gnutls >>