Skip to main content
Question

Box CLI V2 doesn't use proxy?

  • May 22, 2025
  • 3 replies
  • 51 views

Forum|alt.badge.img

Hello There, 

 

We can use Box CLI 1.4 without any issue, but as soon as we setup Box CLI V2, we no longer are able to get anything. 

 

 tunneling socket could not be established, cause=connect ECONNREFUSED

 

Anyone else have this issue?

3 replies

Forum|alt.badge.img

I have the same problem. I am running the following command in Box CLI. 

 

PS C:\Program Files (x86)\@boxcli> box tokens:get -user-id $user_number
tunneling socket could not be established, statusCode=408

 

The version I am using 

 

/cli/2.0.0 win32-x86 node-v10.10.0


Forum|alt.badge.img

Hi guys,

Did someone manage to use Box CLI v2 behing a company proxy  ?

This is not supported in v2 while it was in previous versions, and it seems there is no official workaround. 

I try to find a workaround using something like SOCKSCAP64 (capturing the connection and redirecting through the proxy), but did not find a way to make it work yet.

Did someone try to do it ? 

Any idea is welcome. Please share


Forum|alt.badge.img

Hi  

 

Have you tried to set the https_proxy environment variable to your proxy on command prompt before running Box CLI commands?

set https_proxy=http://proxy_server_name:8080
set http_proxy=http://proxy_server_name:8080

https://stackoverflow.com/questions/26992886/set-proxy-through-windows-command-line-including-login-parameters

 

The above worked for me on Windows.