Brute Force Stop problem with my Joomla a message error .htaccess is not read or writeble

[raziel1973]

Hi to everyone,
and thank you about your help.

I got this message when I go to Brut Force Stop in the setting section: You're either not using apache server, or the .htaccess file either does not exist, or it is not read- or writeable. Blocking via .htaccess will not work.

I on't know what I have to do...
Any help? is there a tutorial to help me?
my web site is www.around-naples.com

Thank you
Tony

[codeling]

The message is telling you what BFStop can determine. That is, that the .htaccess mechanism somehow isnt working on your server.
Do you know, are you using an apache webserver?
If yes, have you checked the permissions and ownership of the .htaccess file?
These things aside, if you can't figure out why .htaccess isn't working, you can still use the default way of blocking via Joomla itself.

[raziel1973]

Hi and thank you about your reply. I don't know how it's working... So do you know any tutorial that shows me how to figure out to changing the permissions... P.s I'm under host.it no Apache but mysql database Thank you Tony Inviato da Outlook per Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Bernhard Froehler ***@***.***> Sent: Tuesday, February 4, 2025 6:39:08 AM To: codeling/bfstop ***@***.***> Cc: raziel1973 ***@***.***>; Author ***@***.***> Subject: Re: [codeling/bfstop] Brute Force Stop problem with my Joomla a message error .htaccess is not read or writeble (Issue #220) The message is telling you what BFStop can determine. That is, that the .htaccess mechanism somehow isnt working on your server. Do you know, are you using an apache webserver? If yes, have you checked the permissions and ownership of the .htaccess file? These things aside, if you can't figure out why .htaccess isn't working, you can still use the default way of blocking via Joomla itself. — Reply to this email directly, view it on GitHub<#220 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPEHU4DY7BHEXQTMKGE3ESD2OBG7ZAVCNFSM6AAAAABWNI3EJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZSHEZDKMRWGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[codeling]

As I said, you don't really need the .htacces blocking functionality - bfstop works just as well with database-based blocking. It's just that some people prefer .htaccess based blocking (in case there are many attacks, there may be a performance benefit).

Also, it's hard to impossible to give a generic guide here - first you'd have to know if you're using apache; then, permissions come from multiple sources (operating system file level permissions, potential additional security measures such as SELinux, web server configuration, ...)

[codeling]

so if you're just worrying about the warning - its not critical for bfstop operation; just ignore it!