Fresh Install of Piwik Fails

Support & Bugs
1

I continue to have problems with my piwik install so I thought the easy thing to do would be a fresh install with the old database. But even the fresh install wont complete and on the second page reports a 404 “GET request to piwik.php failed. Try whitelisting this URL from mod_security and HTTP Authentication.”

But I DONT HAVE mod_security installed! See the module list below. Running PHP 5.3.8

When I try to get past this, it just bails and you can even try by going here to this test install.

http://www.squamishspeaks.ca/piwik/

Compiled in modules:
core.c
mod_authn_file.c
mod_authn_default.c
mod_authz_host.c
mod_authz_groupfile.c
mod_authz_user.c
mod_authz_default.c
mod_auth_basic.c
mod_cache.c
mod_mem_cache.c
mod_include.c
mod_filter.c
mod_deflate.c
mod_log_config.c
mod_logio.c
mod_env.c
mod_expires.c
mod_headers.c
mod_ident.c
mod_unique_id.c
mod_setenvif.c
mod_version.c
mod_proxy.c
mod_proxy_connect.c
mod_proxy_ftp.c
mod_proxy_http.c
mod_proxy_scgi.c
mod_proxy_ajp.c
mod_proxy_balancer.c
mod_ssl.c
prefork.c
http_core.c
mod_mime.c
mod_status.c
mod_autoindex.c
mod_asis.c
mod_info.c
mod_suexec.c
mod_cgi.c
mod_negotiation.c
mod_dir.c
mod_actions.c
mod_userdir.c
mod_alias.c
mod_rewrite.c
mod_so.c

Loaded Modules:
core_module (static)
authn_file_module (static)
authn_default_module (static)
authz_host_module (static)
authz_groupfile_module (static)
authz_user_module (static)
authz_default_module (static)
auth_basic_module (static)
cache_module (static)
mem_cache_module (static)
include_module (static)
filter_module (static)
deflate_module (static)
log_config_module (static)
logio_module (static)
env_module (static)
expires_module (static)
headers_module (static)
ident_module (static)
unique_id_module (static)
setenvif_module (static)
version_module (static)
proxy_module (static)
proxy_connect_module (static)
proxy_ftp_module (static)
proxy_http_module (static)
proxy_scgi_module (static)
proxy_ajp_module (static)
proxy_balancer_module (static)
ssl_module (static)
mpm_prefork_module (static)
http_module (static)
mime_module (static)
status_module (static)
autoindex_module (static)
asis_module (static)
info_module (static)
suexec_module (static)
cgi_module (static)
negotiation_module (static)
dir_module (static)
actions_module (static)
userdir_module (static)
alias_module (static)
rewrite_module (static)
so_module (static)
bwlimited_module (shared)
suphp_module (shared)

2

http://www.squamishspeaks.ca/piwik/piwik.php?url=http://example.com fails with 404
but http://www.squamishspeaks.ca/piwik/piwik.php works

If it isn’t mod_security there is something else causing the first URL to fail most likely because the URL contains a URL (typical mod_security behavior, but this could maybe also be in a .htaccesss or something similar…?)

3

Thanks for the tip, that got me looking and I found the problem. I run a Wordpress site and used the Bulletproof Security module which creates an alternative, secure root .htaccess. Disabled this and piwik upgraded fine and all sections work!

Now I wonder if it’s still possible to use BPS and not break Piwik. Any suggestions as to what might be in the “secure” .htaccess that would break Piwik? Would it be reasonable to post it here?