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
https proxy call brakes logo.svg URL (also some strange redirect removing /piwik/ folder) and getting a "No input file specified." response. #11765
Comments
I'm Dockerising my Piwik install presently, and am getting the same. I use Apache in the host and in the guest. Here's the Apache config in the host:
This results in a broken logo URL of: That IP address is the internal IP of the container, accessible only to the host. I expect I can write a |
Could be a duplicate of:
The last one says it is resolved by #9145, but that sounds like a different issue. |
I've managed to work around it, by enabling the
then add this config to the vhost:
|
halfer, have you tried calling it over a SSL connection? For me - that is what is breaking (not working). Over a non-SSL connection it works, but I would like to use SSL connection. |
@courtens: my configuration presently is: SSL on the host, proxying to the container via plaintext. After adding the two lines above, the However my work has paused there. My live instance is running v2.17.x but my Piwik Docker build (pointing to the same database) contains 3.x, and as a result I get the database upgrade screen. I think my next step is to do a manual upgrade on live, and then I can play around with the containerised version to see if there are any problems. What specifically is still not working for you? I've seen reports of several things not working - logo, sparkline graphs, and some other things I think. I've only experienced the logo so far, and I think I've now fixed that. |
@halfer I picked to use the "logo not working" as post titles (issue 1 in the first post) because it was simple to document -- other things require more words, but they are all related (see issue 2 and 3 in first post for the other things that are not woring.) I have to note that if I proxy over a non secure connection (proxy server to the world) Piwik works just fine. Piwik is only acting up over a SSL connection (proxy server to the world over SSL) and internal (proxy server to server using port 8080.) |
(@courtens: It would be ideal to swap out your hash marks in your comment just now, they link to very old bugs of the same numbers). |
I've not been able to replicate item (2). Item (3) is also a problem for me, it's a JavaScript crash:
See if you get the same, in your browser console? Mine is from latest FF 54/Mint Linux. Edit: I have removed For the record they are:
|
I am getting a long list of JS errors
looking at the code it must be due to a I am still getting the logo error:
I have Piwik in a sub-directory, and somehow the code is dropping this. Is there a place in the config file where one can specify the sub-directory to prevent this? My config.ini.php file is set to (and I made sure that global.ini.php is set to the same)
|
@courtens I don't have any answers over and above my existing detail, as I'm not using subdirs myself. However the detail we have now both supplied may be helpful to devs wanting to repro the problem. In the meantime, consider using a subdomain instead of a subdir. I appreciate it is not ideal to have to make such a change, but it may get you started again in the short term. |
@halfer ..... the problem using sub-domains is that it requires a more expensive SSL certificate. Just using www cost less. |
@courtens: you can use Let's Encrypt to get as many certs as you need, free of charge, and automatically renewed, for as long as you want. |
Update regarding this issue: a new pull request was submitted by @user121216 in #12011 and addresses this issue by 1) requiring the web server to set the header -> if you could test and leave a comment here or on the PR that would be great? (and maybe also share what the apache config looks like to set this header). |
Hi everyone, Since #12011 was merged, we consider this issue fixed. Please check the FAQ here for more information: https://piwik.org/faq/how-to-install/faq_98/ in particular check the section Feedback welcome! @halfer currently the FAQ only explains how to configure the |
Seems like I have also run into this issue. I have this apache reverse proxy config:
This results in a header coming to piwik which looks like this: Given this in the config.ini.php |
Hi @mattab, I forget the exact details of my proxy woes, but we're several releases of Piwik on since I made my posts above, and my setup has been problem-free for months. I include below my current Apache config, lightly edited to remove domain-specific stuff, and with my old comments left in (logos and JS are now fine). The Docker container is at
(Looking at this, I would guess I have config missing in my non-SSL vhost, but since I don't use it, it has not been something I have needed to fix!). Let me know if any more info would be useful. |
@tobiasassmann: does my (SSL) vhost config above help? Edit: mine may have been another problem though - I am proxying a root domain to a root domain, whereas the |
Yes it should but you need to use at least piwik 3.2.1-b1, released yesterday, learn more: http://piwik.org/faq/how-to-update/faq_159/ |
OK - this is an old issue, but here is what needs fixing:
|
There are three issues I have, and they are all related to the proxy setup problem I am experiencing.
======
On the login page located here
https://www.mydomainname.com/piwik/
I get a broken logo image. The logo image is located on the server athttp://192.168.1.1:8080/plugins/Morpheus/images/logo.svg
. But somehow the proxy (or piwik) responds that the logo.svg file is located here:https://www.mydomainname.com/plugins/Morpheus/images/logo.svg
which is wrong, where in fact it should behttps://www.mydomainname.com/piwik/plugins/Morpheus/images/logo.svg
. Somehow/piwik/
gets dropped.======
Immediately after logging in I get a redirect to a page that prompts:
No input file specified.
(or a redirect tohttps://www.mydomainname.com/
instead ofhttps://www.mydomainname.com/piwik/
) It is only after clicking back on the browser that I get redirected to the piwik website. Somehow the piwik code truncates the piwik folder during the redirect right after a successful login (back to the root folder.) This redirect brakes the page.=====
The "All Websites" page is not working (not giving me any data), only the "Dashboard" page works. "Add a new website" goes to
https://www.mydomainname.com/?module=SitesManager&action=index&showaddsite=1&period=range&date=previous30&idSite=1
but it should go tohttps://www.mydomainname.com/piwik/?module=SitesManager&action=index&showaddsite=1&period=range&date=previous30&idSite=1
Same issue as issue 1 and 2, a redirect dropping the working folder I am in.
=== my setup ============
I am running Ubuntu, hosting VM (VirtualBox) Win10 serving:
Piwik 3.0.4 (running on IIS)
Apache 2.4 listening to :80 and :443
Apache proxy from
https://www.mydomainname.com/piwik/
tohttp://192.168.1.1:8080
IIS 10 is hosting Piwik on
http://192.168.1.1:8080
relevant parts of my httpd-ssl.conf file
my piwik global.ini.php file is set to:
I tried
host = 192.168.1.1;
port = 8080;
-- but it did not fix the issue.The text was updated successfully, but these errors were encountered: