Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

[Raku] Cannot Access https://docs.raku.org/

by dvergin (Monsignor)
on Jun 25, 2021 at 20:47 UTC ( [id://11134300] : perlquestion . print w/replies, xml ) Need Help??

dvergin has asked for the wisdom of the Perl Monks concerning the following question:

For some time I have been unable to access docs.raku.org

The response I get using Chrome on Chromebook, Linux, Windows, and Android is:

This site can’t provide a secure connection docs.raku.org sent an invalid response.

In an attempt to learn more about what's going on, if I try to grab the Raku Docs home page from a linux command line with wget, here's what happens:

$ wget https://docs.raku.org --2021-06-25 13:36:45-- https://docs.raku.org/ Resolving docs.raku.org (docs.raku.org)... 2606:4700:20::681a:f4 +6, 2606:4700:20::681a:e46, 2606:4700:20::ac43:4429, ... Connecting to docs.raku.org (docs.raku.org)|2606:4700:20::681a:f +46|:443... connected. GnuTLS: An unexpected TLS packet was received. Unable to establish SSL connection.

Is this a known issue? I can find no mention of it on the web. That suggests that the problem is unique to my situation. But I have had no problem accessing other web sites.

If it's specific to my situation, how do I go about diagnosing the problem and connecting to this key documentation source?

If access to docs.raku.org is broken for everyone, is anything known about the restoration of access to the site?

TIA

------------------------------------------------------------
"Perl is a mess and that's good because the
problem space is also a mess.
" - Larry Wall

Replies are listed 'Best First'.
Re: [Raku] Cannot Access https://docs.raku.org/
by choroba (Cardinal) on Jun 25, 2021 at 21:05 UTC
    I can access the site both from wget and from a browser (Firefox). Are you sure your system is up to date? What versions of wget and gnutls do you use?

    map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

      Thanks for the response, choroba.

      All browser software on my various devices is up to date. Also, all apt packages on my two Debian Buster systems are up to date.

      I can successfully access the docs.raku.org home page in two (inconvenient) ways. 1)If I turn off wifi on my cell phone the docs.raku.org index.html page loads just fine over the cell data network. 2)If I ssh into my web server in a cloud somewhere out there I can wget the index.html page from there as well.

      All of which leads me to want to look upstream from the individual machines on my local wifi network.

      So... my Comcast router? I can bring up the admin interface in a browser but I don't know what to look for. Something further upstream? I'm getting out of my depth here.

      All suggestions welcome.

      ------------------------------------------------------------
      "Perl is a mess and that's good because the
      problem space is also a mess.
      " - Larry Wall

        Maybe check the DNS server settings in the router's menu?

        map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
Re: [Raku] Cannot Access https://docs.raku.org/
by NetWallah (Canon) on Jun 25, 2021 at 22:53 UTC
    Looks like you are connecting via IPV6 - and there may be issues with that.

    Try using one of the IPv4 addresses below:

    Name: docs.raku.org Addresses: 2606:4700:20::681a:f46 2606:4700:20::681a:e46 2606:4700:20::ac43:4429 104.26.14.70 172.67.68.41 104.26.15.70

                    "The difficult we do today; the impossible takes a little longer."

      Thanks, NetWallah.

      I am assuming that you are suggesting the bottom three addresses in the list you gave. My browser doesn't recognize the top three as URLs.

      Each of those bottom three addresses gives the same result:

      Error 1003 Ray ID: 6651ee569bb639f6 • 2021-06-25 23:21:14 UTC Direct IP access not allowed What happened? You've requested an IP address that is part of the Cloudflare networ +k. A valid Host header must be supplied to reach the desired website.

      You said, "Looks like you are connecting via IPV6 - and there may be issues with that." Again, I'm out of my depth here, but is there no way to just say, "Please don't use IPV6" (perhaps just for this site)? And why would IPV6 be a problem? And why would this be happening with just this one particular web site. I do a _lot_ of web reading on a widely varied range of sites -- and this is the only case where this problem has come up.

      This article:

      IPv6 support on Chrome OS https://support.google.com/chrome/a/answer/9211990?hl=en
      seemed promising until I remembered that this problem is occurring with Chrome, Vivaldi, Edge, _and_ wget on (variously) Chrome OS, Windows, Android, and Debian. Are the suggestions on that page relevant for all access to IPV6 from this side of my router?

      ------------------------------------------------------------
      "Perl is a mess and that's good because the
      problem space is also a mess.
      " - Larry Wall

        Here are a few alternatives from ServerFault/StackExchange that you could experiment with to allow access to the Roku site via IP address.

        I see you have discontinued active discussion on this issue, but , hopefully you have time for a few short tests.

                        "The difficult we do today; the impossible takes a little longer."

