Does anyone else have any idea how to bypass that?
Update:
Tried to add exclusions via pangolin docker bot
----------------------------------------------
Allowlist: white
----------------------------------------------
Name white
Description whitelists_pangolin
Created at 2025-04-05T08:21:04.621Z
Updated at 2025-04-05T08:21:31.137Z
Managed by Console no
----------------------------------------------
-------------------------------------------------------------
Value Comment Expiration Created at
-------------------------------------------------------------
95.88.xx.xxx never 2025-04-05T08:21:04.621Z
-------------------------------------------------------------
Still effect is the same
Originally created by @aszurnasirpal on GitHub (Apr 5, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/463
Hi,
I tried many ways to bypass that, but I failed miserably.
in docker compose I mounted volume under crowdsec section
```
- ./config/whitelists.yaml:/etc/crowdsec/parsers/s02-enrich/whitelists.yaml
```
then I edited ./config/whitelists.yaml, where I put my IP address
```
ip:
- "::1"
- "95.88.xxx.xxx"
```
but still, while in crowdsec logs I see that IP is banned
```
time="2025-04-05T08:05:47Z" level=info msg="172.18.0.4 - [Sat, 05 Apr 2025 08:05:47 UTC] \"GET /v1/decisions?ip=95.88.xxx.xxx&banned=true HTTP/1.1 403 828.986µs \"Crowdsec-Bouncer-Traefik-Plugin/1.X.X\" \""
```
Additional info:
```
/ # cscli decisions list
No active decisions
```
```
/ # cscli alerts list
No active alerts
```
Does anyone else have any idea how to bypass that?
Update:
Tried to add exclusions via pangolin docker bot
```
----------------------------------------------
Allowlist: white
----------------------------------------------
Name white
Description whitelists_pangolin
Created at 2025-04-05T08:21:04.621Z
Updated at 2025-04-05T08:21:31.137Z
Managed by Console no
----------------------------------------------
-------------------------------------------------------------
Value Comment Expiration Created at
-------------------------------------------------------------
95.88.xx.xxx never 2025-04-05T08:21:04.621Z
-------------------------------------------------------------
```
Still effect is the same
Seems that is empty
output of
/crowdsecbouncers list
------------------------------------------------------------------
Name IP Address Valid Last API pull Type Version Auth Type
------------------------------------------------------------------
------------------------------------------------------------------
Do you know how can I fix it?
<!-- gh-comment-id:2780683611 -->
@aszurnasirpal commented on GitHub (Apr 5, 2025):
Seems that is empty
output of
/crowdsecbouncers list
```
------------------------------------------------------------------
Name IP Address Valid Last API pull Type Version Auth Type
------------------------------------------------------------------
------------------------------------------------------------------
```
Do you know how can I fix it?
Seems that is empty output of /crowdsecbouncers list
------------------------------------------------------------------
Name IP Address Valid Last API pull Type Version Auth Type
------------------------------------------------------------------
------------------------------------------------------------------
Most of 403 error we see here is due to bouncer not properly registered.
<!-- gh-comment-id:2780861203 -->
@hhftechnology commented on GitHub (Apr 5, 2025):
> Seems that is empty output of /crowdsecbouncers list
>
> ```
> ------------------------------------------------------------------
> Name IP Address Valid Last API pull Type Version Auth Type
> ------------------------------------------------------------------
> ------------------------------------------------------------------
> ```
>
> Do you know how can I fix it?
https://hhf.technology/snippets/pangolin-commands#bouncer-management
Most of 403 error we see here is due to bouncer not properly registered.
Thanks for the hint! I added the bouncer as you suggested
/ # cscli bouncers list
─────────────────────────────────────────────────────────────────────────────
Name IP Address Valid Last API pull Type Version Auth Type
─────────────────────────────────────────────────────────────────────────────
traefik-bouncer ✔️ api-key
─────────────────────────────────────────────────────────────────────────────
I added the given API key in docker-compose.yml with
and restarted the docker. But still I'm blocked (actually all requests are blocked also from other IPs)
Should I modify something else as well?
<!-- gh-comment-id:2780874319 -->
@aszurnasirpal commented on GitHub (Apr 5, 2025):
Thanks for the hint! I added the bouncer as you suggested
```
/ # cscli bouncers list
─────────────────────────────────────────────────────────────────────────────
Name IP Address Valid Last API pull Type Version Auth Type
─────────────────────────────────────────────────────────────────────────────
traefik-bouncer ✔️ api-key
─────────────────────────────────────────────────────────────────────────────
```
I added the given API key in docker-compose.yml with
```
environment:
- CROWDSEC_BOUNCER_API_KEY=MY_BOUNCER_API
```
and restarted the docker. But still I'm blocked (actually all requests are blocked also from other IPs)
Should I modify something else as well?
http:
middlewares:
# CrowdSec configuration with proper IP forwarding
crowdsec:
plugin:
crowdsec:
enabled: true
logLevel: INFO
updateIntervalSeconds: 15
updateMaxFailure: 0
defaultDecisionSeconds: 15
httpTimeoutSeconds: 10
crowdsecMode: live
crowdsecAppsecEnabled: true
crowdsecAppsecHost: crowdsec:7422
crowdsecAppsecFailureBlock: true
crowdsecAppsecUnreachableBlock: true
crowdsecLapiKey: "csdcdssffdsfdsfdsf+xXWwpif8j0WeBpeo" #key will go here
crowdsecLapiHost: crowdsec:8080
<!-- gh-comment-id:2780915612 -->
@hhftechnology commented on GitHub (Apr 5, 2025):
you should put it in the dynamic_config.yml
```
http:
middlewares:
# CrowdSec configuration with proper IP forwarding
crowdsec:
plugin:
crowdsec:
enabled: true
logLevel: INFO
updateIntervalSeconds: 15
updateMaxFailure: 0
defaultDecisionSeconds: 15
httpTimeoutSeconds: 10
crowdsecMode: live
crowdsecAppsecEnabled: true
crowdsecAppsecHost: crowdsec:7422
crowdsecAppsecFailureBlock: true
crowdsecAppsecUnreachableBlock: true
crowdsecLapiKey: "csdcdssffdsfdsfdsf+xXWwpif8j0WeBpeo" #key will go here
crowdsecLapiHost: crowdsec:8080
```
@hhftechnology, many thanks for the help. It works! I also appreciate other scripts that you provide on your forum. The Docker bot is fantastic!
<!-- gh-comment-id:2781030534 -->
@aszurnasirpal commented on GitHub (Apr 5, 2025):
@hhftechnology, many thanks for the help. It works! I also appreciate other scripts that you provide on your forum. The Docker bot is fantastic!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @aszurnasirpal on GitHub (Apr 5, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/463
Hi,
I tried many ways to bypass that, but I failed miserably.
in docker compose I mounted volume under crowdsec section
then I edited ./config/whitelists.yaml, where I put my IP address
but still, while in crowdsec logs I see that IP is banned
Additional info:
Does anyone else have any idea how to bypass that?
Update:
Tried to add exclusions via pangolin docker bot
Still effect is the same
@hhftechnology commented on GitHub (Apr 5, 2025):
did you check your bouncer? is it registered properly ?
@aszurnasirpal commented on GitHub (Apr 5, 2025):
Seems that is empty
output of
/crowdsecbouncers list
Do you know how can I fix it?
@hhftechnology commented on GitHub (Apr 5, 2025):
https://hhf.technology/snippets/pangolin-commands#bouncer-management
Most of 403 error we see here is due to bouncer not properly registered.
@aszurnasirpal commented on GitHub (Apr 5, 2025):
Thanks for the hint! I added the bouncer as you suggested
I added the given API key in docker-compose.yml with
and restarted the docker. But still I'm blocked (actually all requests are blocked also from other IPs)
Should I modify something else as well?
@hhftechnology commented on GitHub (Apr 5, 2025):
you should put it in the dynamic_config.yml
@aszurnasirpal commented on GitHub (Apr 5, 2025):
@hhftechnology, many thanks for the help. It works! I also appreciate other scripts that you provide on your forum. The Docker bot is fantastic!