I'm looking to buy some security cameras for my mother in law. I currently have a small server with plenty of storage at my place that I'd prefer to use on at least a temporary basis to keep costs down. Are there any self hostable cameras that support a built in VPN? I currently use tailscale for my network but I'm open to learning something else. Alternatively, can they run over a tailscale subnet router? I don't use that yet but if I could place a cheap node in her place to help her access footage and my other services via subnet routing I'll do that too.

I'm repairing an old TV with corrosion on the board. I'm having trouble reading the schematic from the manual. Here's the relevant section: I have two questions:

Do the thick bars on one side of the capacitor and the base of the transistor indicate those are connected together? I'd tone it out but the board is heavily corroded and I'm unsure if they should be connected. I've also seen these bars on other parts of the board, but the components there are not rated anywhere near as high as C451. I feel like that risks high voltage backfeeding through the other parts of the circuit.

What kind of capacitor is C451, and should it be polarised? The BOM lists it as a pp cap which I understand to be non-polarised, but I can't find any key that tells me what the dot on the symbol means. Let me know if I can provide any further information. Thanks

I've been having trouble rebuilding my system for a few days now. The issue seems to be that a commit to nixpkgs-xr/xrizer added an aarch64 patch. There's been a commit that removes this patch but I can't seem to pull it with nix flake update which makes me think my flake might never have been working properly (although I'm getting the home-manager, stylix and unstable packages I've selected). Could someone please review my flake.nix and tell me if I'm doing something wrong?

{
  description = "Core Flake";

  inputs = {
    # Official NixOS Packages v25.11
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.11";
    home-manager = {
      url = "github:nix-community/home-manager/release-25.11";
      inputs.nixpkgs.follows = "nixpkgs";
    };

    nixpkgs-xr.url = "github:nix-community/nixpkgs-xr";

    unstable = {
      url = "github:NixOS/nixpkgs/nixos-unstable";
    };

    stylix = {
        url =  "github:nix-community/stylix/release-25.11";
        inputs.nixpkgs.follows = "nixpkgs";
        };
  };

  outputs = inputs@ { nixpkgs, nixpkgs-xr, unstable, home-manager, stylix, ... }: {
    nixosConfigurations.nixos = nixpkgs.lib.nixosSystem {
      modules = [
        # Import my existing configuration.nix
        ./configuration.nix

        nixpkgs-xr.nixosModules.nixpkgs-xr

        home-manager.nixosModules.home-manager
        {
          home-manager.useGlobalPkgs = true;
          home-manager.useUserPackages = true;
          home-manager.users.professor = import ./home.nix;
        }

        stylix.nixosModules.stylix

        {
        nixpkgs.overlays = [
          (final: prev: {
            unstable = import unstable {
                inherit (final) config;
                inherit (final.stdenv.hostPlatform) system;
                };
          })

        ];
        }
      ];
    };
  };
}

I'm running Proxmox 9 on a server with currently a single LXC running. On no apparent time schedule, within a day but frequently within an hour, the host will stop responding to SSH, pings and the web UI stops updating. However, the LXC continues to run happily. The only way to bring the host back up is to power cycle the server.

Has anyone got any troubleshooting tips?

2nd Edit: the problem was not the PSU but either the motherboard or the CPU. I installed a USB expansion card with an internal USB 3 header that has narrowed down the issue. I am aware that early Ryzen chips had issues with USB reliability, so maybe the Trixie update installed a new chipset driver that caused this. Either way I'm saving for an upgrade so hopefully won't be an issue too much longer.

Edit: I've now tested in other OSes and had the same issue. So it's probably just a poorly timed hardware issue.

Since I updated my desktop to Debian 13, my external SSDs (Over 1TB) are only detected by gnome-disks as "no media". They also bring down my other USB drives if I leave the unrecognised SSDs plugged in while trying to make other transfers. All these drives work in Debian 12 on my laptop.

I've checked dmesg for my external SSD:

`[ 1801.737164] usb 1-4: new high-speed USB device number 7 using xhci_hcd

[ 1801.909543] usb 1-4: New USB device found, idVendor=152d, idProduct=0580, bcdDevice= 2.14

[ 1801.909549] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 1801.909551] usb 1-4: Product: PX10

[ 1801.909552] usb 1-4: Manufacturer: SP

[ 1801.909554] usb 1-4: SerialNumber: 2405185321200000000D

[ 1801.946647] scsi host41: uas

[ 1801.947031] scsi 41:0:0:0: Direct-Access SP PX10 0214 PQ: 0 ANSI: 6

[ 1801.949657] sd 41:0:0:0: Attached scsi generic sg7 type 0

[ 1803.041153] usb 2-3: USB disconnect, device number 2

[ 1813.106975] sd 41:0:0:0: [sdg] Unit Not Ready

[ 1813.106981] sd 41:0:0:0: [sdg] Sense Key : Hardware Error [current]

[ 1813.106984] sd 41:0:0:0: [sdg] ASC=0x44 <>ASCQ=0x81

[ 1813.107229] sd 41:0:0:0: [sdg] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK

[ 1813.107232] sd 41:0:0:0: [sdg] Sense Key : Hardware Error [current]

[ 1813.107235] sd 41:0:0:0: [sdg] ASC=0x44 <>ASCQ=0x81

[ 1813.107549] sd 41:0:0:0: [sdg] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK

[ 1813.107552] sd 41:0:0:0: [sdg] Sense Key : Hardware Error [current]

[ 1813.107555] sd 41:0:0:0: [sdg] ASC=0x44 <>ASCQ=0x81

[ 1813.107631] sd 41:0:0:0: [sdg] 0 512-byte logical blocks: (0 B/0 B)

[ 1813.107634] sd 41:0:0:0: [sdg] 0-byte physical blocks

[ 1813.107872] sd 41:0:0:0: [sdg] Test WP failed, assume Write Enabled

[ 1813.107952] sd 41:0:0:0: [sdg] Asking for cache data failed

[ 1813.107955] sd 41:0:0:0: [sdg] Assuming drive cache: write through

[ 1813.108195] sd 41:0:0:0: [sdg] Preferred minimum I/O size 4096 bytes not a multiple of physical block size (0 bytes)

[ 1813.108198] sd 41:0:0:0: [sdg] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)

[ 1813.108560] sd 41:0:0:0: [sdg] Attached SCSI disk`

I'd assume the issue is corruption in my SSD, but it's happening with two different drives.