Trying to do initial setup, pressing next->next as fast as I can, but my IP is blacklisted and I got on logs:
INFO Blocked IP address (security.ip-blocked) listenerId = “http-recovery”, localPort = 8080, remoteIp = 172.29.0.1, remotePort = 49124
Cleaning data and etc directories and another try didn’t help me.
Expected Behavior
Disable IP blacklisting during initial setup and first login to help me whitelist my IP.
Stalwart Version
v0.16.x
Installation Method
Docker
Database Backend
RocksDB
Blob Storage
RocksDB
Search Engine
Internal
Directory Backend
Internal
I have reviewed the documentation and FAQ and confirm that my issue is NOT addressed there.
on
I have searched this support forum (open and closed topics) and confirm this is not a duplicate.
on
I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.
The block is a BlockedIp record created automatically by Stalwart’s auto-ban mechanism (the security.ip-blocked event you’re seeing means the connection is being rejected because that address already has a stored ban, not that it’s happening for the first time). Clicking through the wizard very quickly can trip the “scan” or “loitering” ban thresholds, which are counted per source IP.
Because RocksDB is your data store, BlockedIp entries are persisted there. If clearing your mapped data/etc directories didn’t remove the ban, it’s likely that Docker is actually using a named volume for the RocksDB data rather than the bind-mounted paths you cleaned, so the ban survived. Check your docker-compose.yml/run command for any stalwart_data (or similar) named volume and remove it explicitly with docker volume rm, in addition to clearing the bind-mounted folders, then restart the container to trigger bootstrap mode again.
Once you’re past initial setup, you can avoid this in the future by adding your admin workstation’s IP as an AllowedIp entry (Security › Allowed IPs in the WebUI, or via CLI/JMAP), which bypasses rate limiting and auto-banning entirely. Note that only 127.0.0.1/::1 are allow-listed by default.
Cleaning data and etc folders help me for some seconds, i can run initial wizard again and if I fast as Clint Eastwood, sometimes I can do login, but until i navigate to whitelist IP tab, I became banned! And usually auto-ban is faster than me and it ban me on initial setup procedure.