I installed a new proxmox LXC container with TurnKey GitLab 16.0-1.

When asked for the root password, I set one and the installation went fine.

Now I can see the GitLab login screen and I think I should be able to log in with user "root" and the password I have set. But this leads to "Invalid Login or password.".

I am really sure I made no typo in the password, because the same password works fine for SSH or Webmin.

I already removed the machine completely and did the whole process again with the exact same result.

Has anyone any idea what went wrong here?

Even better: does anyone know how to fix this situation?

Forum: 

I still have no idea what went wrong, but I managed to reset the gitlab root password using the rails console as described here:

https://docs.gitlab.com/ee/security/reset_user_password.html

Now an can log into my new GitLab installation successfully.

 

Jeremy Davis's picture

The password setting firstboot script uses the same (or at least very similar) method to set the password (as your solution). So I'm not really sure why it didn't just work?

Is it running with plenty of resources? GitLab is a beast and to run smoothly it takes a fair bit of resource allocation.

Even if it's running ok, perhaps it's especially slow to start? If that's the case, then perhaps the backend hadn't completely started by the time you were setting up the password? In that scenario, a race condition may have meant that the password you wanted may not have been set. In that case, the process would have errored, but you may have missed it?

Considering that we had huge issues with that in previous versions (and worked around it), and yours is the first complaint re v16.0 (which has been available for a while now) I suspect my guess isn't too far off.

Regardless, glad to hear that you are up and running now and we'll certainly keep an eye out for that when we do the rebuild for the next release.

Tomasz's picture

Hello I had exactly the same case (proxmox LXC container with TurnKey GitLab 16.0-1 and then invalid login on webpage) But when I first logged into SSH I noticed in the output of initialization script that not everything was OK. Below are some sample of warnings and errors. Especially postgreSQL connection failed for setting password, but later I checked that a socket file "/var/opt/gitlab/postgresql/.s.PGSQL.5432" existed.  
  • Error executing action `restart` on resource 'runit_service[gitlab-workhorse]'
  • Error executing action `restart` on resource 'runit_service[nginx]'
  • Error executing action `restart` on resource 'runit_service[grafana]'
  • Warnings: Environment variable LC_ALL specifies a non-UTF-8 locale. GitLab requires UTF-8 encoding to function properly. Please check your locale settings. Setting GitLab 'root' user password and email in database. This might take a while too. Please wait (again). Traceback (most recent call last): 85: from bin/rails:4:in `<main>' 84: from bin/rails:4:in `require' (....) 2: from /opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/pg-1.2.2/lib/pg.rb:58:in `connect' 1: from /opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/pg-1.2.2/lib/pg.rb:58:in `new'/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/pg-1.2.2/lib/pg.rb:58:in `initialize': could not conne ct to server: No such file or directory (PG::ConnectionBad) Is the server running locally and accepting connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"? 86: from bin/rails:4:in `<main>' 85: from bin/rails:4:in `require'
Tomasz's picture

PS. I see that I even have problems running gitlab-rake, something's wrong with this TurnKey GitLab! I didn't do anything, I just instantiated the template   
root@gitlab ~# sudo gitlab-rake "gitlab:password:reset"
rake aborted!
Don't know how to build task 'gitlab:password:reset' (See the list of available tasks with `rake --tasks`)
Did you mean?  gitlab:assets:vendor
/opt/gitlab/embedded/bin/bundle:23:in `load'
/opt/gitlab/embedded/bin/bundle:23:in `<main>'
(See full trace by running task with --trace)

root@gitlab ~# sudo gitlab-rake "gitlab:test"
rake aborted!
NameError: uninitialized constant RSpec
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/frontend.rake:4:in `block in <main>'
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/frontend.rake:2:in `<main>'
/opt/gitlab/embedded/service/gitlab-rails/Rakefile:10:in `<top (required)>'

