BakedCatboy

I have about 50% humidity and don’t usually dry my filament and I start to have issues with the outer layer of the spool snapping repeatedly when feeding after a year or two of sitting out. I used to have a dryer for cases like this but it got left behind in a move so I currently try to only use my new spools until I can get another one because I don’t trust using the oven and using the heat bed is really slow.

I use haproxy just for simplicity, with the https fronted in tcp mode with a tcp request inspect delay and acls using req_ssl_sni allows switching between multiple backend based on hostname, though if you only had 1 backend server then it could just be a raw tcp proxy. I have my stuff split between 2 local boxes that are both connected to the reverse proxy using wg so this works well for me.

I use a wireguard tunnel as a reverse proxy and it does ssl passthrough with sni. Termination happens on my local box and the reverse proxy host doesn’t do any certs.

I went with rsync.net, grabbed a promo at some point and have been getting 1.6TB for $10/mo. They support a wide range of protocols (sshfs, sftp, r sync, borg), snapshots, idle alerts, geo redundancy for a fee. Been very happy with it so far. Had to retrieve some files once and had no issue.

Doesn’t this need an AI disclosure in the title and post per the rules of this community?

I completed a 300 mile move yesterday, and my homelab was one of the least stressful parts thanks to my pre-emptive downsizing from a half rack to just a Synology + Intel nuc. I also pre-emptively switched from forwarded ports to a reverse proxy because I didn’t want to be thinking about what isp I would end up with. Even further, I linked the nas and nuc directly with Ethernet so that I wouldn’t need to rely on static IPs or router-assisted local hostnames, mdns, avahi, whatever because I wanted to be able to transplant my lab onto any network just in case of emergency - thankfully I haven’t had to test that out but it’s nice knowing my lab should work on any network where both boxes can reach the internet / my reverse proxy. I was thinking worst case if we ended up in some apartment complex with some crappy provided setup that had broken local discovery then it would be 1 less thing to worry about.

To re-state, it’s not a problem of understand or the language, it’s a problem with overused, bland, and repetitive language and phrasing. It’s not fun to read even if you can understand it perfectly.

Yeah Google translate preserves a lot more of your communication style. AI overuses so many phrases it can get annoying reading something that was processed through it.

Honestly I like the idea of your project but the writing style of your post is very grating.

Ah cool, the docs made it sound like container: uses the container ID hash instead of the name so I wasn’t sure how that works. I just put stuff like this in the same compose file since they’re all closely related.

If it helps, here’s how I had my gluetun / transmission set up with mullvad (I’ve since moved to proton for port forwarding but I saved the mullvad config in case I needed to switch back):

services:
  gluetun:
    image: qmcgaw/gluetun:v3
    container_name: gluetun
    restart: always
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun:/dev/net/tun
    volumes:
      - ./volumes/gluetun:/gluetun
    environment:
      - TZ=America/New_York
#      Mullvad
      - VPN_SERVICE_PROVIDER=mullvad
      - VPN_TYPE=wireguard
      - SERVER_COUNTRIES=USA
      - SERVER_CITIES=New York NY
      - WIREGUARD_PRIVATE_KEY=
      - WIREGUARD_ADDRESSES=x.x.x.x/32
      - UPDATER_PERIOD=24h
      - UPDATER_MIN_RATIO=0.1
      - UPDATER_VPN_SERVICE_PROVIDERS=mullvad,privado,protonvpn
    networks:
      - default
      - ingress

  transmission:
    image: linuxserver/transmission:latest
    container_name: transmission
    restart: always
    network_mode: "service:gluetun"
    environment:
      - PUID=0
      - PGID=0
      - TZ=America/New_York
    volumes:
      - ./volumes/transmission:/config
      - /volume1/Media:/media

  flood:
    image: jesec/flood:latest
    container_name: flood-sidecar
    restart: always
    command: --port 3000
    user: "0:0"
    network_mode: "service:gluetun"
    volumes:
      - ./volumes/transmission:/config
      - /volume1/Media:/media:ro
    environment:
      - TZ=America/New_York
      - HOME=/config
    labels:
      - com.centurylinklabs.watchtower.enable=true
      - "traefik.enable=true"
      - "traefik.http.routers.flood.rule=Host(`flood.example.com`)"
      - "traefik.http.services.flood.loadbalancer.server.port=3000"
      - "traefik.http.routers.flood.entrypoints=websecure"
      - "traefik.http.routers.flood.tls.certresolver=mytlschallenge"
      # This example uses "Selective Authentication"
      - "traefik.http.routers.flood.middlewares=oauth-middleware"

It sounds like it’s just not worth it for you, and that’s totally fine! Plenty of people get by just fine with using random streaming sites.

Personally, I want something more reliable, I want to have copies of what I watch in my possession that cannot be taken down, and I want to share this with others so that my friends can benefit from my time investment instead of using a solution that only works for me. So that if my friends ask me “where do you get your stuff” I can offer to share with them at 0 extra effort instead of telling them “go do all these things that I already did”

As for usage, I only watch a few hours a week myself, but I share with 15-20 friends and family who watch a collective 160 hours a month last year and around 360 hours a month this year (about 15 days of watch time per month).

I have a fairly comprehensive arrstack, torrents and Usenet, seerr, Plex and jellyfin side by side with identical media mounts for maximum user choice, running on a nuc with quicksync so it handles 8+ simultaneous 1080p live transcodes without using much power or increasing CPU usage much more than 5-10%.

Mmmm fresh slop

Image

Image

My primary use case is safeguarding my important personal artifacts (family photos, digitized paperwork, encryption key / account recovery / 2FA backups) against drive failure (~2TB), followed by my decently sized Plex server (23TB), immich, nextcloud, and various other small things like selfhosted bitwarden, grocy, ollama, and stuff like that.

I run all of my stuff off of a 6 bay Synology (more drives helps with capacity as double redundancy with 6 drives costs you 30%) with an Intel nuc on top to run plex/jellyfin transcoding using quicksync instead of loading the poor nas with cpu transcoding, I also run ollama on the nuc since it has faster cores than the nas.

Image