Help Request: CrowdSec CAPI Connection Blocked β Proxy Support?
Hi everyone! π
I'm currently running CrowdSec on my server, but it's unable to connect to https://api.crowdsec.net/ due to heavy network censorship and governmental blocks (a lot of CDNs and websites are affected in my region).
Because of this, the CAPI communication fails, and CrowdSec can't function as intended.
Is there any way to configure CrowdSec to use a proxy (HTTP or SOCKS5) for outgoing requests β especially to reach the CrowdSec API?
Any workaround, built-in support, or hacky solution is welcome. Appreciate any help or ideas!
Thanks in advance
2 Replies
Important Information
Thank you for getting in touch with your support request. To expedite a swift resolution, could you kindly provide the following information? Rest assured, we will respond promptly, and we greatly appreciate your patience. While you wait, please check the links below to see if this issue has been previously addressed. If you have managed to resolve it, please use run the command
/resolve or press the green resolve button below.Log Files
If you possess any log files that you believe could be beneficial, please include them at this time. By default, CrowdSec logs to /var/log/, where you will discover a corresponding log file for each component.
Guide Followed (CrowdSec Official)
If you have diligently followed one of our guides and hit a roadblock, please share the guide with us. This will help us assess if any adjustments are necessary to assist you further.
Screenshots
Please forward any screenshots depicting errors you encounter. Your visuals will provide us with a clear view of the issues you are facing.
Β© Created By WhyAydan for CrowdSec β€οΈ
FAQ / Troubleshooting | CrowdSec
You may see CrowdSec referred to as "Security Engine" and Bouncers referred to as "Remediation Components" within new documentation. This is to better reflect the role of each component within the CrowdSec ecosystem.