Remote access solved with NGINX Proxy Manager

Plex Media Server Remote Access
,
43

most important thing (and I still do not understand why) is that a DDNS is not enough. it only points to your IP. this cannot be SSL secured. so you need a CNAME domain that is pointing there. that can be SSL certified, so you can use the port 443 route.

44

Sory for the late replay, been a crazy week!

I guess you could try and do it with a unfriendly DDNS name and it should work (for some reason I have this niggle in the back of my mind there is a requirement form LE as to why this may not work). On another point, if you’re sending a invite to your mother to share 1998 xmas video, would it be better to send plex.yourson.surf or 3456ibus.asusausrouter.io?

I personally have one DDNS name and I use with differing ports at my NPM for service. My firewall allows inbound 443/80 and then this hits the NPM and there the traffic is routed based on URL and internal port. I have different services hosted like WordPress websites, Plex and so on.

45

does anybody know why my reverse proxy sends me to router login instead of plex inside my home network? from outside it is not even accessible now. worked yesterday. only thing I changed was turn on PiHole on another Virtual machine and tell the router to use it as DNS.

46

This has nothing to do with this topic, to be clear. Your router must have admin login external enabled (any chance it’s an Asus router?), which will take all 443 traffic and point it at itself and ignore any other 443 forwarding. I turn that off, purely from a security perceptive its dangerous as hackers with out mfa or 2fa enabled could password spray attack and hack your firewall.

Secondly PiHole will manager your DNS for you internally (assuming you’re using as your DNS manager), in PiHole go to local DNS and added a DNS record for your plex.domain.com URL to your NPM IP and you should be golden :wink:

Good luck

1 Like
47

Hi,
I followed this and am able to access this from the browser outside the network. But not from the app. Why is that? Should I change something in Android app?

1 Like
No remote access using Android Apps
48

Maybe clear the cache, and/or delete the app and reinstall.

49

Hello, I have Dietpi (Debian Bullseye, intel x64, Mini-PC) I install Nginx Proxy Manager. I make ports forwarded like this:

External ports:           Host/IP:                             Internal ports:
80-80                        192.168.0.19                        8080-8080
443-443                                                                   4443-4443

I install Nginx Proxy Manager with:

version: '3'
services:
  nginx-proxy-manager:
    image: jlesage/nginx-proxy-manager
    network_mode: host
    volumes:
      - "/home/dietpi/.config/nginx-proxy-manager:/config:rw"

I have Plex, Nextcloud, Home Assistant installed with dietpi-software center.
I have Petio installed with docker-compose.
I set in Nginx Proxy Manager Home Assistant as main address because it don’t support subfolders.

  1. New Proxy Host.
Details tab:
shema:http       host/IP:  127.0.0.1     port: 8123
Custom locations:
- location: /petio
shema:http       host/IP:  127.0.0.1     port: 7777

- location: /plex
shema:http       host/IP:  127.0.0.1     port: 32400

-location: /nextcloud
shema:http       host/IP:  127.0.0.1     port: 80

I disable all things I now on lighttpd and nextcloud not to use SSL but when I start https://myserver.ddns.net I get placeholder page for lighttpd.
When I use https://myserver.ddns.net/nextcloud/ it works. Also Petio works that way but not Home Assistant and Plex.
Can somebody help me?
Regards.

50

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.