Skip to content
This repository has been archived by the owner on Nov 22, 2022. It is now read-only.

Cannot Login to Self-hosted instance in the subdirectory #988

Open
nison-jp opened this issue Apr 12, 2022 · 1 comment
Open

Cannot Login to Self-hosted instance in the subdirectory #988

nison-jp opened this issue Apr 12, 2022 · 1 comment
Labels
bug Something isn't working stale

Comments

@nison-jp
Copy link

nison-jp commented Apr 12, 2022

Description

  • I'm using a GitLab self-hosted instance, which is located in the sub directory, like https://example.com/gitlab/.
  • At command glab auth login, asking hostname, glab only accepts domain name.
  • SSH connection is not available for that instance.

Expected Behavior vs Actual Behavior

  • Expected behavior:
    • accepts subdirectory
  • Actual behavior:
    • only accepts domain name

Possible Fix

  • SSH protocol only requires hostname, so glab auth login should ask protocol at first, and if user choose HTTPS, they should accept subdir.

Steps to Reproduce

1.glab auth login
2. Prompt "? GitLab hostname: "
3. Enter "example.com/gitlab/"
4. Error Shown: X Sorry, your reply was invalid: invalid hostname: "example.com/gitlab/"

Logs

nothing

Your Environment

  • Version used (Run glab --version): glab version 1.22.0 (2022-01-10)
  • Operating System and version:
    • /etc/os-release
    NAME="Ubuntu"
    VERSION="20.04.4 LTS (Focal Fossa)"
    ID=ubuntu
    ID_LIKE=debian
    PRETTY_NAME="Ubuntu 20.04.4 LTS"
    VERSION_ID="20.04"
    HOME_URL="https://www.ubuntu.com/"
    SUPPORT_URL="https://help.ubuntu.com/"
    BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
    PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
    VERSION_CODENAME=focal
    UBUNTU_CODENAME=focal
    
    • uname -rsv: Linux 5.10.16.3-microsoft-standard-WSL2 #1 SMP Fri Apr 2 22:23:49 UTC 2021
@nison-jp nison-jp added the bug Something isn't working label Apr 12, 2022
@clemsbot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had recent activity. We haven't had the time to address it yet, but we want to keep it open. This message is just a reminder for us to help triage issues.

@clemsbot clemsbot added the stale label May 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

2 participants