Answers: <p>After a spending a lot of time I decided not to continue with this approach and decided to use Jenkins helm.</p>
  
Answers: CC BY-SA 3.0
Answers: 2018-04-27T16:28:03.463Z
Answers: 2018-04-27T16:28:03.463Z
Answers: 030
Answers: <p>VIRTUAL_HOST is meant to point to the internal port, in your case it should be 8080 instead of 8083</p>
  
Answers: CC BY-SA 3.0
Answers: 2018-04-15T17:55:00.067Z
Answers: 2018-04-15T17:55:00.067Z
Answers: Hludwig
Body: <p><a href="https://github.com/jwilder/nginx-proxy" rel="nofollow noreferrer">https://github.com/jwilder/nginx-proxy</a></p>
  
  <pre><code>nginx.1    | 2018/03/04 22:24:54 [error] 102#102: *276 no live upstreams
  while connecting to upstream, client: 83.85.143.226, server:
  jenkins.releasesoftwaremoreoften.com, request: "GET / HTTP/2.0", upstream:
  "http://jenkins.releasesoftwaremoreoften.com/", host: 
  "jenkins.releasesoftwaremoreoften.com"
  </code></pre>
  
  <p>The docker-compose file looks as follows:</p>
  
  <pre><code>version: '3'
  services:
    jenkins:
      image: jenkins/jenkins:lts
      environment:
        - VIRTUAL_HOST=jenkins.releasesoftwaremoreoften.com
        - VIRTUAL_PORT=8083
      ports:
        - 127.0.0.1:8083:8080
        - 127.0.0.1:50000:50000
      volumes:
        - /usr/local/jenkins/jenkins_home:/var/jenkins_home
      networks:
        - rproxy
        - jenkins
  
  networks:
    jenkins:
    rproxy:
      external:
        name: rproxy
  </code></pre>
  
  <p>Another attempt to make it work, was changing the VIRTUAL_HOST to 80, but that did not work as well.</p>
  
  <p>Navigating to <a href="http://jenkins.releasesoftwaremoreoften.com/" rel="nofollow noreferrer">http://jenkins.releasesoftwaremoreoften.com/</a> returns a 502.</p>
  
Tags: <nginx><rproxy>
Title: How to solve `no live upstreams while connecting to upstream` when trying to rproxy jenkins using jwilder/nginx?
UserDisplayName: 030
ThreadText: # How to solve `no live upstreams while connecting to upstream` when trying to rproxy jenkins using jwilder/nginx?
  
  (Asked by: username_0 on 2018-03-04)
  
  <https://github.com/jwilder/nginx-proxy>
  
  ```
  nginx.1    | 2018/03/04 22:24:54 [error] 102#102: *276 no live upstreams
  while connecting to upstream, client: 83.85.143.226, server:
  jenkins.releasesoftwaremoreoften.com, request: "GET / HTTP/2.0", upstream:
  "http://jenkins.releasesoftwaremoreoften.com/", host: 
  "jenkins.releasesoftwaremoreoften.com"
  
  ```
  
  The docker-compose file looks as follows:
  
  ```
  version: '3'
  services:
    jenkins:
      image: jenkins/jenkins:lts
      environment:
        - VIRTUAL_HOST=jenkins.releasesoftwaremoreoften.com
        - VIRTUAL_PORT=8083
      ports:
        - 127.0.0.1:8083:8080
        - 127.0.0.1:50000:50000
      volumes:
        - /usr/local/jenkins/jenkins_home:/var/jenkins_home
      networks:
        - rproxy
        - jenkins
  
  networks:
    jenkins:
    rproxy:
      external:
        name: rproxy
  
  ```
  
  Another attempt to make it work, was changing the VIRTUAL\_HOST to 80, but that did not work as well.
  
  Navigating to <http://jenkins.releasesoftwaremoreoften.com/> returns a 502.
  
  **Tags:** nginx, rproxy
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2018-04-27. Score: 0 | Accepted answer
  
  After a spending a lot of time I decided not to continue with this approach and decided to use Jenkins helm.
  
  
  ---
  
  ### Answer by username_1 on 2018-04-15. Score: -1
  
  VIRTUAL\_HOST is meant to point to the internal port, in your case it should be 8080 instead of 8083
  
  
  ---
  
  