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

Closed
Open
Created Jan 22, 2014 by Administrator@rootOwner

WebHook returns 500 when running Test

Created by: mchineboy

The error page occurs after the "Test" button is clicked. The only relevant log entry is in gitlab/logs/production.log:

--snip--
Started GET "/redacted/redacted/hooks/4/test" for 127.0.0.1 at 2014-01-19 13:48:33 -0800
Processing by Projects::HooksController#test as HTML
  Parameters: {"project_id"=>"redacted/redacted", "id"=>"4"}
Completed 500 Internal Server Error in 78ms

EOFError (end of file reached):
  app/models/web_hook.rb:31:in `execute'
  app/contexts/test_hook_context.rb:5:in `execute'
  app/controllers/projects/hooks_controller.rb:27:in `test'
  app/controllers/application_controller.rb:57:in `set_current_user_for_thread'
--snip--

The url is a simple: http://sever:8001/

The remote server never logs any requests or attempts at a request. Using netcat shows that the remote server is accessible on the correct name and port. To be sure, we've tested with a raw IP address as well.

Assignee
Assign to
Time tracking