Caused by:
NameError: uninitialized constant RSpec
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/frontend.rake:4:in `block in <main>'
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/frontend.rake:2:in `<main>'
/opt/gitlab/embedded/service/gitlab-rails/Rakefile:10:in `<top (required)>'
(See full trace by running task with --trace)
rake aborted!
["rake", "brakeman"] failed!
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/test.rake:12:in `block (3 levels) in <top (required)>'
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/test.rake:11:in `each'
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/test.rake:11:in `block (2 levels) in <top (required)>'
/opt/gitlab/embedded/bin/bundle:23:in `load'
/opt/gitlab/embedded/bin/bundle:23:in `<main>'
Tasks: TOP => gitlab:test
(See full trace by running task with --trace)

Running with trace:
root@gitlab ~# sudo gitlab-rake --trace "gitlab:test"
** Invoke gitlab:test (first_time)
** Execute gitlab:test
rake aborted!
NameError: uninitialized constant RSpec
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/frontend.rake:4:in `block in <main>'
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/frontend.rake:2:in `<main>'
/opt/gitlab/embedded/service/gitlab-rails/Rakefile:10:in `<top (required)>'

Caused by:
NameError: uninitialized constant RSpec
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/frontend.rake:4:in `block in <main>'
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/frontend.rake:2:in `<main>'
/opt/gitlab/embedded/service/gitlab-rails/Rakefile:10:in `<top (required)>'
(See full trace by running task with --trace)
rake aborted!
["rake", "brakeman"] failed!
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/test.rake:12:in `block (3 levels) in <top (required)>'
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/test.rake:11:in `each'
/opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/test.rake:11:in `block (2 levels) in <top (required)>'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:273:in `block in execute'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:273:in `each'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:273:in `execute'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:214:in `block in invoke_with_call_chain'
/opt/gitlab/embedded/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:194:in `invoke_with_call_chain'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/task.rb:183:in `invoke'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:160:in `invoke_task'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:116:in `block (2 levels) in top_level'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:116:in `each'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:116:in `block in top_level'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:125:in `run_with_threads'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:110:in `top_level'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:83:in `block in run'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:186:in `standard_exception_handling'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/lib/rake/application.rb:80:in `run'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/rake-12.3.3/exe/rake:27:in `<top (required)>'
/opt/gitlab/embedded/bin/rake:23:in `load'
/opt/gitlab/embedded/bin/rake:23:in `<top (required)>'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/cli/exec.rb:74:in `load'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/cli/exec.rb:74:in `kernel_load'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/cli/exec.rb:28:in `run'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/cli.rb:463:in `exec'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/cli.rb:27:in `dispatch'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/cli.rb:18:in `start'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/exe/bundle:30:in `block in <top (required)>'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/lib/bundler/friendly_errors.rb:124:in `with_friendly_errors'
/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/bundler-1.17.3/exe/bundle:22:in `<top (required)>'
/opt/gitlab/embedded/bin/bundle:23:in `load'
/opt/gitlab/embedded/bin/bundle:23:in `<main>'
Tasks: TOP => gitlab:test
 
Jeremy Davis's picture

Apologies for slow response. Your GitLab looks really broken?! I couldn't reproduce your issue, but I must admit that my experience with the TurnKey GitLab LXC build (via Proxmox) didn't go particularly well for me either...

FIrstly, are you running this as unprivileged? If not, then either try it as unprivileged or enable "nesting" for the container (weird issues when running privileged without nesting enabled is a known issue for all v16.x TurnKey LXC builds).

Beyond that, have you tried updating the installed GitLab package? Another user has recently had issues with LDAP that was a bug in GitLab itself. Obviously, this issue isn't related to LDAP, but perhaps it's another bug that has been fixed in a newer GitLab version? Try updating GitLab like this:

apt update
apt install gitlab-ce

Also FWIW you don't need to use sudo when running as root (unless you want to run as a non-root user - e.g. 'sudo -u OTHER_USER COMMAND').

If you don't have any luck, please try downloading the ISO from the GitLab appliance page and installing that into a "proper" VM. I suspect that might give a better experience anyway (unless you run it as priveledged with nesting enabled - which has security implications)... As I'm sure you're already aware GitLab requires a ton of resources; at least 2x CPU & 4GB RAM with 4GB swap (recommended 4x CPU and 8GB RAM).

Add new comment