adguard-sync VS Nginx Proxy Manager

Shameless plug, since DNS becomes very important, I wrote a tool that you can run 2 separate AdGuardHome instances on 2 separate VMs but keep them in-sync. This gives you redundancy in case your primary goes down: https://github.com/atoy3731/adguard-sync

I have primary and secondary AGH VMs (AGH running in docker) and shameless plug, use my sync tool so I only have to update my primary. They both upstream to 1.1.1.1 for anything non-local. I then have my router's upstream DNS pointing to my primary and secondary to give me some redundancy.

To that point, another shameless plug, but if you go the AGH route, I wrote a sync tool that'll let you dynamically copy changes from a primary to a secondary instance of it. That way if for whatever reason if one goes down, you can point your router to both and hopefully still be fine.

https://github.com/atoy3731/adguard-sync found this? Might wanna look at it.

Adgaurd makes it easy to set up multiple instances of you dns using the adguard-sync tool.

I discovered these 3 amazing projects recently:

Cryptpad, essentially google docs/sheets/forms e2e encrypted. It does include collaboration. https://github.com/cryptpad/cryptpad

Immich, google photos self hostable, with share options https://github.com/immich-app/immich

Nginxproxymanager manages certificates and proxies to self hosted stuff through nginx https://github.com/NginxProxyManager/nginx-proxy-manager

Great self hosting stuff!

Nginx Proxy Manager

Take a look at NginxProxyManager. This would give you the opportunity to put everything in the form of service1.domain.com , service2.domain.com ,etc.

Prime example: Nginx Proxy Manager is often recommended in the sub. The latest minor release came with breaking changes (so already ignoring semver). I bet you many people were running on latest and then had broken stuff: https://github.com/NginxProxyManager/nginx-proxy-manager/releases/tag/v2.10.0

I started looking into how to make add dynamic IPs to NPM access lists. I came across a couple of GitHub issues (1, 2) on the topic. It looks like people have solved the problem, but not in a complete way without modifying the NPM docker image. I did not want to do that, so decided looking into writing a separate script.

Here is the (NPM) GitHub issue where the "fork of a fork" image came into existence (lepresidente/nginx-proxy-manager). It has some interesting discussions about the challenges of having NPM and CrowdSec coexist and cooperate.

Agree with this, myQ is such a dumpster fire. It needs to have an the ability to be managed over the local network instead of requiring the garage door and app connect to their server.

My very first experience with myQ was figuring out that their IP blocklist provider, brightcloud, blocks anything with the word "proxy" - including the default "it works" page for Nginx Proxy Manager [1]. And they have no way of overriding this to actually provide service if someone turns out to be a legitimate customer.

[1]: https://github.com/NginxProxyManager/nginx-proxy-manager/dis...

Edit: If you're using Nginx Proxy Manager there seems to be open PR for support for proxy protocol https://github.com/NginxProxyManager/nginx-proxy-manager/pull/1882 however in the comments there's a name of repository with this PR merged.