did you run `gitlab-ctl reconfigure` after changing gitlab.rb?

Best regards,
Sytse Sijbrandij
CEO GitLab B.V.


On Sat, Nov 22, 2014 at 1:22 PM, Etienne Savard <esav...@symbiosoft.net> wrote:
> Hi,
>
> I have managed to install correctly gitlab-omnibus on DigitalOcean.  I have
> also installed Jenkins on this machine.  All applications are available via
> a subdomain and a SSL reverse proxy in nginx.  The Nginx part seems to work
> because I'm able to access both Jenkins and GitLab using their subdomain :
>
> https://git.example.com -> 127.0.0.1:8080
> https://ci.example.com -> 127.0.0.1:8081
>
> The only thing I still can't get to work is the external_url directive in
> the gitlab.rb file.  Whatever I put in there, every repo url is still
> http://example.com/myuser/myrepo.git...
>
> My FQDN is example.com and not git.example.com as I have other server on the
> same machine but under different subdomain name.  Is there a way to force
> gitlab to use https://git.example.com hostname instead of the FQDN?
>
> Here is a copy of my /etc/gitlab/gitlab.rb :
>
> # Check and change the external_url to the address your users will type in
> their browser
> external_url = 'git.example.com'
>
> unicorn['worker_processes'] = 3
> unicorn['worker_timeout'] = 100
> postgresql['shared_buffers'] = '100MB'
>
> gitlab_rails['smtp_enable'] = true
> gitlab_rails['smtp_address'] = "localhost"
> gitlab_rails['smtp_port'] = 456
> #gitlab_rails['smtp_user_name'] = "smtp user"
> #gitlab_rails['smtp_password'] = "smtp password"
> gitlab_rails['smtp_domain'] = "example.com"
> #gitlab_rails['smtp_authentication'] = "login"
> #gitlab_rails['smtp_enable_starttls_auto'] = true
> gitlab_rails['gitlab_email_from'] = 'g...@example.com'
>
> And this is my configuration for nginx :
>
> upstream gitlab {
>     server unix:/var/opt/gitlab/gitlab-rails/sockets/gitlab.socket;
> }
>
> server {
>     listen 80;
>     server_name git.example.com;
>     return 301 https://$server_name$request_uri;
> }
>
> server {
>     listen 443;
>     server_name git.example.com;
>
>     ssl_certificate           /etc/nginx/star.example.com.crt;
>     ssl_certificate_key       /etc/nginx/star.example.com.key;
>     ssl on;
>     ssl_session_timeout 5m;
>     ssl_session_cache  builtin:1000  shared:SSL:10m;
>     ssl_protocols  TLSv1 TLSv1.1 TLSv1.2;
>     ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
>     ssl_prefer_server_ciphers on;
>     access_log            /var/log/nginx/gitlab.access.log;
>
>     location / {
>         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;
>
>         # Fix the "It appears that your reverse proxy set up is broken"
> error.
>         proxy_pass          http://127.0.0.1:8080;
>         proxy_read_timeout  90;
>         proxy_redirect      http://127.0.0.1:8080 https://git.example.com;
>     }
> }
>
>
> Thanks in advance for your help!
>
> --
> 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/0818d5dc-5439-42fb-bde6-e231bf38b91a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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/CAJTzhG8FiRmcS_LgEJ6LQd1ZNNpSiESnik5M27K%2BJyOxxL5PtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to