Kaizac

I'm trying to use the Cloudflare DNS + HTTP proxy which I can't seem to get working as I want. What I have is a Let's Encrypt set up, in Cloudflare I created CNAME's which redirect to my DuckDNS domain. When I put off the proxy mode in Cloudflare my personal domain and subdomains resolve to the right dockers. However, when I put on the HTTP proxy in Cloudflare, the (sub)domain can't resolve anymore. Should what I'm trying to do work, or is it impossible? I'd prefer not to put my WAN IP out in the open, so the HTTP proxy would be very useful.

Thanks for that, that works!

I run airsonic on a subdomain and with Lets Encrypt reverse proxy I have to use airsonic.domain.com/airsonic to access the login page. Removing the context path in the template solves this problem, but it returns after every update. Is there something I can do to fix this permanently?

That only works with a Plex Pass AFAIK, which I do not have. And since I also have Nextcloud I would like to be able to limit it from within NGINX (or maybe there is an other and better solution).

I would like to limit the upload speed of my server to the outside world for specific dockers. Is this possible to do? I'm currently running Nextcloud and Plex for which I would like to limit the upload speed. I've found some articles about rate limiting in NGINX, but I can't make much sense of it to apply it. Would be nice to make sure other people are not collapsing my full bandwidth.