You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Piwik on a webserver in an internal network that requires an HTTP proxy to reach the internet for outgoing requests (i.e. DMOZ data). So I configured the [proxy] settings which are working fine.
The problem I'm facing the the fact, that the Piwik console uses these proxy settings also for archive jobs ("core:archive"). This results in an unnecessary loop, because the console doesn't try to work on the local host anymore. Instead it uses the proxy which then tries to connect back to the local host.
I've created a new [proxy] option called "excludes" which accepts a whitespace-separated list of hosts that should be accessed directly and added my local Piwik hostname to it.
These are the modifications I did:
"config/config.inc.php":
[proxy]
excludes = "myhostname.xy"; space-separated list of hosts
Would that be a proper fix for my problem?
It seems to work fine, but I'm not sure if this is sufficient or if this creates negative side-effects.
Would it be possible to add this fix (or an optimized version) to one of the next Piwik releases?
Thanks!
Thomas
The text was updated successfully, but these errors were encountered:
Hi there, maybe another solution could be to "ignore" the proxy settings when attempting to contact a hostname where this hostname is found within the trusted_hosts array in config file?
mattab
added
Bug
For errors / faults / flaws / inconsistencies etc.
duplicate
For issues that already existed in our issue tracker and were reported previously.
labels
Dec 1, 2014
Hi!
I'm using Piwik on a webserver in an internal network that requires an HTTP proxy to reach the internet for outgoing requests (i.e. DMOZ data). So I configured the [proxy] settings which are working fine.
The problem I'm facing the the fact, that the Piwik console uses these proxy settings also for archive jobs ("core:archive"). This results in an unnecessary loop, because the console doesn't try to work on the local host anymore. Instead it uses the proxy which then tries to connect back to the local host.
I've created a new [proxy] option called "excludes" which accepts a whitespace-separated list of hosts that should be accessed directly and added my local Piwik hostname to it.
These are the modifications I did:
"config/config.inc.php":
"core/Http.php":
Would that be a proper fix for my problem?
It seems to work fine, but I'm not sure if this is sufficient or if this creates negative side-effects.
Would it be possible to add this fix (or an optimized version) to one of the next Piwik releases?
Thanks!
Thomas
The text was updated successfully, but these errors were encountered: