help configuration bouncer traefik
apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
name: bouncer
namespace: traefik
spec:
plugin:
bouncer:
CrowdsecLapiKey: api-key
Enabled: true
logLevel: DEBUG
crowdsecMode: live
crowdsecLapiHost: "crowdsec-service:8080"
I've also tried setting crowdsecLapiHost to just "crowdsec-service" and "http://crowdsec-service:8080", but the error persists.
I've confirmed that the crowdsec-service is available via HTTP at 10.105.37.20:8080 from other pods.
Is there a specific format for the crowdsecLapiHost or another way to configure the LAPI connection to avoid this URL validation error?
5 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 ❤️
in our helm chart example the url is
that might point you in the right direction?
"That's an excellent point, thank you for clarifying! I believe the issue was that my crowdsecLapiHost value was already prefixed with the scheme, causing the http://http:// error.
Yes, the remediation has
crowdsecLapiScheme as another configuration option, so it does auto prefix the http:// or whatever value this is set too but defaults to formerAh, that makes perfect sense! Thank you so much for the clarification.
That explains the http://http:// error perfectly. My Middleware was configured with the scheme in the crowdsecLapiHost value, which was causing the issue.
I've now separated the configuration to explicitly use:
crowdsecLapiHost: "crowdsec-service.crowdsec.svc.cluster.local:8080"
crowdsecLapiScheme: http
I'm re-deploying with this fix now. I'll let you know if it resolves the issue. Your help is very much appreciated!