• Support
  • The log file does not exist and cannot be created (Fail2Ban plugin)

aaPanel_Kern
i find this, are the access and error logs for my 3 sites, included the site that cant be added to fail2ban. What log you need?

    oitekablom
    Hello, now the logs of the three websites should correspond to the websites you created. Can you add the wrong website to fail2ban now?

      aaPanel_Kern No. 🙁 I cant add to fail2ban, i see the both logs of my website that cant be added. I dont understand. Only this website have error, the other 2 websites working with fail2ban.

        2 months later

        aaP_iovajay
        Hello, does your site have logs at /www/wwwlogs, its name needs to be the same as the site's name. For example: xxx.com_access_log , xxx.com.log , xxx.com_ols.access_log

          aaPanel_Kern
          I ended up re-creating that site and now it works. I did compare the logs with the working sites and they were all there. permissions and everything the same. Only one domain not working. It was just weird. I have cleaned, removed, change permisions, restarted, nothing seems to get rid of that error. I did use cloudflare cdn just like above messages, I did have a few IP's banned, fail attempts... Then decided to delete the site from fail2ban. When I tried to add the site again getting "The log file does not exist and cannot be created."

          P.S. I have a test server. If you need access let me know. I have recreated that error.

            aaP_iovajay
            Has your site changed the log configuration? give me your access me, what is the problem with the test, thanks
            please send to kern@aapanel.com.
            It is recommended to fill in the following
            Post link:
            SSH account password and port:
            aapanel login link address and account password:

              aaP_iovajay
              This is because the default log configuration has been modified, and fail2ban cannot make a judgment when adding a site, so the addition fails.
              Solution:

              1. Modify it back to the default configuration
              2. Add one more default configuration and comment it.
                3 months later
                5 months later

                in site-directory turn on (write access log ... works for me

                7 months later
                7 months later
                3 months later

                I have the same error! how can i fix it i tried many things but nothing worked!

                23 days later