Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File for Fail2ban is always empty, so seems useless #174

Open
gwen-lg opened this issue Nov 25, 2023 · 0 comments
Open

File for Fail2ban is always empty, so seems useless #174

gwen-lg opened this issue Nov 25, 2023 · 0 comments

Comments

@gwen-lg
Copy link

gwen-lg commented Nov 25, 2023

Describe the bug

The file indicated for fail2ban is never filled, so it as no impact.
"/var/log/${domain}-access.log"

Context

  • Hardware: All
  • YunoHost version: 11.2.6
  • I have access to my server: whatever
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
  • Using, or trying to install package version/branch: 1.22.1~ynh1

Expected behavior

The file indicated in fail2ban conf should be the same than the file indicated in corresponding ngnix conf ?
And in case of installation in subfolder of a domain, it's seems than there is no dedicated access log file, and the one of the domain should be used. So there is no need of dedicated fail2ban conf when installed in subfolder, only when installed in subdomain.

Note: At symptomof somthing is weird, the path of the file is linked to domain, but the configuration is linked to app.

@gwen-lg gwen-lg mentioned this issue Nov 28, 2023
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant