• 0 Posts
  • 19 Comments
Joined 2 months ago
Cake day: February 15th, 2025
  • HelloRoot@lemy.loltoLinux@lemmy.ml•Linux is not your PanaceaEnglish
    0·
    14 days ago

    Oh, it was supposed to be rage bait. I actually thought it was quite funny.

    I recognized myself from a decade ago and this post quite a bit. It uhh didn’t go very well until through years of suffering I figured out the perfect setup for me and how to properly deal with all the little issues.

    I know it sounds dumb but my Ubuntu used to break like every six months and I had to always reinstall it.

  • HelloRoot@lemy.loltoSelfhosted@lemmy.world•~~Enshitification of CrowdSec~~ Edit: bug in CrowdSec limiting featuresEnglish
    0·
    16 days ago

    Copied reply from the mastodon thread:

    tldr - OP misunderstood a bug 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.

  • HelloRoot@lemy.loltoSelfhosted@lemmy.world•Caddy reverse proxyEnglish
    0·
    18 days ago

    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.

    Steps to Fix:

    1. Check if the path exists and is correct Run:

      ls -ld /home/Joe/container/caddy/Caddyfile
      • If it’s a directory, it should be a file instead.
      • If it doesn’t exist, create an empty one:
        touch /home/Joe/container/caddy/Caddyfile

    2. Ensure correct permissions

      chmod 644 /home/Joe/container/caddy/Caddyfile

    3. 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

    4. Restart Docker and Try Again

      docker compose down
docker compose up -d

    If the error persists, check docker logs caddy for additional hints.

  • HelloRoot@lemy.loltoSelfhosted@lemmy.world•Random people started sharing child pornography on my matrix server, what are my options?English
    0·
    27 days ago

    Probably should have given all of the evidence to the police instead of deleting some of it.

    In most western jurisdictions platform operators are not liable for user content, (as long as they cooperate with the authorities) so nothing for you to worry about.

    Next time, don’t do anything, no deleting, no blocking, contact the police and ask them what they would like you to do. Maybe they’d even would want to letting them keep posting for a while to gather more data on the offenders, but idk how they deal with selfhosted stuff tbh…

    (this is not legal advice)

    (Also I totally understand that you don’t want your other users seing that kind of stuff. I know nothing about the matrix moderation tools, so maybe the media is on the server db somewhere … might be relevant to figure that out)

    Edit: this does not apply if you live in an authoritarian police state or third world country, like OP apparently does.