documentation VS Nginx Proxy Manager

I can't say I have used the documentation that much, to me most of this things are self explanatory, you should check it to see for yourself, there's a users and administration manuals: https://docs.nextcloud.com/

I see this change to the docs was made a month ago, but there's no explanation for the new requirement. Meanwhile I'm running NextCloud 24 on a Raspberry Pi running Buster, and I'm worried about upgrading to Bullseye because Raspberry Pi themselves don't recommend it:

I think you need to refer to the manual and deduct from your configuration files where the data is stored.

You do know that Nextcloud provides some excellent documentation, right? No need to watch someone's youtube video. https://docs.nextcloud.com/

That was over a year ago. Then they said "we'll fix it in a better way". Ok, nothing wrong with that. But that never landed, and by now it is "32 bit is deprecated, so we won't fix it" - at least that is how I understand this

I just noticed https://github.com/nextcloud/documentation/pull/9071 and I am a bit worried: does this mean Nextcloud is officially dropping 32 Bit support?

The problem is service discovery. If you use a reverse proxy (nginx proxy manager in my case), then you need to add a redirecting code. 1. https://help.nextcloud.com/t/caldav-and-carddav-ios-issues/73801/4 2. https://github.com/nextcloud/documentation/pull/8318 3. https://docs.nextcloud.com/server/latest/admin\_manual/issues/general\_troubleshooting.html#service-discovery 4. https://help.nextcloud.com/t/caldav-and-apple-impossible-to-use-caldav-with-mac-and-ios/91560/5 5. https://docs.nextcloud.com/server/latest/admin\_manual/installation/nginx.html 6. https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2093 Note: Browser redirection works, but for iOS clients you must set up the rules in the reverse proxy manager, otherwise it will just refuse to redirect for some reason. You can also just manually enter the redirected address if you need a quick fix.

Documentation source is here https://github.com/nextcloud/documentation

Why trafik over nginx for my modest needs, a couple docker hosts and a few dozen containers. I use https://github.com/NginxProxyManager/nginx-proxy-manager, would trafik provide a benefit on such a small scale?

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.