Skip to content

glab returns 404 for everything on our self hosted instance

Checklist

  • I'm using the latest version of the extension (Run glab --version)
    • Extension version: no extensions
  • Operating system and version: WSL2 with Ubuntu LTS 22.04
  • Gitlab.com or self-managed instance? self-managed instance
  • GitLab version (if self-managed) 17.2.1
  • I have performed glab auth status to check for authentication issues

Summary

All glab commands result in 404s:

14:37 $ glab issue list
1 error occurred:
        * valid/project/path: GET https://selfhosted.com/api/v4/projects/valid/project/path: 404 {error: 404 Not Found}

Presumably, glab needs some feature or functionality enabled on self hosted GitLab that is disabled for ours. I could not find anything in the documentation about that, though.

Environment

  • OS: Linux 5.15.146.1-microsoft-standard-WSL2 x86_64
  • SHELL: /bin/bash
  • TERM: xterm-256color
  • GLAB: Current glab version: 1.45.0

Steps to reproduce

You can't, since it's specific to our self hosted instance.

What is the current bug behavior?

404s for every command.

What is the expected correct behavior?

No 404s for every command.

Possible fixes

Presumably activating something on our instance, but there is no documentation as to what.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information