Heimdall VS Nginx Proxy Manager

The control panel is called Homepage. I like it more than Heimdall. To manage Docker I use Portainer.

You don't need to use heimdall with docker. You just need a working web server with PHP then install it from source: https://github.com/linuxserver/Heimdall Instructions are in the readme.

I prefer using Heimdall

There is a 3.x branch, but it hasn't been touched in about a year. Contrast that to the 2.x branch which was updated within the last week. Seems maybe there isn't any development on the 3.x branch.

Fo example, Heimdall is a dashboard, a polygon validator node, and an Android firmware flasher. All of which are quite popular projects

Heimdall - A homepage for self-hosted applications (like 'Homepage', but for people who prefer to do the config in the application, rather than editing .yaml files)

There is a more straightforward solution if it's all just for internal links. Set up something like heimdal. https://github.com/linuxserver/Heimdall

Heimdall: A homelab dashboard linking to all my services

Dispute configure heimdall correctly for your domain? There is a github issue about this: https://github.com/linuxserver/Heimdall/issues/362

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.