Url redirection on runner creation/view ignores port
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
I'm using Gitlab 16.2 in a self-hosted docker container. When trying to create a new runner, or viewing an already created runner, I am redirected to a url that disregards the port where the web interface is hosted.
I'm accessing the web interface through port 8080, which is mapped to port 80 on the container.
So, for instance, if I'm on the runner creation page (http://192.168.18.62:8080/admin/runners/new), when I click on the "create runner" button I'm redirected to this url: http ://192.168.18.62/admin/runners/7/register?platform=linux (notice the missing port).
For now I'm managing to get around this issue by manually inserting the port in the url, this being the only way I can see the newly created runner's token.
The same issue occurs on the runners admin page (http://192.168.18.62:8080/admin/runners). When I try to click on the "edit" button of any of the runners, I am redirected to a portless (and therefore non-existent) url.
Something I've already tried, after googling some possible solutions, was adding the port to the "external_url" variable of the gitlab.rb file (http://192.168.18.62:8080), and of course, also changing the port mapping of the container (to 8080:8080). But after doing that I just completely lost access to the web interface.