Note: Make sure your hostname can be resolved on the machine itself by either a proper DNS record or an additional line in /etc/hosts ("127.0.0.1 hostname"). This might be necessary for example if you set up GitLab behind a reverse proxy. If the hostname cannot be resolved, the fin...
When I investigated further, I found out that I needed to add some configurations to my nginx reverse proxy to support websockets. Here is the nginx configuration for the reverse proxy I borrowed from u/ccoleyKubernetes agent fails to connect to GitLab with "expected handshake response status ...
Customize if you have GitLab behind a reverse proxy which is running on a ###! different machine. ###! **Add the IP address for your reverse proxy to the list, otherwise users ###! will appear signed in from that address.** # gitlab_rails['trusted_proxies'] = [] ### Content ...
Note:Make sure your hostname can be resolved on the machine itself by either a proper DNS record or an additional line in /etc/hosts ("127.0.0.1 hostname"). This might be necessary for example if you set up GitLab behind a reverse proxy. If the hostname cannot be resolved, the final...
Customize if you have GitLab behind a reverse proxy which is running on a ###! different machine. ###! **Add the IP address for your reverse proxy to the list, otherwise users ###! will appear signed in from that address.**
Note:Make sure your hostname can be resolved on the machine itself by either a proper DNS record or an additional line in /etc/hosts (“127.0.0.1 hostname”). This might be necessary for example if you set up GitLab behind a reverse proxy. If the hostname cannot be resolved, the fin...
Note:Make sure your hostname can be resolved on the machine itself by either a proper DNS record or an additional line in /etc/hosts ("127.0.0.1 hostname"). This might be necessary for example if you set up GitLab behind a reverse proxy. If the hostname cannot be resolved, the final...
Note:Make sure your hostname can be resolved on the machine itself by either a proper DNS record or an additional line in /etc/hosts ("127.0.0.1 hostname"). This might be necessary for example if you set up GitLab behind a reverse proxy. If the hostname cannot be resolved, the final...
We use Apache as a reverse proxy in front of gitlab since we depende on Shibboleth as an authentication mechanism. The problem seems to have something to do with escaping in mod_rewrite. Our current RewriteRules
Summary Using GitLab behind a reverse proxy doesn't seem to work if the configured URL is relative, but the server is...