[BUG] Unban through bwcli when using redis fails

[LeVraiRoiDHyrule]

What happened?

Hi,
I am using redis to persist bans (bw version 1.6.2-rc2). It is configured as such :

      USE_REDIS: yes
      REDIS_HOST: bunkerweb-redis

  bunkerweb-redis:
    image: redis:7-alpine
    container_name: bunkerweb-redis
    restart: unless-stopped
    environment:
      <<: *all-common
    networks:
      - bunkerweb-redis
    volumes:
      - ${CONFIG_FOLDER}/bunkerweb/redis:/data 
    healthcheck:
      test: ["CMD-SHELL", "redis-cli ping | grep PONG"]
      start_period: 20s
      interval: 30s
      retries: 5
      timeout: 3s

bunkerweb-main and bunkerweb-ui are also in the bunkerweb-redis docker network.
Bunkerweb-main does not throw any error when trying to connect to redis at container start. So it is working.

But when I try to do bwcli unban XXXXXXX to unban an ip, I am having the following error:

b87cb053ceb7:~$ bwcli unban XXXXXX
[2025-05-24 12:12:20 +0200] [CLI] [44526] [ℹ️ ] - Getting variables from database
[2025-05-24 12:12:20 +0200] [CLI] [44526] [ℹ️ ] - ✅ Database connection established
[2025-05-24 12:12:21 +0200] [CLI] [44526] [ℹ️ ] - Connecting to Redis at bunkerweb-redis:6379
[2025-05-24 12:12:26 +0200] [CLI] [44526] [❌] - Failed to connect to Redis: Error -3 connecting to bunkerweb-redis:6379. Try again.
[2025-05-24 12:12:26 +0200] [CLI] [44526] [❌] - Failed to connect to Redis, disabling Redis functionality
[2025-05-24 12:12:26 +0200] [API] [44526] [ℹ️ ] - Successfully sent API request to http://bunkerweb-main:5000/unban
[2025-05-24 12:12:26 +0200] [CLI] [44526] [ℹ️ ] - CLI command status : ✔️ (success)

 ✅ SUCCESS 
────────────────────────────────────────────────────────────────────────────────
• 🔓 IP XXXXXX has been unbanned globally
────────────────────────────────────────────────────────────────────────────────

b87cb053ceb7:~$ 

The unban does not work, the ip is still banned.
Would you have an idea why ?

Thanks in advance for any answer.

How to reproduce?

1. Install bw 1.6.2-rc2
2. Install redis with the compose above
3. Configure bw as above
4. Check that bw connects to redis at startup
5. Try to unban a banned ip

Configuration file(s) (yaml or .env)

USE_REDIS: yes
      REDIS_HOST: bunkerweb-redis

Relevant log output

b87cb053ceb7:~$ bwcli unban XXXXXX
[2025-05-24 12:12:20 +0200] [CLI] [44526] [ℹ️ ] - Getting variables from database
[2025-05-24 12:12:20 +0200] [CLI] [44526] [ℹ️ ] - ✅ Database connection established
[2025-05-24 12:12:21 +0200] [CLI] [44526] [ℹ️ ] - Connecting to Redis at bunkerweb-redis:6379
[2025-05-24 12:12:26 +0200] [CLI] [44526] [❌] - Failed to connect to Redis: Error -3 connecting to bunkerweb-redis:6379. Try again.
[2025-05-24 12:12:26 +0200] [CLI] [44526] [❌] - Failed to connect to Redis, disabling Redis functionality
[2025-05-24 12:12:26 +0200] [API] [44526] [ℹ️ ] - Successfully sent API request to http://bunkerweb-main:5000/unban
[2025-05-24 12:12:26 +0200] [CLI] [44526] [ℹ️ ] - CLI command status : ✔️ (success)

 ✅ SUCCESS 
────────────────────────────────────────────────────────────────────────────────
• 🔓 IP XXXXXX has been unbanned globally
────────────────────────────────────────────────────────────────────────────────

b87cb053ceb7:~$

BunkerWeb version

1.6.2-rc2

What integration are you using?

Docker

Linux distribution (if applicable)

OpenMediaVault

Removed private data

• I have removed all private data from the configuration file and the logs

Code of Conduct

• I agree to follow this project's Code of Conduct

[TheophileDiot]

Hi @LeVraiRoiDHyrule, thank you for opening this Issue. You have a connection issue with your redis server.

[LeVraiRoiDHyrule]