Re: [Raku] Cannot Access https://docs.raku.org/
by kcott (Archbishop) on Jun 26, 2021 at 05:52 UTC

    G'day dvergin,

    I'm not experiencing any problems. Just for the record, here's what I tried.

    On Firefox (version 89.0.2): https://docs.raku.org/ works fine; and, http://docs.raku.org/ and docs.raku.org both redirect to that URL.

    $ wget --version GNU Wget 1.21.1 built on cygwin. ... $ wget https://docs.raku.org --2021-06-26 15:39:21-- https://docs.raku.org/ Resolving docs.raku.org (docs.raku.org)... 104.26.15.70, 104.26.14.70, + 172.67.68.41, ... Connecting to docs.raku.org (docs.raku.org)|104.26.15.70|:443... conne +cted. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘index.html’ index.html [ <=> + ] 6.16K --.-KB/s in 0s 2021-06-26 15:39:23 (16.4 MB/s) - ‘index.html’ saved [6307]
    $ ping --version ping (GNU inetutils) 2.0 ... $ ping docs.raku.org PING docs.raku.org (104.26.15.70): 56 data bytes 64 bytes from 104.26.15.70: icmp_seq=0 ttl=60 time=5.763 ms ... 64 bytes from 104.26.15.70: icmp_seq=14 ttl=60 time=5.437 ms --- docs.raku.org ping statistics --- 15 packets transmitted, 15 packets received, 0% packet loss round-trip min/avg/max/stddev = 4.907/5.625/6.328/0.393 ms

    I'm not sure if any of that helps you at all. It does indicate the docs.raku.org is generally healthy.

    — Ken

Re: [Raku] Cannot Access https://docs.raku.org/
by rizzo (Curate) on Jun 26, 2021 at 11:04 UTC

    Works fine for me using firefox, wget and fetch, but they are all openssl based.

    You could try to debug your connection directly using gnutls-cli. The output of

    gnutls-cli -V -d 3 docs.raku.org

    is pretty exhaustive.

Re: [Raku] Cannot Access https://docs.raku.org/
by dvergin (Monsignor) on Jun 26, 2021 at 21:23 UTC

    Thanks to all who have chipped in with suggestions and ideas.

    I had hoped for a quick fix on this. But I fear it has run on rather long on an issue that is only marginally related to Raku programming per se. So I am ready to close this thread out here and take the matter up else where -- starting with Comcast tech support.

    I have discovered that if I reboot my Comcast router, I can freely load pages from docs.raku.org, as many as I want, for about 20-30 minutes. Then the problem begins, affecting all machines on my lan, and continuing until I reboot the router again.

    While I pursue a solution elsewhere, I can get by just fine accessing docs.raku.org pages via the Internet Archive.

    Cheers,
    David

    ------------------------------------------------------------
    "Perl is a mess and that's good because the
    problem space is also a mess.
    " - Larry Wall

Re: [Raku] Cannot Access https://docs.raku.org/
by dvergin (Monsignor) on Jun 26, 2021 at 01:12 UTC

    Hmmm... Perhaps the issue is not IPV6 after all (as suggested elsewhere in this thread).

    Check this out:

    $ wget --inet4-only https://docs.raku.org --2021-06-25 18:01:47-- https://docs.raku.org/ Resolving docs.raku.org (docs.raku.org)... 104.26.15.70, 172.67.68.4 +1, 104.26.14.70 Connecting to docs.raku.org (docs.raku.org)|104.26.15.70|:443... con +nected. GnuTLS: An unexpected TLS packet was received. Unable to establish SSL connection. $ wget --inet6-only https://docs.raku.org --2021-06-25 18:06:19-- https://docs.raku.org/ Resolving docs.raku.org (docs.raku.org)... 2606:4700:20::ac43:4429, +2606:4700:20::681a:e46, 2606:4700:20::681a:f46 Connecting to docs.raku.org (docs.raku.org)|2606:4700:20::ac43:4429| +:443... connected. GnuTLS: An unexpected TLS packet was received. Unable to establish SSL connection.
    As you can see, the request fails in the same way for both IPV6 and IPV4.

    So how do I go about diagnosing this failure to access docs.raku.org? It _does_ seem to be related to access through my Comcast router and network (access via my cloud server and via cell data both work fine). It does _not_ seem to be dependent on IPV6 vs IPV4.

    ------------------------------------------------------------
    "Perl is a mess and that's good because the
    problem space is also a mess.
    " - Larry Wall

      So how do I go about diagnosing this failure to access docs.raku.org? It _does_ seem to be related to access through my Comcast router and network (access via my cloud server and via cell data both work fine). It does _not_ seem to be dependent on IPV6 vs IPV4.

      Are you in prison? (That's a joke.) I'm glad you offer the example, because the raku target makes a good canary in coalmine for whether you can do anything with the internet, whether one is 'alive' in some sense. This was my experience from western US with a linux notebook:

      $ wget -r https://docs.raku.org ... --2021-06-25 19:16:36-- https://docs.raku.org/css/app.css?v=7 Reusing existing connection to docs.raku.org:443. HTTP request sent, awaiting response... 200 OK Length: 34556 (34K) [text/css] Saving to: ‘docs.raku.org/css/app.css?v=7’ docs.raku.org/css/a 100%[===================>] 33.75K --.-KB/s in + 0.001s 2021-06-25 19:16:37 (53.8 MB/s) - ‘docs.raku.org/css/app.css?v=7’ save +d [34556/34556] FINISHED --2021-06-25 19:16:37-- Total wall clock time: 7m 24s Downloaded: 1719 files, 67M in 7.1s (9.41 MB/s) $

      You talk about your router. I would definitely give it a hard start to rule out malware/disfunction in that realm. My $.02

      Happy Friday....

        I wonder if OP has obsolete SSL certificates and/or some issues with GNU TLS (as opposed to OpenSSL (wget -- with OpenSSL 1.1.1k_1,1 -- worked on FreeBSD 13)).