Your software
My Mautic version is: 5.1.1
My PHP version is: 8.1.3
My Database type and version is: mysql - 8.0.39-0ubuntu0.24.04.2
Hi Mautic community,
I hope you’re all doing well! I’m experiencing an issue with Mautic tracking on my website, and I was hoping someone could help me out.
My problem is:
I’ve added the Mautic tracking script to my website (www.todosobreautos.com), but I’m not seeing any visitors reflected in the Mautic dashboard. Additionally, when I trigger an event, the response shows ‘success: 0’.
These errors are showing in the log:
There aren’t any specific errors logged related to this issue, but it seems like the tracking isn’t working as expected.
Steps I have tried to fix the problem:
Double-checked the tracking script implementation.
Cleared the Mautic cache and my browser cache.
Tested with different browsers.
If anyone has encountered a similar issue or has suggestions on what else I can try, I would greatly appreciate your help!
Thanks for pointing that out. I had already checked that the mtc.js file was available. When I initially accessed it, I also encountered the 500 error, but after refreshing, the file loaded properly, and it seems to be accessible again.
I’m currently reviewing the logs to understand what might have caused the intermission. Do you have any suggestions on what could trigger this intermittent behavior?
I’ve attached a screenshot of how I’m seeing the file and the request for the event, for reference.
Hmm, let me try to recap where you are:
a) it is working now (after you trying twice)
b) you are trying to figure out the reason
right?
What you need to do is look at the Mautic log on your server in <mautic home>/var/logs/ (you can also that through the UI) for entries that match the point in time. They will probably flagged ERROR or CRITICAL.
Just wanted to update on my previous issue. After trying several troubleshooting steps, I finally managed to resolve the error by simply restarting the server. It seems like there might have been some lingering processes or a configuration that needed a reset.
If anyone else encounters a similar issue, a quick server restart might be worth a shot. Thanks to everyone who provided suggestions!
