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

Closed
Open
Created Mar 19, 2013 by Administrator@rootOwner

Login via https

Created by: matthiasg

It seems it is still not possible to login using https. When I navigate to https://myserver i am redirected to http://myserver/users/sign_in.

Once signed in, it remains https until i log out, which will redirect to http again.

Thus it does not seem to be possible to login using https.

The issue looks similar to https://github.com/gitlabhq/gitlabhq/issues/715 which was closed referring to added web configuration (AFAIK since been renamed from 'web' to 'gitlab'). But that configuration is applied and did not solve the Login problem.

Configuration: Using c90a98c5

gitlab.yml

 gitlab:
     host: myhost.com
     port: 443
     https: true

All projects correctly show https in the clone field.

Environment:

I have stud working on a firewall machine in front of the actual machine with nginx. From the perspective of gitlab this should not make a difference. The problem seems to be that unauthenticated requests are redirected absolutely to the http port.

Assignee
Assign to
Time tracking