Skip to content

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

@gwen-lg

Description

@gwen-lg

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions