I had these sorts of issues too, always assumed it was something i’d goofed - but have never had similar with Caddy.

I used NPM as well, and eventually just got sick of various issues i’d had with it (probably all my fault, but…) so switched to Caddy and it was just so much easier and reliable for me. I’d heartily recommend it.

I put a passively cooled GT1030 in mine and its doing the decoding & tensorrt detection for 4x 1080p cameras just fine, based on its current load I expect I could add another 4.

I couldn’t tell you if that specific Amcrest camera will work, but I have 2 of the recommended ones on the frigate docs (https://www.amazon.com/gp/product/B083G9KT4C/) and they work.

Heh, mine’s not so different, multiple subnets - plus Wireguard :)

I don’t exactly know why but in the end it was definitely a inter-vlan connectivity problem I kept hitting. The pain was trying to prove it out as the official Nginx Proxy Manager container for unraid didn’t include anything like ping / traceroute etc.

I had a similar problem - the auto-renew didn’t work.

My setup had nginx proxy manager running on an unRaid box using macvlan network, and connected to unifi switching. What the problem was for me was the NPM box wasn’t able to get external network connectivity so like you I ended up reinstalling it all over again.

Problem kept happening, so in the end I just ditched it all & went CaddyV2 and (touch wood) so far no problems.

I haven’t got time to take a decent look at this right now, but will try to make time later today. But I had nightmares getting Nginx Proxy Manager to behave reliably on my unraid box - with Vaultwarden (among other things) as well coincidentally. And subsequently I ended up switching to CaddyV2 as it ended up being easier to get running and has (touch wood) so far been more stable.