Problem to get reverse proxy to work, what could be wrong

[krfinstad79]

Hi,

I've never done this before, so I need some tips on how to proceed. Thanks for your help.

I am running Nginx proxy manager as a docker on my Qnap nas.

Did use this docker compose ->

version: '3.8'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '8180:80' # Map QNAP's port 8080 to container's port 80 (HTTP)
- '8443:443' # Map QNAP's port 8443 to container's port 443 (HTTPS)
- '8181:81' # Map QNAP's port 8181 to container's port 81 (Admin UI)
volumes:
- /share/CACHEDEV1_DATA/Docker/nginx/data:/data
- /share/CACHEDEV1_DATA/Docker/nginx/letsencrypt:/etc/letsencrypt

Created domain from Duck DNS and point it to the local QNAP ip.

Added the SSL certiicate in Nginx ->

Proxy host added in Nginx ->

Then i added SSL certificate to the proxy host ->

If i try to open site from Nignx it just say the sites can´t be reached.

If I enter the full DNS name and port number and http, I get the page opened. Where it says that it is not secured. But if i try to open it from https:// and port number it says the site can´t be reached.

Used this video for guidance https://www.youtube.com/watch?v=qlcVx-k-02E

If anyone can help me get going I would be grateful. Thank you for your help.

[OnlineProxy-io]

Looks like you're having some trouble getting to your site over HTTPS on your QNAP NAS with Nginx Proxy Manager. No worries, here’s how to sort it out - First up, in your Docker Compose, make sure you’re mapping port 8443 to 443 - that’s how HTTPS traffic gets through. Then try hitting up your site at https://yourdomain.duckdns.org:8443. Next, double-check your router’s port forwarding. You want port 80 going to 8180, and 443 heading to 8443 on your NAS. This lets the outside world actually reach your NPM container. In the NPM admin panel, add a new proxy host, tick the SSL box, force HTTPS, and request that Let’s Encrypt cert. It’s all pretty straightforward in there. Last thing - don’t forget to peek at your QNAP firewall settings. Sometimes they sneakily block Docker traffic, and that’ll mess with everything.