fire
fire
Had the same problem. See https://github.com/brush701/keechallenge/issues/36#issuecomment-455229141 for the solution.
This https://github.com/thomas-maurice/ansible-role-gitea/blob/ed984bb95a5e5d00ea911c0efb5212d02613cfdb/templates/fail2ban/filter.conf.j2#L3 should be this `failregex = .*(Failed authentication attempt|invalid credentials|Attempted access of unknown user).* from ` according to https://docs.gitea.io/en-us/fail2ban-setup/ Just made a PR to adopt this #99
To clarify: cryptic because there is not a single error code or reasonable error message to start debugging from. The only information you get is from git: ``` fatal: Could...
Did you had time to review the change, yet?
Just noticed I forgot the second part of the commit. Sorry for that. I've added a when statement to only activate the task when the user DOESN'T want to use...
Same here, except protocoll=h2
I can confirm @serioustk, thanks btw In my case the problem was also related to non ascii / unicode chars in the password. I was able to bypass the problem...
Any update yet? Using ocr and Sumatra together is no fun at the moment.