Filter chain halted as :authenticate_user rendered or redirected


I have GitLab Community Edition 11.2.3 running under Apache on a Debian 9 server with a SSL certificate from LetsEncrypt. I have successfully created the first group and project within it and am trying to follow the instructions to upload an existing directory of source code.

When I try to run “git push -u origin master” from the development machine (git command line client v2.11.0) it asks for username and password then gives up with:

fatal: unable to access ‘’: The requested URL returned error: 500

Looking in the production.log I see the following reported:

Filter chain halted as :authenticate_user rendered or redirected
Completed 401 Unauthorized in 34ms (Views: 1.6ms | ActiveRecord: 4.9ms)

Completed 500 Internal Server Error in 247ms (ActiveRecord: 12.3ms)

Does anyone have any guidance on what I don’t have configured correctly?


Hmm… to preface, I don’t have experience with Gitlab; I stumbled on this thread while researching a “Filter chain halted as…” that I’ve run into while on my own projects. I’m assuming that Devise authentication is used with rails on the back end. From what I’ve gathered, when the controller associated with login/registry (usually the User controller) hits the
before_action :authenticate_user!
line, user authentication fails due to… something I’m still researching. It sounds like it has to do with headers that are lost somewhere along the line. I’ve heard that changing
before_action :authenticate_user!
before_filter :authenticate_user!, except: [:new, :create]
can resolve the issue, although this seems like it would just be a work-around. In my case at least, I think the header-loss may be connected with improper log out / my browser attempting to preserve user information upon closing my localhost tab / shutting off my server.

For more information on my sources, see: