if you have a pixel theres absolutely no reason why you shouldnt use it.

Plenty reasons to not use it on a pixel…I had horrible compatibility with all sorts of banking apps, government 2FA and traffic warning systems, to the point where they just couldn’t work at all. Their sandboxed play services breaks a shitload of day to day convenience and even necessities to increase privacy.

The article also mentions how the ports are not seated well and also talks about how they’re unstable in the OS.

But the 16 still has issues with the modular ports, this really shouldn’t be the case. That stuff should be ironed out by now. By the fourth generation of port modules, they absolutely should fit well, look good and work properly all the time…but they don’t

But the entire concept of a modular build with replaceable ports should be well known. They should not have panel gaps, bad alignment with height differences and stability issues with these parts because they’ve had multiple design iterations of this already. So why have they seemingly not applied any of this knowledge and experience they have from the 13 to the 16? These are the same issues gen 1 of the 13 had, they should not exist on the 16 that uses the exact same design for these parts.

It’s not v1 though, it’s v4 of the concept. They already made 3 generations of the concept with the framework 13, and it’s pretty bad to have these kind of issues after that many attempts.

I am actually using docker compose, I’ve tried their guide as well with no luck.

It would just result in them having official and unofficial devices, where all the things they don’t want linked to their person, political party or public knowledge is on a different device that isn’t going to get caught in the FOIA requests.

Hmm, they’re not easily available in the EU it seems.

Also a US based company, if that matters to you.

I would consider that a downside TBH, but it’s hard to avoid unfortunately.

What would you recommend as a replacement with same level of novice-friendly UI/setup? I was looking to go down that route specifically because it seems like an easy way to get a solid network setup without being a network pro.

I’m running my smart home entirely from a single NUC running proxmox with VMs and LXCs for my services. It’s pulling ~7W on average

No they’re in the same compose file, I just left other parts out because it’s fairly long for a post.

Actually I’m also not using the default port for any of my qbit instances

IDK, it’s worth a try to rearrange the containers I would say.

Yeah i pretty much stole this from someone else, although it only used a single torrent client so i just added another that looked the same. i’m not very skilled in docker, so some things may not be best practice (or even correct)

qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    network_mode: service:gluetun
    environment:
      - PUID=${APPUSER_PUID}
      - PGID=${APPUSER_PGID}
      - TZ=${TIME_ZONE_VALUE}
      - WEBUI_PORT=8084
    volumes:
      - ${PATH_TO_DATA}/qbit/config:/config
      - ${PATH_TO_COMPLETE}:/downloads
    restart: unless-stopped
    depends_on:
      - gluetun

  qbittorrentTL:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrentTL
    network_mode: service:gluetun
    environment:
      - PUID=${APPUSER_PUID}
      - PGID=${APPUSER_PGID}
      - TZ=${TIME_ZONE_VALUE}
      - WEBUI_PORT=8085
    volumes:
      - ${PATH_TO_DATA}/qbitTL/config:/config
      - ${PATH_TO_COMPLETE}:/downloads
    restart: unless-stopped
    depends_on:
      - gluetun

  gluetun:
    image: qmcgaw/gluetun
    container_name: gluetun
    networks:
      pirate_net:
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - VPN_SERVICE_PROVIDER=protonvpn
      - OPENVPN_USER=[USER]
      - OPENVPN_PASSWORD=[PASSWORD]
      - SERVER_COUNTRIES=[COUNTRIES]
      - VPN_PORT_FORWARDING=on
      - UPDATER_PERIOD=6h
    ports:
      - 8084:8084 # Qbit
      - 8085:8085 # QbitTL
      - 6881:6881
      - 6881:6881/udp
      - 8191:8191 # Flaresolverr
      - 9696:9696 # Prowlarr
      - 7878:7878 # Radarr
      - 8989:8989 # Sonarr
    volumes:
      - ${PATH_TO_DATA}/gluetun/config:/config

networks:
  pirate_net:
    driver: bridge

That’s really weird, I’m using the same image to run two instances of qbit behind gluetun without any issues whatsoever.