How to troubleshoot curl, git not using http_proxy, https_proxy

User Support
1

I am trying to use both curl and git in a qube that I cloned from another existing qube.
In the clone, both curl and git fail to work saying that they cannot to connect to the server.

Traceback for curl:

$ curl --proxy http://127.0.0.1:8082/ --tlsv1.2 --proto =https --max-time 180 "$@" https://gitlab.com/gitlab-org/gitlab-development-kit/-/raw/main/support/install | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (7) Failed to connect to 127.0.0.1 port 8082 after 0 ms: Couldn't connect to server
$ curl https://gitlab.com/gitlab-org/gitlab-development-kit/-/raw/main/support/install | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (7) Failed to connect to 127.0.0.1 port 8082 after 0 ms: Couldn't connect to server

Traceback for git:

$ git clone https://github.com/asdf-vm/asdf.git ~/.asdf --branch v0.14.0
Cloning into '/home/user/.asdf'...
fatal: unable to access 'https://github.com/asdf-vm/asdf.git/': Failed to connect to 127.0.0.1 port 8082 after 0 ms: Couldn't connect to server

I tried doing sudo apt update just to see if it was a general networking issue with the qube and sudo apt update worked fine. I’ve also tried directly exporting the proxy like so:

$ export http_proxy=http://127.0.0.1:8082/
$ export https_proxy=http://127.0.0.1:8082/

Not sure what to check next. Any guidance is appreciated

2

not quite.
It’s saying that failed to connet to the proxy you have provided.

Do you really have a proxy on the same VM?
or you trying to use some QUbes related proxy services?

3

I would say that I am going by this post:

4

It seems to have been a glitch where the qube was concerned?
Just tried out curl again and it seems to be working. Not sure why

5

well, what they are talking about on that thread you linked… is completely different.
It’s about setting up a template with custom repositories.

A normal VM do not neet such proxy to reach the internet.