cli: Linux: CLI- Configuration Error

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!

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 21 (9 by maintainers)

Most upvoted comments

I’ve opened a pull request to add the configurable http timeout.

Once that gets merged and a cut is released, you will be able to pass a flag --timeout= which will override the default timeout that we use. E.g.

exercism download --track=go --exercise=hello-world --timeout=60

kytrinyx on Aug 26, 2018

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. https://github.com/docker/for-win/issues/611

arademann on Aug 22, 2018