Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

logo.svg not found #12623

Closed
courtens opened this issue Mar 17, 2018 · 5 comments
Closed

logo.svg not found #12623

courtens opened this issue Mar 17, 2018 · 5 comments
Labels
answered For when a question was asked and we referred to forum or answered it.

Comments

@courtens
Copy link

courtens commented Mar 17, 2018

OK - this is an old issue (#11765), but here it is again.

@halfer
Copy link

halfer commented Mar 18, 2018

I believe the other bug was fixed, and my own experience is that the issue went away. Is this a new occurrence of the same bug?

@courtens
Copy link
Author

it wasn't fixed (it never went away.) I gave up on bugging for it...

@mattab
Copy link
Member

mattab commented Mar 28, 2018

Hi @courtens

Is your matomo installed behind a proxy and in a sub-path? If so, see the new FAQ section:

important

in https://matomo.org/faq/how-to-install/faq_98/

@lindsaymacvean
Copy link

We are experiencing a similar issue. We have a docker cluster, Using varnish/apache with matomo in a subdirectory /analytics/ route. We have set the HTTP_X_FORWARDED_URI and the proxy_uri_header=1 and we can see some urls have rewritten. However some assets do not get rewritten.

<script type="text/javascript" src="libs/bower_components/jquery-placeholder/jquery.placeholder.js"></script>

We since realised that the obvious default behaviour of the browser is to make calls to the url base (not including the directory) unless there is an extra / at the end of our base url/directory/ in the varnish config so that the browser knows its a directory and not a file.

On top of following the steps in the above FAQ, try adding a / to the end of your directory wherever you have configured the base route to matomo either in varnish or apache.

@Findus23 Findus23 added the Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. label May 24, 2020
tsteur added a commit that referenced this issue Aug 25, 2020
refs matomo-org/matomo-for-wordpress#335 and #12623

This way it isn't needed to configure proxy headers for the real time map.
sgiehl pushed a commit that referenced this issue Aug 25, 2020
refs matomo-org/matomo-for-wordpress#335 and #12623

This way it isn't needed to configure proxy headers for the real time map.
@sgiehl
Copy link
Member

sgiehl commented Nov 9, 2022

should have been fixed with #16341
If anyone still has a similar issue, feel free to create a new report. Thanks.

@sgiehl sgiehl closed this as completed Nov 9, 2022
@sgiehl sgiehl added answered For when a question was asked and we referred to forum or answered it. and removed Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. labels Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Development

No branches or pull requests

6 participants