"upstream" directive is not allowed here

[sjoshi10]

Hey @ehazlett , we are getting this error when we upgraded to interlock 1.4.0. We had to update nginx.conf template file to get it working. This is the error we are seeing:

2017/07/17 13:33:00 [emerg] 92#92: "upstream" directive is not allowed here in /etc/nginx/nginx.conf:95
nginx: [emerg] "upstream" directive is not allowed here in /etc/nginx/nginx.conf:95

[ehazlett]

Can you give an example of your deployment (containers, labels, etc) so I can try to re-create. Thanks!

[sjoshi10]

services:
  sonarqube:
    image: dtr-1.prod/admin/sonarqube:comp
    logging:
      driver: gelf
      options:
        tag: sonarqube
        gelf-address: udp://0.0.0.0:12201
    mem_limit: 2000m
    restart: always
    ports:
    - '8080'
    labels:
    - interlock.ssl=true
    - interlock.ssl_only=true
    - interlock.ssl_backend_tls_verify=false
    - interlock.ssl_cert=/certs/cert.pem
    - interlock.ssl_cert_key=/certs/key.pem
    - interlock.hostname=76sonarqubecomp
    - interlock.domain=apps.prod
    - gitbranch=development
    - env=prod
    - com.docker.swarm.reschedule-policies=["on-node-failure"]
networks:
  default:
    driver: overlay```

[sjoshi10]

@ehazlett this is our docker-compose.yml file

[sjoshi10]

@ehazlett were you able to recreate the problem?

[ehazlett]

I haven't yet. I'm hoping to get to it today.

[sjoshi10]

@ehazlett any luck?

[ehazlett]

@sjoshi10 hey sorry for the delay. i'm not able to reproduce this on my end. Do you have any other apps that are running that could be conflicting?

[sjoshi10]

@ehazlett Hey, we deployed this to UCP. We are getting this error because the nginx.conf that interlock produces is missing curly braces.

[sjoshi10]

user  www-data;
worker_processes  2;
worker_rlimit_nofile 65535;

error_log  /var/log/error.log warn;
pid        /etc/nginx/nginx.pid;


events {
    worker_connections  1024;
}


http {
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;
    server_names_hash_bucket_size 128;
    client_max_body_size 2048M;

    log_format  main  '$remote_addr - $remote_user [$upstream_addr] [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    keepalive_timeout  65;

    # If we receive X-Forwarded-Proto, pass it through; otherwise, pass along the
    # scheme used to connect to this server
    map $http_x_forwarded_proto $proxy_x_forwarded_proto {
      default $http_x_forwarded_proto;
      ''      $scheme;
    }

    #gzip  on;
    proxy_connect_timeout 600;
    proxy_send_timeout 600;
    proxy_read_timeout 600;
    proxy_set_header        X-Real-IP         $remote_addr;
    proxy_set_header        X-Forwarded-For   $proxy_add_x_forwarded_for;
    proxy_set_header        X-Forwarded-Proto $proxy_x_forwarded_proto;
    proxy_set_header        Host              $http_host;
    send_timeout 600;

    # ssl
    ssl_prefer_server_ciphers on;
    ssl_ciphers HIGH:!aNULL:!MD5;
    ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2;


    map $http_upgrade $connection_upgrade {
        default upgrade;
        ''      close;
    }

    # default host return 503
    server {
            listen 80;
            server_name _;

            location / {
                return 503;
            }

            location /nginx_status {
                stub_status on;
                access_log off;
            }
    }



    upstream wordpresstest4.apps.test {
        zone wordpresstest4.apps.test_backend 64k;

        server 10.177.80.146:32768;

    }



    server {
        listen 80;
        server_name wordpresstest4.apps.test;



        return 302 https://$server_name$request_uri;


    upstream interlocktest.dev {
        zone interlocktest.dev_backend 64k;

        server 10.177.80.172:32768;
        server 10.177.80.198:32768;

    }



    server {
        listen 80;
        server_name interlocktest.dev;



        return 302 https://$server_name$request_uri;


    include /etc/nginx/conf.d/*.conf;
}

[sjoshi10]

2017/07/17 13:33:00 [emerg] 92#92: "upstream" directive is not allowed here in /etc/nginx/nginx.conf:95 @ehazlett

[ehazlett]

@sjoshi10 can you see if #238 fixes? You can use the image ehazlett/interlock:pr-238 to test.

[sjoshi10]

@ehazlett I am still seeing that error after using that image.

[sjoshi10]

@ehazlett any idea why it's still happening?

[ghost]

still...

[ehazlett]

This should have been fixed. Try the 1.4.4 release (ehazlett/interlock:1.4.4).

…

On Feb 18, 2018 03:44, "asteroids" ***@***.***> wrote: still... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#226 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAP6Iui_iBHOvKJnxjOocNGG1yy7hAEPks5tV-LggaJpZM4OZ-5U> .