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 }}
This repository has been archived by the owner on May 3, 2020. It is now read-only.
I just tried the dashboard, and i had a strange bug : when launching the webserver and going to localhost:5000, i get a :
UnicodeDecodeError
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 0: ordinal not in range(128)
I tracked down the problem to the variable status before the rendering of the homepage (line 32 of home.py), and i think it comes from the fact that on systemd OSs, the "service" command is translated to "systemctl" command; with systemctl, the output is this :
it has the little green led to indicate that the service is up, and that cannot be parsed by Jinja.
I will try to fix this problem and give a PR to make the fail2ban status checking more universal.
The text was updated successfully, but these errors were encountered:
Hi @nocternology, this tool was developed with Debian Wheezy (based on sysvinit) and wasn't tested with systemd.
Thanks and i'm waiting for your fix 👍 :)
Hi there,
I just tried the dashboard, and i had a strange bug : when launching the webserver and going to localhost:5000, i get a :
I tracked down the problem to the variable status before the rendering of the homepage (line 32 of home.py), and i think it comes from the fact that on systemd OSs, the "service" command is translated to "systemctl" command; with systemctl, the output is this :
it has the little green led to indicate that the service is up, and that cannot be parsed by Jinja.
I will try to fix this problem and give a PR to make the fail2ban status checking more universal.
The text was updated successfully, but these errors were encountered: