Repository navigation
CrowdSec Firewall Bouncer not starting after reboot #90
Description
Deployrr Version
v6.0.37
Operating System
Ubuntu 24.04
Other OS (if applicable)
No response
Server Environment
Proxmox LXC (Unprivileged)
CPU Architecture
x86_64 (amd64)
Docker Version
No response
Bug Area
App Runtime (after install)
Affected App (if applicable)
CrowdSec Firewall Bouncer
GPU Passthrough
None
Bug Description
CrowdSec Firewall Bouncer doesn't start after system reboot due to a race condition.
Fix:
sudo vim /etc/systemd/system/crowdsec-firewall-bouncer.service.d/override.conf
add these line:
[Service]
Restart=always
RestartSec=5
then run
sudo systemctl daemon-reexec
sudo systemctl daemon-reload
and test a reboot sudo reboot now
Steps to Reproduce
- install CrowdSec Firewall Bouncer
- reboot
- check service status, it will say dead
Expected Behavior
the service to run after reboot
Actual Behavior
service tries to start and fails
Relevant Logs
Additional Context
No response
Pre-submission Checklist
- I have searched existing issues and this hasn't been reported yet.
- I am running the latest version of Deployrr.
- I have checked the documentation for a solution.
Activity
FloTexaTenn commentedon May 28, 2026
sudo vim /etc/systemd/system/crowdsec-firewall-bouncer.service.d/override.confreturns[ Directory '/etc/systemd/system/crowdsec-firewall-bouncer.service.d' does not exist ]despite the service showing running in the deployrr menu.systemctlshows that it is running...crowdsec-firewall-bouncer.service loaded active running The firewall bouncer for CrowdSecFloTexaTenn commentedon May 28, 2026
I can now confirm that creating the directory first works. Here are the steps:
Create the drop-in directory
sudo mkdir -p /etc/systemd/system/crowdsec-firewall-bouncer.service.d/Create the override.conf
sudo nano /etc/systemd/system/crowdsec-firewall-bouncer.service.d/override.confAdd the following lines:
[Service]
Restart=always
RestartSec=5
sudo systemctl daemon-reexecsudo systemctl daemon-reloadThanks, @g0ldfngr!