Playing with headers for over 3 hours now, if you got any hints, would appreciate it.Network Attached Storage, or NAS, is essentially a file server that hooks directly to your network. Still need to figure out why all local clients are seen with NGINX reverse proxy IP, but hey, I'm on the right track.

That being said, I didn't changed the proxy_pass from http to https. Curious how it worked when I had port forwarding done on my Firewall.ĮDIT2: 2nd problem also solved, as somebody here on Reddit said, the issue was between the chair and keyboard. If you guys can help out with these 2 issues, would be just great!ĮDIT: Problem 1 solved (the one with remote IP always being 127.0.0.1) - I had proxy_set_header outside of location block on NGINX, placing those lines inside, did the trick. I have certs set-up with certbot and nginx, also setup the pfx cert and placed it in plex, with no luck. If I set secure connections to 'required', android plex app, and web browser, cannot anymore access the web page, only through the windows client. What gives? Why is this happening and how can I fix it? It's not using plex relay, because from what I could see online, plex relay is limited to 1-2 MB/s max while I easily exceed this.Ģnd issue I have and I hope to find some answers here, is with the cert. Also, my public IP is never revealed, but this is not due to the tunnel itself.īack to my case: Everything is routed through the tunnel, and works fine, except one thing which is driving me crazy 🤪 - >all remote clients are seen with IP 127.0.0.1, as for local clients, everything works. Anybody else have this set-up? For those who don't, the answer to the'Why?' would be answered (from my perspective) with something like: Less opened ports on router, increased security.

My cloud plex