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 started encountering problems where the console core:archive cron job was failing to run. The curl calls that are spawned were failing with 302 forbidden.
I don't have root access to the server my installation runs on, so I asked my hosting provider to check the mod_security logs. They found that a WAF rule was being tripped because the calling IP was showing as 0.0.0.0, and they were blocking requests from there to prevent IP-spoofing abuse.
I've not been able to learn my way around Matomo's source code, so I thought I'd report it here for others to comment: Surely, a localhost originating curl call should come through from 127.0.0.1. Is this something Matomo manually overrides, or if not where does it come from?
TIA.
The text was updated successfully, but these errors were encountered:
I started encountering problems where the console core:archive cron job was failing to run. The curl calls that are spawned were failing with 302 forbidden.
I don't have root access to the server my installation runs on, so I asked my hosting provider to check the mod_security logs. They found that a WAF rule was being tripped because the calling IP was showing as 0.0.0.0, and they were blocking requests from there to prevent IP-spoofing abuse.
I've not been able to learn my way around Matomo's source code, so I thought I'd report it here for others to comment: Surely, a localhost originating curl call should come through from 127.0.0.1. Is this something Matomo manually overrides, or if not where does it come from?
TIA.
The text was updated successfully, but these errors were encountered: