Are you sure it's nginx problem? gitlab omnibus is using embedded chef solo to provision nginx with configuration templates and whatnot. It's out of the scope of nginx configuration itself.
You should really check if your nginx configuration for jenkins actually included to the main nginx config, how you reload nginx? using gitlab-ctl will reset all hand-custom configuration except if you actually edit the template. Using gitlab-embedded nginx is possible but it's more involved, you should familiar with how gitlab omnibus works inside, there's no magic in the nginx configuration itself. On Fri, Oct 16, 2015 at 10:00 PM, edofthemountain <[email protected]> wrote: > Is there a NGINX configuration command to exclude listening for /jenkins/ > in > the gitlab-http.conf ? > > Something in the gitlab-http.conf is preventing my proxy_pass from working > in nginx-jenkins.conf ? > > Posted at Nginx Forum: > https://forum.nginx.org/read.php?2,262255,262280#msg-262280 > > _______________________________________________ > nginx mailing list > [email protected] > http://mailman.nginx.org/mailman/listinfo/nginx > -- regards, Nurahmadie --
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
