-
But if I read https://docs.cloudron.io/security/ correctly:
"Be aware that Fail2Ban only works partially on Cloudron because most apps do not log failed authenticated attempts in a manner that Fail2Ban can parse (even if they did, Cloudron's reverse proxy hides the remote IP)."
This means it could be indeed outside traffic? When will outside traffic have an internal IP, because I also have public IPs in my log.
(Ask me about B2B marketing automation & low code business solutions, if thats interesting for you.)
-
G girish moved this topic from Feature Requests on
-
But if I read https://docs.cloudron.io/security/ correctly:
"Be aware that Fail2Ban only works partially on Cloudron because most apps do not log failed authenticated attempts in a manner that Fail2Ban can parse (even if they did, Cloudron's reverse proxy hides the remote IP)."
This means it could be indeed outside traffic? When will outside traffic have an internal IP, because I also have public IPs in my log.
@dsp76 that line is outdated, I will fix it. Cloudron apps do see the remote IP. In the past, they were hidden. But we got enough complaints that event logs inside apps were not useful anymore with internal private IPs. So, we have fixed up apps to have access to the Client/remote IP.
-
G girish marked this topic as a question on
-
G girish has marked this topic as solved on
This topic was forked from Automatic restart of an app (especially regarding websites) after it is down
girish
