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
{{ message }}
Repository navigation
[Bug]: IA_SYSTEM_LOG_TIMEZONE is need when not using docker #1096
I have installed Intruder Alert in a server with Debian Stable (v.13) and all updates, so apache2: 2.4.67-1-deb13u3 and php: 8.4.21-1-deb13u1.
It is installed in the SO, no docker. I install it downloading the zip files from the releases page (now it is intruder-alert-v1.22.10.zip). I now have installed this 1.22.10 version.
Intruder Alert is working fine from some months. It worked well with the latter version 1.22.9, and now I install the newer 1.22.10 and I think that it works well too.
But now I realized that the ban dates and hours in the Intruder Alert "log" are not the same that the fail2ban logs... This is an example of one ban in fail2ban log:
2026-07-03 22:25:27,612 fail2ban.actions [773]: NOTICE [apache-modsecurity] Ban 179.43.168.58
And in the Intruder Alert interface, this ban was sown at 2026-07-04 00:25:27,612 (I not made a screenshot prior the fix, sorry).
I was searching in the bug reports, and find this: #482
So I add the setting IA_SYSTEM_LOG_TIMEZONE, and now it is working well, see the screenshot:
changed the title [-][Bug]: IA_SYSTEM_LOG_TIMEZONE is neded too in NO docker installations...[/-][+][Bug]: IA_SYSTEM_LOG_TIMEZONE is need when not using docker[/+]on Jul 6, 2026
This is an oversight on my part. When IA_SYSTEM_LOG_TIMEZONE is not given, Intruder Alert uses the timezone set in the PHP configuration, and I wrongly assumed it would match the timezone of system php is running on, which is not always the case.
Fixed in #1097 by making the environment variable mandatory.
Activity
[-][Bug]: IA_SYSTEM_LOG_TIMEZONE is neded too in NO docker installations...[/-][+][Bug]: IA_SYSTEM_LOG_TIMEZONE is need when not using docker[/+]VerifiedJoseph commentedon Jul 6, 2026
Thank you for bring this to my attention.
This is an oversight on my part. When
IA_SYSTEM_LOG_TIMEZONEis not given, Intruder Alert uses the timezone set in the PHP configuration, and I wrongly assumed it would match the timezone of system php is running on, which is not always the case.Fixed in #1097 by making the environment variable mandatory.
Config: Require IA_SYSTEM_LOG_TIMEZONE env (#1097)