Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #3934

Closed
Open
Created May 14, 2013 by Administrator@rootOwner

BitNami GitLab Stack 5.1.0-2 rewrites gitlab.yml after reboot

Created by: paulvi

I am trying configure LDAP for GitLab on Bitnami stack

Then ran into problem

Could not authorize you from Ldap because “Server 192.168.133.100 refused connection on port 389”.

where 192.168.133.100 is actually gitlab server itself.

I change /opt/bitnami/apps/gitlab/htdocs/config/gitlab.yml to have

ldap:
enabled: true
host: '192.168.1.14'

, but after reboot or GitLab restart

sudo /opt/bitnami/ctlscript.sh restart gitlab_sidekiq

it is back to 192.168.133.100. That is bug!

How to make BitNami GitLab Stack not to do that?

http://stackoverflow.com/questions/16539993/bitnami-gitlab-stack-5-1-0-2-rewrites-gitlab-yml-after-reboot

Assignee
Assign to
Time tracking