zpfhyj
(zpfhyj)
February 24, 2021, 10:53am
1
我按照官方文档进行了配置,并且在网站页面添加了javascript ,但是访问我的网站确一直没有收集到访问日志。查看matomo的nginx日志,有对应网站上的请求记录。但是在mysql的matomo_log_visited中没有任何信息。我在命令行执行/usr/bin/php72 /data/soft/matomo3/console core:archive --url=https://demo.com 输出如下内容:
INFO [2021-02-24 09:49:03] 17724 START
INFO [2021-02-24 09:49:03] 17724 Starting Matomo reports archiving…
INFO [2021-02-24 09:49:04] 17724 Start processing archives for site 1.
INFO [2021-02-24 09:49:04] 17724 Finished archiving for site 1, 0 API requests, Time elapsed: 0.156s [1 / 1 done]
INFO [2021-02-24 09:49:04] 17724 Done archiving!
Lukas
(Lukas Winkler)
February 24, 2021, 11:50am
2
Hi,
I’d recommend you to use https://developer.matomo.org/api-reference/tracking-api#debugging-the-tracker to find out why the requests are not stored (it returns a verbose log with the matomo.php request)
zpfhyj
(zpfhyj)
February 24, 2021, 2:24pm
3
Lukas
(Lukas Winkler)
February 24, 2021, 4:21pm
4
zpfhyj:
输出的日志我该怎么查询?
Check the network tab of your browsers developer tools and look at the output of the Matomo request.
Interestingly just this issue should have been fixed with 4.2:
opened 11:26PM - 27 Jan 21 UTC
closed 11:33PM - 04 Feb 21 UTC
Bug
Regression
In the browser developer console I see a warning linking to https://www.chromest… atus.com/feature/5629709824032768 anyone seen this before?
See https://www.chromium.org/Home/chromium-security/corb-for-developers for more information.
HTTP with 204 seems to work but 200 blocked. `send_image=0` is used so it should have sent an HTTP 204 header. Actually... this output happens because of bulk requests. The request with HTTP 200 was sent as a bulk request in this example.
![image](https://user-images.githubusercontent.com/273120/106067345-64755600-6163-11eb-88af-b99e08f601f6.png)
response headers:
![image](https://user-images.githubusercontent.com/273120/106067376-6fc88180-6163-11eb-9a50-5c648fb55b6b.png)
The console warning reads `Cross-Origin Read Blocking (CORB) blocked cross-origin response XYZ with MIME type application/json. See https://www.chromestatus.com/feature/5629709824032768 for more details.`
For a URL where this can be reproduced feel free to ping me privately. I'm not sure if the tracking request will be executed or if just the response is not loaded.
Goal of this issue is to make sure such requests are tracked and the warning is no longer shown.