Skip to content
This repository has been archived by the owner on Dec 4, 2020. It is now read-only.

Installation failing due to running behind proxy #24

Open
RohanSakhale opened this issue Mar 8, 2016 · 4 comments
Open

Installation failing due to running behind proxy #24

RohanSakhale opened this issue Mar 8, 2016 · 4 comments

Comments

@RohanSakhale
Copy link

There should be a way for performing clean installing that would run behind proxy server.

Currently we tried handling by using vagrant-proxyconf plugin and exporting http_proxy and https_proxy in provision shell script,

Things we have configured

  • APT Proxy
  • Git Proxy
  • Environment variables for proxy

We are not sure what we are currently missing in proxy which is causing our installation to fail.

Please let us know if any logs we can provide for deeper analysis.

@superalex
Copy link

Hello @RohanSakhale

You could try using taiga-scripts in a ubuntu 14.04 machine. That way you could check the installation logs easily and detect what's failing exactly.

Regards,

@RohanSakhale
Copy link
Author

No luck over this too over trying multiple times in various way, there is something that we are missing which is not getting installed behind the firewall while fetching from internet.

If taiga installer provides an optional to mention Proxy Server for accessing internet behind the firewall would be a great advantage 😄

❤️ Taiga

@rbhattarai
Copy link

Hello @superalex

I configured http.proxy in .gitconfig, environment, apt, wgetrc, curlrc and tried to install Taiga in Ubuntu 16.04 behind corporate proxy server but getting below error:

taiga@taiga:~$ git clone https://github.com/taigaio/taiga-back.git taiga-back
Cloning into 'taiga-back'...
fatal: unable to access 'https://github.com/taigaio/taiga-back.git/': Received HTTP code 407 from proxy after CONNECT

Please let me know if there is any plan to fix this issue?

@jespino
Copy link
Contributor

jespino commented Oct 13, 2017

Hi @rbhattarai,

This problem is not related with Taiga or taiga infrastructure. This is mainly a problem with your company proxy and how it connects to Github.

A possible option is to try to use http://github.com/taigaio/taiga-back.git instead of https://....

Other option is try to use "git" protocol, but I suppose that won't work neither.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants