Installation and Troubleshooting Guide

Detroit SBS is optimized for Ubuntu-based server environments. Before installing, confirm the host has root access, stable outbound internet, accurate server time, and open management ports for your admin access.

Recommended baseline: Ubuntu 22.04+, 2 vCPU, 4 GB RAM, and persistent public IP. For high traffic services, increase CPU and memory based on observed packet rate.

# check system version and kernel
lsb_release -a
uname -r

# verify resources
free -h
nproc
df -h

Run the installer in a clean shell session. If you manage firewall rules manually, export or snapshot current rules first so rollback is simple if needed.

# update package index
sudo apt update && sudo apt upgrade -y

# install base dependencies
sudo apt install -y curl wget ca-certificates jq

# example bootstrap (replace with your official script)
curl -fsSL https://example.detroit-sbs/install.sh | sudo bash

After installation completes, keep the service credentials secure and store onboarding details in your internal runbook for your team.

For one-port deployments, start with your critical service port first. For full server protection, enable all-port mode according to your purchased plan.

# one-port protection example
sudo sbs-cli protect --mode single --port 443

# all-port protection example
sudo sbs-cli protect --mode all-ports

# review active policy
sudo sbs-cli status

Apply staged rollout in production: protect one service, monitor, then extend policy scope. This prevents accidental lockouts caused by wrong allowlists.

Validate protection immediately after setup. Confirm service reachability, mitigation activation, and acceptable latency from your target regions.

# service + process checks
sudo systemctl status sbs-agent --no-pager
sudo journalctl -u sbs-agent -n 100 --no-pager

# network verification
curl -I https://your-domain.com
ping -c 5 your-domain.com

During attack windows, inspect blocked packet trends and ensure legitimate traffic remains stable. Document baseline latency before and after deployment.

Issue: Agent not starting after install.
Fix: verify dependencies and permissions, then restart service.

sudo systemctl daemon-reload
sudo systemctl restart sbs-agent
sudo systemctl status sbs-agent --no-pager

Issue: Dashboard reports server offline.
Fix: check outbound network/DNS and ensure token is valid.

curl -I https://sbs.detriot.host
nslookup sbs.detriot.host
sudo sbs-cli re-auth --token <NEW_TOKEN>

Issue: Legitimate users blocked.
Fix: add allowlist rules and lower aggressive mitigation profile.

sudo sbs-cli allowlist add --ip <TRUSTED_IP>
sudo sbs-cli policy set --profile balanced
sudo sbs-cli reload

Keep the agent and host patched regularly. Before major updates, take a snapshot and export current policy for quick rollback.

# update routine
sudo apt update && sudo apt upgrade -y
sudo sbs-cli update
sudo sbs-cli backup --output /root/sbs-backup-$(date +%F).json

If your team sees sustained attacks, gather diagnostics (logs, timestamp, traffic samples, affected ports, region impact) and send them with your Detroit SBS ticket. This reduces investigation time and accelerates mitigation tuning.