CrowdSec - lightweight and collaborative security engine
Forum Replies Created
-
Forum: Plugins
In reply to: [CrowdSec] Comment ? Forms ?Hi,
if you install the CrowdSec agent on your server and the CrowdSec plugin on your WordPress site, all web requests to your site will be checked: if there is a known decision for the current visitor’s IP, then the plugin will apply this decision (display a captcha or a ban wall)
At the moment, there is no option to secure only a part of your front site: all requests to the front site are monitored.
I hope this answers your question.
Thanks
Forum: Plugins
In reply to: [CrowdSec] ERROR ON TESTINGHi,
I guess your issue is now resolved. I will thus close this support ticket.
If you still have an error, please feel free to open an issue on the GitHub repository : Github WordPress CrowdSec plugin
Thanks
Forum: Plugins
In reply to: [CrowdSec] Test ErrorHi,
we just released a 1.8.1 version of the plugin with a fix for your issue.
Thanks
Forum: Plugins
In reply to: [CrowdSec] Test ErrorHi,
I guess you have pulled a new version of the plugin and, since you did not save any settings (which is normal), the geolocation type setting was empty (which is normal) and that throws you error : this is not normal and I will try to fix it.
Once you have saved your settings, the geolocation type setting has been populated and thus, error disappears.
Thanks for your message, will try to fix this bug : anything should work without saving settings.
Forum: Plugins
In reply to: [CrowdSec] ERROR ON TESTINGHi,
this error seems to indicate that your bouncer key is not allowed.Maybe you should re-create a bouncer and use the new generated key.
Please let me know.
Thanks
Forum: Plugins
In reply to: [CrowdSec] allow_url_fopen requiredHi,
with the new version 1.8.0 of the plugin, you can choose to use
curlinstead offile_get_contents. (We added a configuration calledUse cURL to call LAPI).So now, if you have
curlon your system, you should be able to use this plugin with a disabledallow_url_fopensetting.Thanks
Forum: Reviews
In reply to: [CrowdSec] CrowdSec Plugin Crashes WordPress 6.01 WebsiteHi,
thanks for your message.
We just have tested the plugin on a fresh WordPress 6.0.1 installation, and we didn’t see this kind of issue.Maybe it could happen due to some other plugin conflict, or for some specific server configuration.
If you can share more details (like error messages in server log files or server setup detail), please feel free to open an issue on the GitHub repository : Github WordPress CrowdSec plugin
Thanks
Forum: Plugins
In reply to: [CrowdSec] Whishlist – Connection checker with backendHi,
I guess we can mark this thread as resolved.
Thanks@marchettia Thanks to your feedback, we added the session_write_close() just after the bouncing stage.
This should now solve the problem you meet (you just have to update to the 1.0.5+ of the CrowdSec WP extension).
Forum: Plugins
In reply to: [CrowdSec] WP_EXCEPTION_WHILE_BOUNCINGHi @wartraxx93,
Thanks to contact us.
“Undefined index: REMOTE_ADDR”: This PHP error occurs when running the code in a non-web context (ex: from the PHP cli).
IMHO,this PHP notice should not break the expected behaviour of your website or of the CrowdSec bouncer, but it’s still strange. Do you run the plugin in a particular way (like CI, PHP CLI, etc)?
Forum: Plugins
In reply to: [CrowdSec] Fatal Error after update v. 1.0.0Hello, yes it was a error from our side, sorry for inconvenience but we quickly release the patch in the next 24h.
Just upgrade to the latest version to fix this issue (currently 1.0.4).
Fell free to ask if you meet another problem.
Hi @marchettia
This has just been fixed in the last release (1.0.x).
Thank you for your feedback 🙂
Thank you for your feedback. We’ll fix this soon.
Forum: Plugins
In reply to: [CrowdSec] bug with matomo pluginHello @denisit71, thank you for using our CrowdSec plugin. After investigations, we are not reproducing the problem you mention.
I can confirm to you that the CrowdSec plugin does not force the display of errors, indeed it does not contain any
ini_setdirective and never calls theerror_reportingfunction.We also installed fresh CrowdSec plugin and fresh Matomo plugin on a fresh install of WordPress (last version).
I assume that another plugin or another code modification will be the cause of this forced display of errors.
Thanks again for your feedback and don’t hesitate to give us more feedback if you have any problems.
- This reply was modified 5 years, 2 months ago by CrowdSec - lightweight and collaborative security engine.
- This reply was modified 5 years, 2 months ago by CrowdSec - lightweight and collaborative security engine.
Forum: Plugins
In reply to: [CrowdSec] bug with matomo pluginHello Denisit71, and thank you for your feedback. We will take a quick look at this.