plex-nginx-reverseproxy VS Nginx Proxy Manager

I ended up resetting my nextcloud AIO, following those instructions to the master container and NGINX, then restoring my backup. All good letting nginix handle it now and have plex working properly and securely now. using this https://github.com/toomuchio/plex-nginx-reverseproxy

Cache is disabled, everything is setup accordingly, using this for my nginx config in an attempt to fix performance but nothing.

I have been using a reverse proxy setup for close to two years. I use the nginx config shown in this github. I have configured it all to my local setup with the correct certification files from certbot and have recently renewed the certificates.

This is the universal nginx config 80% of nginx/plex users default from.

I have the same setup, a VPS that proxies through a Wireguard tunnel to my NAS that runs plex. I am using nginx with this config file https://github.com/toomuchio/plex-nginx-reverseproxy

yeah... sadly not getting much information outta there. Was hoping for some CSP errors. Go check out the general nginx config for plex. Maybe that'll help you.

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.