We have a few links to CI artifacts in our READMEs and project badges, so that it's easy to get to generated documentation and reports. These links are in this sort of format:

https://gitlab.com/mygroup/myproject/-/jobs/artifacts/main/file/dir1/dir2/dir3/index.html?job=build

When following one of these links, GitLab serves a page that says "You are being redirected away from GitLab" and then it has a link to the actual artifact hosted on GitLab pages, like:

https://mygroup.gitlab.io/-/myproject/-/jobs/1234567890/artifacts/dir1/dir2/dir3/index.html

I seem to remember that these "redirect" pages used to actually redirect to the latter address after a second or two, but it seems that they now require that you click on the link.

Am I misremembering the old behavior? Is there some way to get that behavior? Does anyone else find it kind of annoying having to always click on that second link?

Hey guys,

I'm working on a migration of our Gitlab CE instance from a docker compose environment to a dedicated EC2 Runner and Server.

I've got everything working so for except Gitlab Pages. I've followed the documentation here: https://docs.gitlab.com/ee/administration/pages/

I've created the following DNS records.

A record for Gitlab git.dev.company.cloud

A record for Gitlab Pages gitdocs.dev.company.cloud

A record for wildcard *.gitdocs.dev.company.cloud

The omnibus configuration file contains: pages_external_url 'http://gitdocs.dev.company.cloud'

I navigate to the pages section of a project and click on the URL. A redirect begins, but instead of sending me to pages it sends me to my user page and displays:

An error has occurred
The redirect URI included is not valid.

The NGINX logs for pages show a 302 redirect, but that is about it...

Any help would be much appreciated!!

Hi all,

I'm having trouble with my Gitlab (self-hosted) working after an upgrade. I'm relatively confident that it isn't my reverse proxy.

My setup is as follows:

Cloudflare -> Reverse Proxy (separate VM) -> GitLab (Separate. VM)

My Nginx(reverse proxy) config is as follows:

server {
    # bind domain
    server_name subdomain.domain.tld;
    location / {
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass  http://192.168.1.91;
    }
    # logs
    access_log /var/log/nginx/gitlab_access.log;
    error_log /var/log/nginx/gitlab_error.log;

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/subdomain.domain.tld/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/subdomain.domain.tld/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = subdomain.domain.tld) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    listen 80;
    server_name subdomain.domain.tld;
    return 404; # managed by Certbot

}

Problem

Whenever I go to subdomain.domain.tld i am redirected to domain.tld

Everything was working before I upgraded - I am wondering, is there a command I need to run to get it up again?

Gitlab appears to be running, and no firewall rules blocking