Open lkroll opened 9 months ago
Hi @lkroll. Thanks for letting us know.
I guess the problem is, that the log importer sends the token auth within a GET request.
If you are familiar with python and have some time to work on the required changes, feel free to contribute a pull request.
I'm unable to promise if we will be able to work on this soon.
In the meantime using a token that is not configured as secure only
should still work as expected.
@lkroll Thank you, that was exactly the problem I was facing and wasted hours with it. Creating a new token which is not secure solved the problem.
Maybe we just need to add a note in the documentation to use only tokens created without the "Secure token" option?
When creating a new auth token with the default and recommended "secure only" option, the import_logs.py script does not work correctly.
It appears to work just fine, but after a couple of seconds it will report "500 Internel Server Error", because the IP is being blocked by Matomo because of too many failed login attempts.
Whitelisting the IP in Matomo "fixes" the issue and the script finishes with no errors, but the logs are not imported.
Testing the same import with a new auth token, leaving the "secure only" option unchecked, results in a working import.
Here is the ouput with the "secure only" token (not working):
And without this option (working):
The script should return an error and should not display that requests were successfully imported.