Thanks for your answer.
That is the most logical cause. But as I said, the main bunkerweb container can connect to redis without issues when running. I have the following log at start:
025/05/27 09:55:35 [notice] 1064#1064: *18 [REDIS] connectivity with redis server bunkerweb-redis is successful, context: ngx.timer
If I deliberately make the redis connection url false, the logs says that failed to connect. So the connection with redis is working on the main container running.
This connection error to redis only happens when using bwcli. That is why it is weird.

Currently, only my main bunkerweb container can communicate with redis as they are alone in the docker network. Do other containers, like scheduler or autoconf, need to connect to redis too or is all happening through the main container ?

[fl0ppy-d1sk]

Do you execute bwcli in the BW container ?

[LeVraiRoiDHyrule]

Yes. But I have just noticed that the error is different if executed in the main bunkerweb container.

bunkerweb-main:

267411e0f622:/usr/share/bunkerweb$ bwcli unban XXXXXX
[2025-05-27 12:52:41 +0200] [CLI] [10553] [ℹ️ ] - Connecting to Redis at bunkerweb-redis:6379
[2025-05-27 12:52:41 +0200] [CLI] [10553] [ℹ️ ] - Successfully connected to Redis
[2025-05-27 12:52:41 +0200] [CLI] [10553] [❌] - Failed to delete ban for 80.83.34.87 from redis
[2025-05-27 12:52:41 +0200] [API] [10553] [❌] - Can't send API request to http://127.0.0.1:5000/unban : Request failed: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
[2025-05-27 12:52:41 +0200] [CLI] [10553] [ℹ️ ] - CLI command status : ✔️ (success)

 ✅ SUCCESS 
────────────────────────────────────────────────────────────────────────────────
• 🔓 IP XXXXX has been unbanned globally
────────────────────────────────────────────────────────────────────────────────

Every other bunkerweb container (bunkerweb-scheduler, bunkerweb-autoconf...):

89617741761c:~$ bwcli unban XXXXX
[2025-05-27 12:53:02 +0200] [CLI] [7527] [ℹ️ ] - Getting variables from database
[2025-05-27 12:53:02 +0200] [CLI] [7527] [ℹ️ ] - ✅ Database connection established
[2025-05-27 12:53:02 +0200] [CLI] [7527] [ℹ️ ] - Connecting to Redis at bunkerweb-redis:6379
[2025-05-27 12:53:07 +0200] [CLI] [7527] [❌] - Failed to connect to Redis: Error -3 connecting to bunkerweb-redis:6379. Try again.
[2025-05-27 12:53:07 +0200] [CLI] [7527] [❌] - Failed to connect to Redis, disabling Redis functionality
[2025-05-27 12:53:07 +0200] [API] [7527] [ℹ️ ] - Successfully sent API request to http://bunkerweb-main:5000/unban
[2025-05-27 12:53:07 +0200] [CLI] [7527] [ℹ️ ] - CLI command status : ✔️ (success)

 ✅ SUCCESS 
────────────────────────────────────────────────────────────────────────────────
• 🔓 IP XXXX has been unbanned globally
────────────────────────────────────────────────────────────────────────────────

So I guess the error message is not being returned when using a container other than bunkerweb-main. There is more details in bunkerweb-main. I still don't understand why it successfully connects while running and disconnects when using bwcli.

I tried deleting redis data and recreating the container, and got the same results. Is there something wrong with my docker compose above ?

[LeVraiRoiDHyrule]

Hi,
I just updated to 1.6.2-rc5, and I still have the same problem.
As I am apparently the only one with this issue, I guess there is something wrong with my setup. Or there is very few users who uses redis with BW. I can't find what the problem could be.
Did that error happen on your end too ?

Thanks in advance for your help.

[TheophileDiot]

Hi @LeVraiRoiDHyrule, we are having issues with the rc4 and rc5, can you try again when the rc6 is released ? Thank you!

[LeVraiRoiDHyrule]

Thanks for your answer.
I just updated to rc6, and I am still having the same behaviour. bwcli ban/unban commands fail with the same error as above.

[LeVraiRoiDHyrule]

Found the problem ! It was indeed my configuration that was incorrect, the problem is about IPs allowed to access the API. I needed to include 127.0.0.1 in my API_WHITELIST_IP variable. Which gives me API_WHITELIST_IP: ${BUNKERWEB_NETWORK_IP4}.0/24 127.0.0.1. It had nothing to see with redis or its BW configuration.