Glab never hit my self hosted Gitlab
Checklist
$ glab --version
glab version 1.24.1 (2022-12-07)
$ uname -a
MINGW64_NT-10.0-19044 L000217 3.3.6-341.x86_64 2022-09-05 20:28 UTC x86_64 Msys
I also tryed in my gitlab-runner, in wsl, in a basic VM linux, and all finish with the same error
Summary
Glab never hit my self hosted Gitlab
Steps to reproduce
$ glab auth login choose to add your self hosted Gitlab, add all the input and try for example "glab api environments"
What is the current bug behavior?
When i try "glab api environments" Glab keeps trying to log into gitlab.com
What is the expected correct behavior?
The correct behavior should be a call on my self hosted Gitlab
Relevant logs and/or screenshots
$ glab auth login ? What GitLab instance do you want to log into? GitLab Self-hosted Instance ? GitLab hostname: Self-hosted-git
? GitLab hostname: Self-hosted-git ? API hostname: Self-hosted-git
- Logging into Self-hosted-git
Tip: you can generate a Personal Access Token here https://Self-hosted-git/-/profile/personal_access_tokens
The minimum required scopes are 'api' and 'write_repository'.
? Choose default git protocol HTTPS
? Authenticate Git with your GitLab credentials? Yes
? Choose host API protocol HTTPS
- glab config set -h Self-hosted-git git_protocol https ✓ Configured git protocol
- glab config set -h Self-hosted-git api_protocol https ✓ Configured API protocol ✓ Logged in as MY_USERNAME
$ glab api environments Get "https://gitlab.com/api/v4/environments": read tcp 172.18.201.140:61357->172.65.251.78:443: wsarecv: Une connexion existante a dû être fermée par l’hôte distant.
Possible fixes
I don't have a clue.