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 and world map URLs use internal IP address that can not be reached #335
Comments
refs matomo-org/matomo-for-wordpress#335 and #12623 This way it isn't needed to configure proxy headers for the real time map.
Thanks for this issue @giladrom Similar as with the other issues I'm creating a new FAQ about this and this issue should be solvable by following the "Matomo URL" steps in https://matomo.org/faq/wordpress/how-do-i-make-matomo-for-wordpress-work-when-it-is-behind-a-cdn-or-proxy/ Let me know if this is clear and if that works? For the map itself I'm also working on a fix as part of matomo-org/matomo@475eb16 For the logo I need to see if/how this can be fixed. Does above FAQ help? |
refs matomo-org/matomo-for-wordpress#335 and #12623 This way it isn't needed to configure proxy headers for the real time map.
Issue resolved as of last update. |
Great @giladrom Did you add the entry to the config file for proxy client? Can you check which one you added for CloudFront then I would document this so it'll be easier for other users. |
Hi, I did not make any changes to resolve this issue; I assumed there was an automatic update by WordPress with a fix. |
When loading the dashboard, the logo URL is always returning a 404 since it is referenced using an internal IP that can not be reached:
https://172.26.5.151/wp-content/plugins/matomo/app/plugins/Morpheus/images/logo.svg?matomo
Also, when trying to load the real-time map, the page doesn't load and the following 404's are received:
https://172.26.5.151/wp-content/plugins/matomo/app/plugins/UserCountryMap/svg/world.svg
https://172.26.5.151/wp-content/plugins/matomo/app/plugins/Morpheus/images/logo.svg?matomo
The text was updated successfully, but these errors were encountered: