Proxy Setup

Running Lattice cluster on Vagrant behind an HTTP proxy

Install the vagrant-proxyconf plugin as follows:

$ vagrant plugin install vagrant-proxyconf

Specify your HTTP proxy when provisioning your cluster:

$ http_proxy=http://PROXY_IP:PROXY_PORT \
    https_proxy=http://PROXY_IP:PROXY_PORT \
    no_proxy=local.lattice.cf \
    vagrant up

ltc build-droplet and ltc launch-droplet will detect the proxy configuration passed to vagrant and automatically pass it down into your apps. Passing -e http_proxy etc is no longer necessary.

Using ltc behind an HTTP proxy with an external Lattice cluster

ltc requires outbound HTTP and HTTPS access to connect to the Lattice cluster (e.g., local.lattice.cf or 55.66.77.88.xip.io) and DockerHub, respectively. If your network requires a proxy in order to access the Internet, set the http_proxy and https_proxy environment variables (standard for many applications) in the terminal in which you are running ltc.

Example:

$ export http_proxy=http://PROXY_IP:PROXY_PORT
$ export https_proxy=http://PROXY_IP:PROXY_PORT
$ ltc target <lattice_target>   # e.g., local.lattice.cf or 55.66.77.88.xip.io
$ ltc test -v                   # runs cluster smoke tests

“Error verifying target: Invalid Response with status code: 411”

If you see this error when running ltc target through a proxy, you have a strict HTTP proxy which is rejecting certain ltc requests. There is a story in the Lattice tracker project to improve the HTTP requests to address this issue. Unfortunately, there isn’t currently any workaround.

Modular. Flexible. Powerful

Application Instances