im trying to import and set a new environment compiler
bit import bit.envs/bundlers/vue -c
the request fail with a connect ETIMEDOUT
Currently, Bit does not have a specific support for it. However, it uses the openssh client found on most *nix systems (and also putty, for windows), so setting up a proxy config in the ~/.ssh/config should work. Having said that, I would want to validate it first before saying it can be done.
Additionally, some features (like the bit login command, or the anonymous usage analytics) require HTTP/S communication. To enable these features, we would need to implement support for configuring HTTP_PROXY and HTTPS_PROXY variables.
If we go through this process, I think that it鈥檚 critical to see if we can support SSH over HTTPS port as well, for proxies that block SSH port.
I will post my findings in the next couple of days.
I'm having the same issue behind a corporate firewall.
@itaymendel We're you able to verify that the proxy config in .ssh/config does indeed work? And what config values did you use? I'm completely unfamiliar with ssh config - pretend like you're explaining to a fifth grader :)
Same issue behind corporate firewall
.ssh/config file did not work for me
Update
We're checking about supporting SSH over port 443, this might help when using Bit behind a corporate firewall.
Please could you share us how to configure bit in order read ~/.ssh/config file?
Maybe we've to use https://docs.bit.dev/docs/overrides? Please could you share an example?
Only through this configuration we're able to have ssh tunneling into http request.
Host *.bit.dev
ProxyCommand connect -H http://proxyIP:proxyPort %h 443
Hi. We're also looking into using Bit.dev behind a company proxy. Have you had any progress on this issue?
We're moving Bit to HTTP/S, so proxy config should be easier to support.
Any new updates on this issue? 馃槃
Most helpful comment
Currently, Bit does not have a specific support for it. However, it uses the openssh client found on most *nix systems (and also putty, for windows), so setting up a proxy config in the
~/.ssh/configshould work. Having said that, I would want to validate it first before saying it can be done.Additionally, some features (like the
bit logincommand, or the anonymous usage analytics) require HTTP/S communication. To enable these features, we would need to implement support for configuringHTTP_PROXYandHTTPS_PROXYvariables.If we go through this process, I think that it鈥檚 critical to see if we can support SSH over HTTPS port as well, for proxies that block SSH port.
I will post my findings in the next couple of days.