Docs feedback: Troubleshooting GitLab Pages administration and other internal API issues (like IDE) due to Apache reverse proxy settings
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
I've been trying to set up gitlab pages, and the pages have worked but the links to artifacts have failed, even though OAuth has been successful. This turns out to be an issue in pages using the API due to character escape issues.
I've been using the page https://docs.gitlab.com/ee/administration/pages/troubleshooting.html which has been very helpful for finding the logs. All the logs would state is that the API is returning a 404 error, so I had to look at my reverse proxy logs to see the actual API call that was malformed.
I was able to finally figure out this and fix it by incorporating the very helpful content from: https://gitlab.com/gitlab-org/gitlab-recipes/-/blob/master/web-server/apache/gitlab-omnibus-ssl-apache24.conf
I recommend adding another section to the troubleshooting page for the case where pages works but artifacts does not. The issue I had likely only shows for those using an Apache Proxy. In my case I'm using it to route between many services across docker instances on a single webserver.
I also find that the web IDE is now working, so linking those Apache configs in other places may be useful for the occasional user who is using Apache rather than nginx.
For more context why I'm using Apache, it is because I figured out how to utilize its openIDC module with an Authentik instance, so I'm using it for many services and haven't spend the time to migrate to nginx.