https://github.com/TecharoHQ/anubis/issues/92
note: this is pretty much temporary until we get first class support for Traefik
They seem to be working on a traefik middleware, but in the meantime there is a guide to set it up manually with traefik.
what about a local, encrypted backup
fmhy is the best
Copied crowdsec reply from the mastodon thread:
tldr: OP misunderstood a bug/usererror as a new limiting policy
Hey Laurence from CrowdSec Support here.
We don’t store logs, so I assume you’re referring to alerts. Based on the screenshot you provided, the most likely reason you’re not seeing any alerts is that they may fall outside the currently selected date range. You can try clicking the magnifying glass icon next to the date picker to remove the filter, which should display all available alerts.
That said, there is a known issue we’re actively fixing—clicking on the date picker may trigger an error. If removing the filter doesn’t work, let me know, and once the fix is live, I’ll be happy to ping you so we can investigate further.
Regarding alert retention, the community tier has always had a limit—either 500 alerts or seven days, whichever comes first. With the new system, we now retain alerts for both the current and previous month, up to 500 per month, effectively doubling the total alert capacity to 1,000. If you’re primarily interested in real-time alerts, keep in mind that the CrowdSec console is designed for alert retention and ease of use, with additional features. Alternatively, for those who prefer a fully customized setup, we provide extensive documentation on integrating CrowdSec with Prometheus and Grafana for self-hosted monitoring.
I understand the frustration, and I appreciate the feedback. However, it’s important to consider that CrowdSec is built and maintained by a dedicated team of around 30 people. While open-source, over 95% of contributions come directly from our team, whether for the hub or various CrowdSec components. Ensuring the long-term sustainability of the project requires balancing free community access with the resources needed to maintain and improve the platform.
Happy to discuss more via email or on this thread, as we truly value feedback and want to ensure every voice is heard across various platforms.
The error suggests that you’re trying to mount a file (Caddyfile) onto a directory or vice versa. Let’s debug this step by step.
Check if the path exists and is correct Run:
ls -ld /home/Joe/container/caddy/Caddyfile
touch /home/Joe/container/caddy/Caddyfile
Ensure correct permissions
chmod 644 /home/Joe/container/caddy/Caddyfile
Check YAML Formatting
Your docker-compose.yml seems to have incorrect indentation and improper quotes around version. Here’s a fixed version:
version: "3.3"
networks:
caddy:
services:
portainer:
image: portainer/portainer-ce:latest
container_name: portainer2
restart: unless-stopped
security_opt:
- no-new-privileges:true
volumes:
- /etc/localtime:/etc/localtime:ro
- /var/run/docker.sock:/var/run/docker.sock:ro
- /home/Joe/containers/portainer/portainer-data:/data
networks:
- caddy
ports:
- 9000:9000
caddy:
image: caddy:latest
restart: unless-stopped
container_name: caddy
ports:
- 80:80
- 443:443
volumes:
- /home/Joe/container/caddy/Caddyfile:/etc/caddy/Caddyfile
- /home/Joe/container/caddy/site:/srv
- /home/Joe/container/caddy/caddy_data:/data
- /home/Joe/container/caddy/caddy_config:/config
networks:
- caddy
Restart Docker and Try Again
docker compose down
docker compose up -d
If the error persists, check docker logs caddy for additional hints.
unleak it