CrowdSec - lightweight and collaborative security engine

Hi @brndnl0,

I’ve just published release 2.6.4 of the plugin, with the Redis DSN fix.

Now, you should be able to use the following DSN settings:

• redis:redis_user:redis_password@?host[redis_host:6379]
  
  or

• redis://redis_user:redis_password@redis_host:6379

Please let me know if it works for you.

Thanks

Hi @brndnl0 ,
thanks for your message.

I think it should work unless there’s a problem with the Symfony cache component itself.

On reading the documentation, you may have to use redis:user:pass@localhost:6379

Can you try with this ?
Can you also try a password without special characters (especially @)?
Just in case, maybe try also redis:user:[email protected]:6379

Do you have an error message somewhere ? (maybe in wp-content/uploads/crowdsec if you activate the debug log mode in the advanced settings of the plugin, or in the admin view when you save settings or try the bouncer)

Thanks

Hi @rolekwp,

Thanks for your message.

For the moment, it’s not possible to choose the location of log and cache files.
I’ve just created an issue to improve this.

For your information, if you choose Redis or Memcached as cache system, there will be no more cache files in the file system. You can also disable all logs (prod and debug).

Thanks again.

• This reply was modified 2 years, 3 months ago by CrowdSec - lightweight and collaborative security engine.

Hi, I’m closing this issue. Happy to continue the conversation here or elsewhere.

Hi @dimkasta ,
Thanks for your message.

In short: the WordPress plugin is “just” a bouncer (aka remediation component): it doesn’t detect anything, it applies CrowdSec’s decisions.

In other words, once you’ve installed the CrowdSec security engine on your server, certain decisions will be retrieved: community blocklist and local decisions, depending on the scenarios you install. The bouncer will “apply” these decisions: block access for “ban” remediation and display a captcha for “captcha” remediation.

For the last up-to-date documentation of the bouncer: https://github.com/crowdsecurity/cs-wordpress-bouncer/blob/main/docs/USER_GUIDE.md

And for a more generic CrowdSec ecosystem documentation: https://docs.crowdsec.net/docs/intro

Hope it will help,

Thanks

If I understand correctly, crowdsec is installed inside the web container itself. So, it should be accessiible directly.

Can you try the curl test call :

curl -H "X-Api-Key:your-bouncer-api-key" http://127.0.0.1:8080/v1/decisions\?ip=192.168.1.254

to see if there is an error ?

To see more logs from the WordPress bouncer itself, you can enable the debug mode in the Adavnced settings. When this mode is enabled, a debug.log file will be written in wp-content/plugins/crowdsec/logs folder.

Thanks

Hi, I’m closing this issue. Happy to continue the conversation here or elsewhere.

Thanks for your message.

It seems that your “api_url” setting is empty as your log shows ”api_url”:””

Can you set http://localhost:8080 in your Local API URL setting and try again ?

Thanks

• This reply was modified 3 years, 1 month ago by CrowdSec - lightweight and collaborative security engine.