Wp-piwik not tracking when using proxy

Hi,

if your issue is similar than the other one, can you try to answer the questions mension there? Maybe this will give a hint why your visitors aren’t tracked:

If the ID is valid and the JS is loaded if you open the mentioned URL (the leading // is correct), please continue with these steps:

• Does your Piwik setup use the same protocol as your blog does? E.g., if your blog is using https://example.com, Piwik should also be available using https://…mypiwik… and vice versa. If your blog offers both protocols, Piwik should also support both. Otherwise, you can force Piwik to use a specific protocol inside WP-Piwik’s expert settings. (It will replace the // by https:// or https://.)
• Please also check, if any JavaScript errors appear on your site. See https://codex.www.ads-software.com/Using_Your_Browser_to_Diagnose_JavaScript_Errors for further instructions.
• If everything still looks fine, please contact the Piwik community at https://forum.piwik.org/ – it looks like WP-Piwik is doing well, but the tracking does not work, anyway.

https://www.ads-software.com/support/topic/hide-url-of-self-hosted-piwik

If the ID is valid and the JS is loaded if you open the mentioned URL (the leading // is correct), please continue with these steps:

Yes I didn’t want to hijack that thread though…

Does your Piwik setup use the same protocol as your blog does? E.g., if your blog is using https://example.com, Piwik should also be available using https://…mypiwik… and vice versa. If your blog offers both protocols, Piwik should also support both. Otherwise, you can force Piwik to use a specific protocol inside WP-Piwik’s expert settings. (It will replace the // by https:// or https://.)

Yes I have tested with multiple sites always the same result…

Please also check, if any JavaScript errors appear on your site. See https://codex.www.ads-software.com/Using_Your_Browser_to_Diagnose_JavaScript_Errors for further instructions.

There are no errors

If everything still looks fine, please contact the Piwik community at https://forum.piwik.org/ – it looks like WP-Piwik is doing well, but the tracking does not work, anyway.

No unless I can get support for WP-Piwik there ?
I am very sure WP-Piwik is the issue, I tried normal mode in WP-Piwik and it works, Proxy mode in WP-Piwik doesn’t.

I have multiple sites tracking just fine using proxy done manually…

No, you won’t get support for WP-Piwik there, but for the proxy script. Looking at the given information, the proxy code is embedded in a correct way and no JavaScript errors occure (btw. did you just try to open the URL used by the tracking code? Is the Piwik JS code shown as expected?).

WP-Piwik uses Piwik’s own proxy code and “injects” its settings. Of course, there can be something wrong with this injection, but I don’t know how to check this or how to debug the Piwik tracking itself.

If you can figure out why the embedded code which does not cause any errors does not track, and there is something I have to change in WP-Piwik, it would be happy to fix this… But currently I have no idea what’s wrong in this specific case.

I did a bunch of trouble shooting and everything looked fine, I even replaced the code manually and it didn’t work (in the same directory)
inputting my tracking code manually using wp-piwik and replacing the proxy script with the one I’m using on other sites details in the php file rather than the config so i know it should work, but it didn’t…
I was thinking it was an issue getting the details from the DB but no since it can communicate with piwik and create a site profile just fine.

The script points to /wp-content/plugins/wp-piwik/proxy/piwik.php
when using the proxy it uses the php file rather than the JS since its hiding the code if it showed the JS it would reveal the main server address, no ?

I just don’t have the time to mess with it to fully find the issue at the moment, the only think i could think was some sort of permissions issue but I don’t think its that…

Because of the latest Piwik updates, I will have a look at the proxy code again. Maybe Piwik did some changes which I can transfer to WP-Piwik and which may help to solve this issue.