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
URL parameter for core:archive console command is ignored #8316
Comments
Hi @astehlik can you try |
Fyi: a workaround to this issue is to make sure your system supports managing Processes via CLI, ie. you need to:
|
This was also (indirectly) reported in the forums: http://forum.piwik.org/read.php?2,128367 |
It was also reported in http://forum.piwik.org/read.php?2,128384 @diosmosis since many users report this issue as blocking for them to run the cron, could we restore this feature in 2.14.2 and not have to wait 2.15.0? |
… that do not use systems that support CLI archiving.
Fixes #8316, re-add core:archive URL override functionality for usersthat do not use systems that support CLI archiving.
I had a really strange issue today and it occured since the update to 2.14.0.
I'm using the command line interface for archiving:
During that call I got an error, because the script tried to use the IP address to access the Piwik Server which does not work because there is no virtual host entry for the IP.
I finally managed to figure out that there was in invalid URL written to
piwikUrl
setting which is used for making API calls.I also managed to figure out where the IP address came from: Piwik was accessible from a host that was not added to the trusted hosts setting. Therefore the hostname is read from the
SERVER_ADDR
variable which contained the IP address instead ofHTTP_HOST
which contained the actual hostname.I see two problems here:
1. URL parameter is ignored
The parameter passed to the console command
--url
is totally ignored when archiving is run. I would expect Piwik to use that parameter instead of the value that is stored in thepiwikUrl
setting to make API calls.2. Trusted host setting is bypassed
When a
HTTP_HOST
header is provided and the host is not trusted there should be no fallback toSERVER_ADDR
. Only when theHTTP_HOST
is empty it should be possible to fallback toSERVER_ADDR
.I hope this makes sense to you :)
The text was updated successfully, but these errors were encountered: