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

Closed
Open
Created Apr 08, 2013 by Administrator@rootOwner

The plain HTTP request was sent to HTTPS port

Created by: jasperla

My gitlab webfrontend works fine over HTTPS (https://gitlab.example.org:3000), however, I'm having issues getting gitlab-shell to play nice with it.

I've set "ssl on" in my nginx configuration, and the server listens on port 3000.

gitlab-shell/bin/check returns: Check GitLab API access: FAILED. code: 400 Which does show up in the nginx logs: 192.168.122.120 - - [08/Apr/2013:20:11:34 +0200] "GET /api/v3/internal/check HTTP/1.1" 400 271 "-" "Ruby"

But I cannot see it ending up in production.log, even with my gitlab-shell/config.yml: gitlab_url: "https://192.168.122.120:3000" I can visit that URL with w3m and I get shown the regular login screen.

A second issue is when I clone from a remote host I get:

tmp {1432} ssh [email protected] -p 2222 PTY allocation request failed on channel 1 (JSON::ParserError)1.9.1/json/common.rb:148:in `parse': 743: unexpected token at '

400 The plain HTTP request was sent to HTTPS port

400 Bad Request

The plain HTTP request was sent to HTTPS port
nginx/0.7.67 ' from /usr/local/lib/ruby/1.9.1/json/common.rb:148:in`parse' from /home/git/gitlab-shell/lib/gitlab_net.rb:24:in `discover' from /home/git/gitlab-shell/lib/gitlab_shell.rb:28:in`exec' from /home/git/gitlab-shell/bin/gitlab-shell:16:in `'

Any ideas what's going on, or if there's a common cause?

Assignee
Assign to
Time tracking