Missing .js file ERROR 404

[julianf19]

I am trying to run dejavu inside a docker container (swarm) running behind an Nginx.
on loading the page I get the title:

But nothing renders on the screen, And I get a few errors

I am using the latest version of dejavu
Tried with safari firefox and chrome...

If anyone has an idea of how to solve this.

[siddharthlatest]

@julianf19 Can you share the path of any one file that is showing a 404 abort error in your screenshot, minus the domain info? The docker container (latest version) works well, I'm wondering if there is any nginx related config issue over here.

[julianf19]

Here is the 2 things I could find.
I don't really get what "path" you mean.

I was thinking Nginx could also be the problem, but i do the same thing as usual so I don't get it, here is the default.conf

location /dejavu/ {
proxy_set_header Cookie "";
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header Host $host;

proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;

proxy_pass http://dejavu:1358/;
proxy_redirect off;

}

Or do you think it could be the WAF blocking something?

[siddharthlatest]

@julianf19 The path that shows up in the screenshot of your original image: https://user-images.githubusercontent.com/44298384/148044034-bc0cae03-d22e-4ab6-99cd-4837f84f1341.png.

Or do you think it could be the WAF blocking something?

It could be this too, you can tell this from Nginx logs or your WAF logs.

[julianf19]

Well that's the whole path you see there:
https://domain.name.be/common.9459595.css

[sshhsh]

Well that's the whole path you see there: https://domain.name.be/common.9459595.css

The problem is that your browser try to find https://domain.name.be/common.9459595.css.
But the actual file path is https://domain.name.be/dejavu/common.9459595.css.

This is the case because the static file in HTML is using absolute path instead of relative one. Maybe the next version can change to use relative paths.

[siddharthlatest]

@sshhsh This can be the case, if someone feels inclined to create a PR, we will have this change included in the next release.