Hello,
I have been attempting to configure Google OAuth for my GitLab instance
which is running on a VM in my server. Instead of using IPTables
port-forwarding, I have configured an nginx reverse proxy on the host. This
has worked fine for logging into the server and using the site with a
regular user account, but when I attempt a Google OAuth login, it fails (I
see "Processing by OmniauthCallbacksController#failure as HTML").
Strangely, when using a browser on the host server, I can login just fine
using Google OAuth.
What exactly in the reverse proxying could be affecting the OAuth steps?
(Note: when logging in using a browser on the host, I don't specify the
VM's ip. I use the FQDN of the host server.)
Here is my fairly basic, straight-forward nginx conf:
server {
listen 80;
server_name example.com; ## example.com is just a placeholder for
here, of course
access_log /var/log/nginx/gitlab.access.log;
error_log /var/log/nginx/gitlab.error.log;
root /dev/null;
## send request back to gitlab ##
location / {
proxy_pass http://192.168.122.134;
proxy_redirect off;
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_set_header X-Forwarded-Proto $scheme;
}
}
Is there anyway I can increase the verboseness of the production log? I was
thinking that may help me track down my issue.
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/gitlabhq/e8c3470f-d7b9-4e72-9cb2-d6b0dcb2e9f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
