nobullwebsites
Forum Replies Created
-
Forum: Plugins
In reply to: [CrowdSec] Unable to connect Bouncer on DockerI think Crowdsec must be installed outside of the container which is why I’m having issues. According to Runcloud documentation, I need to replace localhost or 127.0.0.1 with “host”, but I still can’t get it to work.
https://runcloud.io/knowledgebase/articles/docker/why-containerized-server-using-host-instead-of-localhost-or-127001
I’m going to give up for now and readdress it when I have some more free time. Thank you kindly for your help!Forum: Plugins
In reply to: [CrowdSec] Unable to connect Bouncer on DockerThank you for your reply. Crowdsec is installed to /etc/crowdsec. I looked in the local_api_credentials.yaml and the URL is http://127.0.0.1:8080. The online_api_credentials.yaml URL is https://api.crowdsec.net.
What you’re saying makes sense. I installed Crowdsec agent to the server using the usual instructions:curl -s https://packagecloud.io/install/repositories/crowdsec/crowdsec/script.deb.sh | sudo bash
sudo apt install crowdsec -y
sudo apt install crowdsec-firewall-bouncer-iptables -y
I guess because the webapp is containerised, it cannot connect to anything localhost. Do you have any tips on how to find the correct value for the localhost field in WordPress bouncer setup?
Thanks again for your help with this.