Hi all,
I've setup NPM to replace the bulletin Synology RP and it isn't working as I would like it to do.
These are the steps I've taken so far:
Test 1: So when I try to access the subdomain from the outside e.g. baikal.mydomain.com I get access to the login-page. (that is good!)
Test 2: When trying to access the next subdomain (with Access List On) from the outside e.g. vaultwarden.mydomain.com I get the 403 Forbidden page (that is good!)
Test 3: When I remove the subdomain from the bulletin Synology RP I cannot connect anymore using my subdomains within my LAN Network e.g. vaultwarden.mydomain.com goes to the webstations webpage (see screenshots).
Test 4: Re-entering the subdomain in Synology's RP connecting to a subdomain within my LAN works!
Any idea what I'm doing wrong?
TIA
I've setup NPM to replace the bulletin Synology RP and it isn't working as I would like it to do.
These are the steps I've taken so far:
- Port-forwarding 80 and 443 to Host (Nas where Docker NPM is running) 80:8080 and 443:44300
- Open 8080 and 44300 in Firewall
- Setup NPM with Access List for some subdomains to allow LAN ONLY access
- Setup NPM proxy hosts for subdomains with SSL (imported my wildcard LE Cert) and some subdomains with LAN ONLY access
- Testing
- Remove the subdomain enteries for Synology RP
Test 1: So when I try to access the subdomain from the outside e.g. baikal.mydomain.com I get access to the login-page. (that is good!)
Test 2: When trying to access the next subdomain (with Access List On) from the outside e.g. vaultwarden.mydomain.com I get the 403 Forbidden page (that is good!)
Test 3: When I remove the subdomain from the bulletin Synology RP I cannot connect anymore using my subdomains within my LAN Network e.g. vaultwarden.mydomain.com goes to the webstations webpage (see screenshots).
Test 4: Re-entering the subdomain in Synology's RP connecting to a subdomain within my LAN works!
Any idea what I'm doing wrong?
TIA