Linux: CLI- Configuration Error

[maeckha]

I tried to configure CLI with my token, but got these errors:

[meck@lilsaint ~]$ exercism configure --token=<my token>
Error: The base API URL 'https://api.exercism.io/v1' cannot be reached.

Get https://api.exercism.io/v1/ping: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Sudo:

[meck@lilsaint ~]$ sudo exercism configure --token=<my token>
[sudo] password for meck: 
Error: The base API URL 'https://api.exercism.io/v1' cannot be reached.

Get https://api.exercism.io/v1/ping: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Troubleshoot:

[meck@lilsaint ~]$ exercism troubleshoot

Troubleshooting Information
===========================

Version
----------------
Current: 3.0.6
Latest:  3.0.6


Operating System
----------------
OS:           linux
Architecture: amd64


Configuration
----------------
Home:      /home/meck
Workspace: /home/meck/exercism (default)
Config:    /home/meck/.config/exercism
API key:   <not configured>
Find your API key at https://exercism.io/my/settings

API Reachability
----------------

GitHub:
    * https://api.github.com
    * [connected]
    * 117.199064ms

Exercism:
    * https://api.exercism.io/v1/ping
    * [connected]
    * 272.994092ms


If you are having trouble please file a GitHub issue at
https://github.com/exercism/exercism.io/issues and include
this information.

Does someone know any solution to this?
Thanks in advance!

[kytrinyx]

You should not need sudo.

This is interesting because it says that you're unable to reach the URL:

Get https://api.exercism.io/v1/ping: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

However when you call the troubleshoot command, you are able to connect. It's not fast, but it's less than a second:

Exercism:
    * https://api.exercism.io/v1/ping
    * [connected]
    * 272.994092ms

The timeout in the configure command is 10 seconds, whereas the one in the troubleshoot command is 20, which should not affect this.

You could try this:

exercism configure --token=<your token> --no-verify 

But if this is a timeout problem, you'd probably get a timeout again when calling download.

What does time curl -v https://api.exercism.io/v1/ping return?

[maeckha]

Hi, thanks for your quick response!
Your --no-verify suggestion worked and my CLI was set up immediately.
But as you predicted, download was canceled.

time curl says this:

time curl -v https://api.exercism.io/v1/ping
*   Trying 54.194.249.254...
* TCP_NODELAY set
* Connected to api.exercism.io (54.194.249.254) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=exercism.io
*  start date: Jul 10 00:00:00 2018 GMT
*  expire date: Aug 10 12:00:00 2019 GMT
*  subjectAltName: host "api.exercism.io" matched cert's "*.exercism.io"
*  issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon
*  SSL certificate verify ok.
> GET /v1/ping HTTP/1.1
> Host: api.exercism.io
> User-Agent: curl/7.61.0
> Accept: */*
> 
< HTTP/1.1 200 OK
< Date: Mon, 13 Aug 2018 16:01:29 GMT
< Content-Type: application/json; charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Server: nginx/1.10.3 (Ubuntu)
< X-Frame-Options: SAMEORIGIN
< X-XSS-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Referrer-Policy: strict-origin-when-cross-origin
< ETag: W/"571587439a6fcd390a7214f28e214fae"
< Cache-Control: max-age=0, private, must-revalidate
< Set-Cookie: site_context=normal; domain=.exercism.io; path=/
< Set-Cookie: _exercism_session=ArtZ8hjmEUjoYlBFSSOZkCj46WPY%2F4G98gXHprv6LlOFz4tfW%2Bj7vGr2msKrewJAHXHNGb%2BB65NQ4WweVRknaOX%2FJyNDeZvg9MRF8Q%3D%3D--Q25Iy9ku%2BlH%2Bdzzo--CpsXV1IL%2Bpr%2B8OUDMt63ug%3D%3D; domain=.exercism.io; path=/; HttpOnly
< X-Request-Id: ea33fccd-bf42-49d5-8f2f-5d0d8bf0ae71
< X-Runtime: 0.002527
< 
* Connection #0 to host api.exercism.io left intact
{"status":{"website":true,"database":true}}
real    0m0,283s
user    0m0,028s
sys     0m0,018s

[kytrinyx]

I don't understand how curl gets access quickly, and the CLI does not!

@nywilken have you run into anything like this before?

[nywilken]

Not sure if time is what we want here. As it is reporting time in seconds which also accounts for the the time to display the output to the screen.

@MarkyMarkz if you run the following command you should see numbers closer to what you see when running exercism troubleshoot

curl -w "connect_time: %{time_connect}, appconnect_time: %{time_appconnect}\r\n" -o /dev/null -s https://api.exercism.io/v1/ping

@kytrinyx I haven't seen this issue yet. I can reproduce if I drop the Timeout for the client to 1 second on my machine. I'm going to spend a little time reading this document https://blog.cloudflare.com/the-complete-guide-to-golang-net-http-timeouts/ to see what I can find.

@MarkyMarkz could you share a little information about your environment OS, DNS,

[maeckha]

I am glad, I´m not the only one irritated by this.
@nywilken, your command gives following output:

curl -w "connect_time: %{time_connect}, appconnect_time: %{time_appconnect}\r\n" -o /dev/null -s https://api.exercism.io/v1/ping
connect_time: 0,544756, appconnect_time: 0,711637

I´m using Manjaro with KDE. I should mention that I used Exercism before without problems on the same laptop but with Mint KDE.
Kernel: 4.16.18-rt12-MANJARO

Sorry for the noob question, I tried using dig or host for DNS information but those commands were not found neither could I install them.
Could you please give me a short explanation in how to provide the DNS information?
Thanks to both of you for your work!

[arademann]

Adding nameserver 8.8.8.8 to your /etc/resolv.conf may be a workaround. It worked for me, at least. I had the same problem a few months ago while I was working with Docker. docker/for-win#611

[nywilken]

@arademann thanks for offering that advice - I've seen others report the same solution. But there are a number of users having the same issue #711 and #712.

@MarkyMarkz I've been trying to debug this further and while I haven't confirmed it just yet because I have not setup a debug process for this I believe the issue occurs when we throw auth into the mix; possibly even load on the backend server when making the request. More specifically, with the extra connections being made the http Client is timing out. The timeout is currently set to 10 seconds.

@kytrinyx mentioned building in a flag to allow for setting the timeout at runtime would you be up for testing out that build to help give us more context on the issue?

[maeckha]

@arademann, thank you for your suggestion. Unfortunately it didn´t work.

[sudha50]

@arademann solution worked for me.