Gitlab : No Data Received on /users/sign_in

January 5, 2014 4.1k views
I have create Gitlab from an image GitLab 6.4.3 CE. With 2Gb/2 Core CPU instance. When I try to reach my domain, it will automatic redirect to /users/sign_in without data received. however, in /home/git/gitlab/log/production.log haven't show that it dispatch /users/sign_in at all, only single request that have been processed is Started GET "/" for at 2014-01-05 00:26:45 -0500 Processing by DashboardController#show as HTML Completed 401 Unauthorized in 26ms I already modify /etc/nginx/site-enable/gitlab and restart both gitlab - nginx service... Nginx config upstream gitlab { server unix:/home/git/gitlab/tmp/sockets/gitlab.socket; } server { listen *:80; # e.g., listen; In most cases *:80 is a good idea server_name; # e.g., server_name; server_tokens off; # don't show the version number, a security best practice root /home/git/gitlab/public; # individual nginx logs for this gitlab vhost access_log /var/log/nginx/gitlab_access.log; error_log /var/log/nginx/gitlab_error.log; location / { # serve static files from defined root folder;. # @gitlab is a named location for the upstream fallback, see below try_files $uri $uri/index.html $uri.html @gitlab; } # if a file, which is not found in the root folder is requested, # then the proxy pass the request to the upsteam (gitlab unicorn) location @gitlab { proxy_read_timeout 300; # proxy_connect_timeout 300; # proxy_redirect off; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_pass http://gitlab; } } This is clean image with just a few settings as show in how-to step-by-step. Any comments to make it work?
1 Answer
Check the error logs, do you see anything in there?
Have another answer? Share your knowledge.