Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

truffle migrate / truffle obtain behind (corporate) proxy #1803

Closed
imbenwolf opened this issue Mar 7, 2019 · 10 comments
Closed

truffle migrate / truffle obtain behind (corporate) proxy #1803

imbenwolf opened this issue Mar 7, 2019 · 10 comments
Labels
bug error better issue indicates improvement to error messaging

Comments

@imbenwolf
Copy link

Issue

Truffle cannot fetch solc from solc-bin behind a proxy even when setting HTTP_PROXY and HTTPS_PROXY env variables.

I propose to:

  • add proxy option inside truffle-config OR
  • add --proxy as option when running truffle in general OR
  • add --proxy as option when running truffle command (migrate/compile/obtain) OR
  • acknowledge HTTP_PROXY and HTTPS_PROXY env variables

Steps to Reproduce

  1. Connect to a network behind proxy
  2. Change solc version inside truffle-config.js to a non-default version (e.g 0.4.24 on truffle v5)
    3.1 Execute truffle migrate/compile --> error
    3.2 Execute truffle obtain --solc= (e.g 0.4.24) --> no error but does not download

Expected Behavior

solc is downloaded and migrations are executed with correct version

Actual Results

command fails

Environment

  • Operating System: Windows 10
  • Ethereum client: ganache-cli
  • Truffle version (truffle version): 5.0.6
  • node version (node --version): 10.15.2
  • npm version (npm --version): 6.4.1
@gnidan gnidan added the error better issue indicates improvement to error messaging label Mar 10, 2019
@gnidan gnidan added bug and removed enhancement labels Apr 17, 2019
@gnidan
Copy link
Contributor

gnidan commented Apr 17, 2019

Definitely we should support that! Will look into fixing this. Thanks for raising the issue!

@pranav-deshpande
Copy link

Any update on this?

@h3nk42
Copy link

h3nk42 commented Mar 9, 2020

Is there any way to use Truffle behind a corporate proxy right now?

@eggplantzzz
Copy link
Contributor

eggplantzzz commented Mar 11, 2020

@gnidan Any thoughts as to whether this might be something we can do anything about or if there is perhaps a workaround related to the network configuration?

@gnidan
Copy link
Contributor

gnidan commented Mar 25, 2020

How does this work for Node.js in other projects? Shouldn't Node just respect the network configuration? Any insight here would be helpful!

@haltman-at
Copy link
Contributor

Closing for issue maintenance. Please let us know if there's still a problem and we can reopen.

@kigawas
Copy link

kigawas commented Jun 11, 2021

Closing for issue maintenance. Please let us know if there's still a problem and we can reopen.

This problem still happens

@Jason5Lee
Copy link

Please fix it.

@cds-amal cds-amal reopened this Jul 1, 2021
@davidmurdoch
Copy link
Member

Closing this one and tracking this issue over at #4016

@sg552
Copy link

sg552 commented Jun 20, 2022

I met the same problem, and I started an http proxy ( using pproxy + socks5 ) , and make this bash file:

# my_env
export HTTP_PROXY="http://192.168.10.54:8080"
export HTTPS_PROXY="http://192.168.10.54:8080"
export http_proxy="http://192.168.10.54:8080"
export https_proxy="http://192.168.10.54:8080"

source my_env and then run truffle command, everything is OK.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug error better issue indicates improvement to error messaging
Projects
None yet
Development

No branches or pull requests