request_profiler | Rack middleware for profiling requests using ruby | Application Framework library

I have recently updated the GitLab version 11.11.8 to 13.2.6.

After the update, I am seeing an issue (500) while navigating to the group main, group detail or group member page. Other pages under the group work find.

here is log from production.log

I'm very new to GitLab and Ruby. Any comment is welcome.

For testing a command line tool against a Gitlab instance in Docker, I would like to login to Gitlab using username and password and grab the created session to authenticate my API requests.

Therefore I do the following:

1. curl the user login page with curl -i http://localhost:8080/users/sign_in -s
2. get me the _gitlab_session from the headers
3. get me the authenticity_token from the login form
4. send a second curl request with

I have restored Gitlab from a backup, now every time I try to access the runners webpage, I get a Internal Server error.

I have tried uninstalling all configured gitlab-runners and accessing it, the problem persists. Here is a trace from the gitlab-rails/production.log:

My GitLab is hosted on DO, and was working fine over the years. I have been updating it time to time and is on very latest release at the moment.

Few days back I have updated my other server where mattermost is hosted, and after the update integration stopped working. I suspected it mattermost is the reason as only that server is reinstalled but so far I am not able to make it work.

1. I have recreated the hook on mattermost and re-enabled them on gitlab - No luck

2. I tried slash commands and those are working. I can pull issue detail from mattermost using /repo issue show 123 and that is pulled in chat - so its working

3. I went to mattermost https://docs.mattermost.com/developer/webhooks-incoming.html for testing and I can confirm my web hooks are working.

   curl -i -X POST --data-urlencode 'payload={"text": "Hello, this is some text\nThis is more text. :tada:"}' http://domain.xyz:8065/hooks/zr7raaqojtgm7j4ormyzzoyz9h

4. at this point, it feels like mattermost side is working fine. so I went into gitlab instance and viewed its logs. I am not sure so here they are

With Gitlab (10.6.2) and Jenkins installed on local machine, and trying to auto build via gitlab's webhook, according to https://github.com/jenkinsci/gitlab-plugin/wiki/Setup-Example

But, when test push, gitlab get error:

500 Internal Server Error - URI::InvalidURIError

The detailed log in production.log is:

Started GET "/laiwan/laiwan-parent/hooks/2/test?trigger=push_events" for 127.0.0.1 at 2018-04-03 17:11:07 +0800 Processing by Projects::HooksController#test as HTML Parameters: {"trigger"=>"push_events", "namespace_id"=>"laiwan", "project_id"=>"laiwan-parent", "id"=>"2"} Completed 500 Internal Server Error in 27ms (ActiveRecord: 2.3ms)

URI::InvalidURIError (URI::InvalidURIError):
lib/gitlab/proxy_http_connection_adapter.rb:14:in connection'
app/services/web_hook_service.rb:73:inmake_request'
app/services/web_hook_service.rb:26:in execute'
app/models/hooks/web_hook.rb:10:inexecute'
app/services/test_hooks/base_service.rb:22:in block in execute'
app/services/test_hooks/base_service.rb:19:incatch'
app/services/test_hooks/base_service.rb:19:in execute'
app/controllers/projects/hooks_controller.rb:41:intest'
lib/gitlab/i18n.rb:50:in with_locale' lib/gitlab/i18n.rb:56:in with_user_locale' app/controllers/application_controller.rb:330:in set_locale' lib/gitlab/middleware/multipart.rb:95:incall'
lib/gitlab/request_profiler/middleware.rb:14:in call'
lib/gitlab/middleware/go.rb:17:incall'
lib/gitlab/etag_caching/middleware.rb:11:in call'
lib/gitlab/middleware/read_only/controller.rb:28:incall'
lib/gitlab/middleware/read_only.rb:16:in call'
lib/gitlab/request_context.rb:18:incall'
lib/gitlab/metrics/requests_rack_middleware.rb:27:in call'
lib/gitlab/middleware/release_env.rb:10:incall'

Gitlab webhook's url is http://localhost:8282/project/laiwan-parent, it's valid.

Seems someone asked similar issue on gitlab's issues page, but didn't get any respond yet: https://gitlab.com/gitlab-org/gitlab-ee/issues/5375

Any help?

I'm running GitLab 10.2.2 and Two Factor Authentication (2FA) doesn't work at all. I shortly migrated and upgraded the GitLab instance. I just copied the old config/secrets.yml with the base key to its place. But even if I don't I should be able to activate 2FA.

When I try to activate 2FA, the logs says:

I upgraded my Gitlab Server to 9.1 and now I am not able to create a new group or subgroup. I get:

I have successfully installed GitLab Community Edition 8.15.2 (omnibus) on my local ubuntu server 16.04 with apache2 (2.4), i can access it in browser and can perform all tasks. But when i try to execute task (like pushing project for first time or cloning project) using git bash or git gui, it does not perform the task e.g.