relative_url instructions lacks gitaly config changes

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

I've tried to setup gitlab installed from current ArchLinux packages:

  • gitlab 17.3.1-1
  • gitlab-gitaly 17.3.1-1
  • gitlab-shell 3:14.39.0-1

.. and configure it under relative_url. I followed ArchWiki instructions and then made changes described in relative_url instructions.

I've setup my first empty project and I was unable to push any commit via ssh or https. It always ends with unclear message "Internal API error (404)"

Enumerating objects: 33558, done.
Counting objects: 100% (33558/33558), done.
Delta compression using up to 8 threads
Compressing objects: 100% (8908/8908), done.
Writing objects: 100% (33558/33558), 509.84 MiB | 46.73 MiB/s, done.
Total 33558 (delta 26528), reused 30840 (delta 24311), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (26528/26528), done.
remote: GitLab: Internal API error (404)
To host.pl:repogroup/backend.git
 ! [remote rejected]   devel -> devel (pre-receive hook declined)
 ! [remote rejected]   master -> master (pre-receive hook declined)

In my case I had to update /etc/gitlab-gitaly/config.toml:

relative_url_root = '/gitlab'

After restarting gitlab-gitaly service I was able to push my commits to empty repositories.

I suggest adding config.toml changes to relative_url instructions.

Edited Sep 26, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading