Reverse proxing gitbucket via nginx

Question

I'm currently trying to make nginx work with gitbucket using following this tutorial.

Although this is the official gitbucket wiki this page is very incomplete, and i need to adapt some details from the guide for apache, mainly the prefix thing, to make gitbucket work with nginx.

So my resulting sites-available/gitbucket is here:

server {
    listen   80; # The default is 80 but this here if you want to change it.
    server_name mydomain.xxx;

    location /gitbucket {
        proxy_pass              http://localhost:8080/gitbucket;
        proxy_set_header        Host $host;
        proxy_set_header        X-Real-IP $remote_addr;
        proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_connect_timeout   150;
        proxy_send_timeout      100;
        proxy_read_timeout      100;
        proxy_buffers           4 32k;
        client_max_body_size    500m; # Big number is we can post big commits.
        client_body_buffer_size 128k;
    }
}

When i enable gitbucket it works, so http://mydomain.xxx/gitbucket redirects to my gitbucket instance, but then nginx stop serving any index file i put on my /var/www/html, and instead serves the default index page supplied when we fresh install it. And when disabling gitbucket the index from html folder is served again.

I've tried to make a ticket on gitbucket repo but i didn't get any satisfactory reply. So can someone shed me light on this problem?

Thanks in advance!

Answer 1

The tutorial you linked gives a very specific example for gitbucket.

If you're setting up sites using nginx you will have to keep in mind that each site has a bunch of settings and that there is a logic that will determine what takes precedence when. This digital ocean article titled "Understanding Nginx Server and Location Block Selection Algorithms" about how that's determined.

From what you explained in your comments you ended up with two site files. One being the default file where you set your regular root for your site and one for gitbucket that just contained the gitbucket location block and (that's is important) a listen directive and server name directive.

The first step nginx takes to determine which site to deliver is to figure out what server block to use. As it currently is you likely have two server blocks with the same definition. Your default and gitbucket block are listening to port 80 for the same server name. So one is always going to be overwriting the other.

If you want both to work you have a few options:

• Set either site to a different port using the listen directive.
• Change the server name for either site. This could also include a sub domain. Whenever this works or not might be dependend on the DNS configuration for the site.
• Just include the location block from your gitbucket configuration in your default file.

A location block, as the name implies, just defines settings for a very specific location. It doesn't really need an independent server block, at least not if it's such a basic definition.