html artifact not found on pages

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

Summary

Since the update to GitLab 12.4 (which enables online view of html artifacts) we can not view them anymore.

What is the current bug behavior?

In a project with enabled (and working) gitlab pages the artifacts are linked to a gitlab page.

Screenshot_2019-11-13_at_11.17.23 image

But if we try to open the file we receive a 404 from the gitlab pages server. The url is pointing to https://our-pages-server.com/-/example-project/-/jobs/1178214/artifacts/logs/test.log

I've looked into different logs but could not find out what is the issue since normal pages do work.

What is the expected correct behavior?

The file should open

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:		Ubuntu 18.04
Proxy:		no
Current User:	git
Using RVM:	no
Ruby Version:	2.6.5p114
Gem Version:	3.0.3
Bundler Version:1.17.3
Rake Version:	12.3.3
Redis Version:	4.0.9
Git Version:	2.24.0
Sidekiq Version:5.2.7
Go Version:	go1.13.4 linux/amd64

GitLab information
Version:	12.4.2-ee
Revision:	5fee6f7b0b8
Directory:	/srv/git/gitlab
DB Adapter:	PostgreSQL
DB Version:	9.5.19
URL:		https://xxx
HTTP Clone URL:	https://xxx/some-group/some-project.git
SSH Clone URL:	ssh://git@xxx:222/some-group/some-project.git
Elasticsearch:	yes
Geo:		no
Using LDAP:	yes
Using Omniauth:	yes
Omniauth Providers:


GitLab Shell
Version:	10.2.0
Repository storage paths:
  • default: /srv/git/repositories GitLab Shell path: /srv/git/gitlab-shell Git: /usr/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.2.0 ? ... OK (10.2.0)
Running /srv/git/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: ... Checking Reply by email ...


IMAP server credentials are correct? ... yes
Init.d configured correctly? ... yes
MailRoom running? ... yes


Checking Reply by email ... Finished


Checking Incoming Email ... Finished


Checking LDAP ...


LDAP: ... Server: ldapmain
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
User output sanitized. Found 100 users of 100 limit.


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? ... yes
Init script up-to-date? ... yes
Projects have namespace: ...yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.5)
Git version >= 2.22.0 ? ... yes (2.24.0)
Git user has default SSH configuration? ... yes
Active users: ... 126
Is authorized keys file accessible? ... yes
Elasticsearch version 5.6 - 6.x? ... yes (6.5.1)
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)

Edited by 🤖 GitLab Bot 🤖