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
  • #8279

Closed
Open
Created Nov 08, 2014 by Administrator@rootOwner

"The change you wanted was rejected." on a fresh install

Created by: jampy

Since I was having trouble setting up LDAP login for GitLab I decided to completely reinstall it from scratch.

This is on Debian 7.7 with the GitLab Omnibus package.

I did:

dpkg -P gitlab

Then restarted the server as there was a Postgresql Instance running and that must be because of GitLab.

Then I did:

rm -rf /var/chef/backup/var/opt/gitlab/postgresql
rm -rf /var/opt/gitlab /var/chef/backup/var/opt/gitlab /tmp/gitlab*
rm -rf /var/log/gitlab
rm -rf /etc/gitlab/

dpkg -i gitlab_7.4.3-omnibus.5.1.0.ci-1_amd64.deb

# then disabled Nginx in /etc/gitlab/gitlab.rb since I'm using Apache (reverse proxy)

gitlab-ctl reconfigure

The GitLab site is working and shows the Sign In form (but no way to register?), see here: https://i.imgur.com/bzadoXF.png

Trying to login with any user/password (even if empty) always leads to this error:

422
The change you wanted was rejected.
Maybe you tried to change something you didn't have access to.

In /var/log/gitlab/gitlab-rails/production.log I see a long stack trace:

Started POST "/users/sign_in" for 188.9.177.98 at 2014-11-08 15:40:59 +0100
Processing by SessionsController#create as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"++YH/fm12Ao7yNJubHA7J+ly24HY29l97FVqUIO9q8o=", "user"=>{"login"=>"fooo", "password"=>"[FILTERED]", "remember_me"=>"0"}}
Can't verify CSRF token authenticity
Completed 422 Unprocessable Entity in 3ms

ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken):
  actionpack (4.1.1) lib/action_controller/metal/request_forgery_protection.rb:176:in `handle_unverified_request'
  actionpack (4.1.1) lib/action_controller/metal/request_forgery_protection.rb:202:in `handle_unverified_request'
  devise (3.2.4) lib/devise/controllers/helpers.rb:182:in `handle_unverified_request'
  actionpack (4.1.1) lib/action_controller/metal/request_forgery_protection.rb:197:in `verify_authenticity_token'
  activesupport (4.1.1) lib/active_support/callbacks.rb:424:in `block in make_lambda'
  activesupport (4.1.1) lib/active_support/callbacks.rb:160:in `call'
  activesupport (4.1.1) lib/active_support/callbacks.rb:160:in `block in halting'
  activesupport (4.1.1) lib/active_support/callbacks.rb:166:in `call'
.......

I have no clue what's happening or what I could do now... Please help.

Assignee
Assign to
Time tracking