request for stylesheets get redirected to sign_in page on "Fedora 31"
Summary
After upgrading from "Fedora Core 29" to "Fedora Core 31" all requests to access a CSS stylesheet are redirected to the login page.
The same version of Gitlab (12.6.0) worked fine before on my "Fedora Core 29" system.
Steps to reproduce
When displaying the login page itself is shown without applying any stylesheet (see screenshot-1.png and screenshot-2.png).
As soon as I log in, I get redirected to "images/touch-icon-ipad-retina.png" which is inaccessible, so I get a 404 page (see screenshot-3.png and screenshot-4.png).
After going back twice I finally reach the "regular" page showing me my projects, but again, stylesheets are not applied since none of the links (e.g. http://myserver.mydomain.de/stylesheets/application.css) is accessible (see screenshot-5.png and screenshot-6.png). The file application.css itself is in sidekiq-5.2.7/web/assets/stylesheets/application.css.
Example Project
Sorry, this isn't possible.
What is the current bug behavior?
As mentioned in the "Steps to reproduce" section, stylesheets can't be downloaded successfully (other assets are affected as well).
What is the expected correct behavior?
Successfully downloading and applying all resources.
Relevant logs and/or screenshots
Screenshots have been attached, if you need any logs, I can provide them as well, just tell me what you need.
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Current User: git Using RVM: no Ruby Version: 2.6.3p62 Gem Version: 2.7.9 Bundler Version:1.17.3 Rake Version: 12.3.3 Redis Version: 3.2.12 Git Version: 2.24.1 Sidekiq Version:5.2.7 Go Version: unknownGitLab information Version: 12.6.0-ee Revision: fc376e40baf Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 9.6.14 URL: http://gitlabtest.ad.meelogic.com HTTP Clone URL: http://gitlabtest.ad.meelogic.com/some-group/some-project.git SSH Clone URL: git@gitlabtest.ad.meelogic.com:some-group/some-project.git Using LDAP: no Using Omniauth: yes Omniauth Providers:
GitLab Shell Version: 10.3.0 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab subtasks ...Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 10.3.0 ? ... OK (10.3.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 4/2 ... yes 4/3 ... yes 4/15 ... yes 3/16 ... yes 15/19 ... yes 4/20 ... yes 15/21 ... yes 4/22 ... yes 4/23 ... yes 4/24 ... yes 18/25 ... yes 18/26 ... yes 20/27 ... yes 20/28 ... yes 20/29 ... yes 20/30 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.5.3 ? ... yes (2.6.3) Git version >= 2.22.0 ? ... yes (2.24.1) Git user has default SSH configuration? ... yes Active users: ... 10 Is authorized keys file accessible? ... yes
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)





