the author recommends changing the logback.xml file "
https://github.com/crazy-max/docker-fail2ban/tree/master/examples/jails/guacamole";
and output the log file from the container for fail2ban processing, but
I couldn’t do it, I don’t have enough rights, the guacamole container
starts without root rights
19.05.2022 04:30, Michael Jumper пишет:
On Mon, May 16, 2022 at 9:37 PM Golota S.V.
<[email protected]> wrote:
Hello!! I use docker version guacamole 1.4 since I organized access
through nginx proxy manager and attached to fail2ban from
crazy-max/docker-fail2ban everything is fine, but there are many
false
locks after authorization. there are recommendations to analyze
logs not
from nginx but from tomcat right from the container, I can’t
display the
logback.xml settings file from the container to correct and enable
logging, what do you recommend?
Can you clarify what it is you are trying to correct/enable? Logging
is always enabled within the "guacamole/guacamole" Docker image. The
logs should be visible directly within the Docker logs for the container.
- Mike
