help setting reverse proxy with nginx proxy manager with duckdns

Roeegg2o · Mar 15th 2023

Hey,

I'm trying to make my NAS server WAN accessible, and so I'm trying to set up a reverse proxy using nginx proxy manager, but I'm lost and don't really know what to do.

I've gotten a domain from duckdns.org, and successfully added a Docker container running duckdns and a container running nginx proxy manager, and even created a proxy host successfully from the nginx proxy manager webgui but it doesn't work and I'm feeling lost.

Is there something I should change in OMV settings? Any good guides on doing this?

chente · Mar 15th 2023

Quote from Roeegg2o

I'm trying to make my NAS server WAN accessible,

What service do you want to access exactly? Or do you want to access your entire LAN network?

Roeegg2o · Mar 15th 2023

I don't want to expose my OMV web administration page, qbittorrent, etc but i do want to have Nextcloud and Jellyfin accessibly from anywhere.

chente · Mar 15th 2023

Quote from Roeegg2o

i do want to have Nextcloud and Jellyfin accessibly from anywhere.

This will go very well with nextcloud

Thread

[How-To] Nextcloud with swag (Letsencrypt) using OMV and docker-compose

Docker Container set up by this method can be managed by Portainer or from CLI.

Pre-requisites
In order to be able to reach nextcloud from the internet you need an external IPv4 address and a hostname.
Regarding external IPv4 address check you router or ask your internet service provider.
To register a hostname you can use services like duckdns, selfhost.eu, strato.de or many others.
Make sure to use strong passwords!!!

Preparation

Install and fully update OMV (a restart might be needed if the kernel

…

macom

Aug 10th 2019

Maybe this will help you too, depends on what you are looking for

Thread

[How-To] Web services using Swag (Proxy) in docker

Installation of swag (reverse proxy) in Docker. This will allow access to local services from the internet through an protected connection.

August 2023.
Warning. I've stopped using swag so I no longer maintain this guide. Some concepts might be outdated, make sure everything is still valid in the official swag documentation.

SWAG (Secure Web Application Gateway) configures an Nginx web server and reverse proxy with php support and a built-in certbot client that automates the free SSL server

…

chente

Dec 26th 2021

BernH · Mar 15th 2023

Have you done the port forwarding in your router?

You need to port forward ports 80 & 443 to the server running nginx proxy manager or swag.

If you are staying with nginx proxy manager, you then just set up the host in there to point to the server and port of your services.

for example:

- Lets say your duckdns domain is domain.duckdns.org

- if your server is using the ip address 192.168.0.200, port froward 80 & 443 to 192.168.0.200

- If your services are running in docker, place nginx proxy manager on the same docker network that the services are using.

- in nginx proxy manager set a host to direct traffic to http://jellyfin:8096 for jellyfin and http://nextcloud:80 (if you are using port 80 for the OMV web GUI, set nextcloud to use a different port)

- in nginx proxy manager get and assign ssl certificated for the two services and enable the option to force ssl. (nextcloud also likes to have hsts enabled)

- if you have services running in virtual machines or other computers, you can substitute the appropriate ip address for the machines instead of jellyfin or nextcloud

- you then access the services from the internet by the full addresses jellyfin.domain.duckdns.org or nextcloud.domain.duckdns.org

a further note about nextcloud. If you want to be able to generate share links when at home, nextcloud needs to be accessed by it's internet address, which you can't do from home unless you are also running a local DNS service like pihole for example or you edit your computer's hosts file to direct nextcloud.domain.duckdns.org to the ip address of the server. Local DNS is a little better as it can also work woth mobile devices on your network if your DHCP server is using the local DNS as its DNS provider.

Roeegg2o · Mar 15th 2023

Quote

Maybe this will help you too, depends on what you are looking for

Thread
[How-To] Web services using Swag (Proxy) in docker
Installation of swag (reverse proxy) in Portainer. This will allow access to local services from the internet through an protected connection.

SWAG (Secure Web Application Gateway) configures an Nginx web server and reverse proxy with php support and a built-in certbot client that automates the free SSL server certificate generation and renewal processes (Let's Encrypt and ZeroSSL). It also contains fail2ban for intrusion prevention.
This image supports x86-64, arm64, and armhf architectures.
…

chente
Dec 26th 2021

Display More

First of all, thank you so much for this tutorial, it really helped me understand in general what im supposed to do.
I got stuck on step 4. I get this output when writing "docker logs -f swag":

Code

"Certbot failed to authenticate some domains"
"Fetching http://my_domain.duckdns.org/.well-known/acme-challenge: Timeout during connect (likely firewall problem)

(switched the my_domain for my actual domain)

macom · Mar 15th 2023

You mixed internal and external. External has to be 80 and 443.

Roeegg2o · Mar 15th 2023

Quote from macom

You mixed internal and external. External has to be 80 and 443.

Oops..
Changed it now but still doesnt work (same error)

macom · Mar 15th 2023

Did you restart swag?

Is the IP .188 the one of the host where docker is running?

Roeegg2o · Mar 15th 2023

yeah

macom · Mar 15th 2023

Did you check the link in the guide

Troubleshooting Letsencrypt Image Port Mapping and Forwarding | LinuxServer.io

Roeegg2o · Mar 15th 2023

still doesnt work
I get an error that "Certbot does not exist"

KM0201 · Mar 15th 2023

Well, first.. you don't need jellyfin forwarded if you're going to use swag.

The error suggests your port fowarding is wrong, but from your router pics, it looks right. Do you have a software firewall running that may be blocking these ports? Have you done some custom configurin with iptables maybe?

Roeegg2o · Mar 15th 2023

There's no special changes from what I can see... Maybe im wrong though...
I also got the error "certbot does not exist". maybe its something to do with that?

I don't know if this is related to the problem, but i see there is no 'letsencrypt' folder in var/logs

KM0201 · Mar 15th 2023

Quote from Roeegg2o

There's no special changes from what I can see... Maybe im wrong though...
I also got the error "certbot does not exist". maybe its something to do with that?

I don't know if this is related to the problem, but i see there is no 'letsencrypt' folder in var/logs

No, it's saying certbot failed to authenticate in the error...

Can you ping your domain?

ping -c5 your-domain.duckdns.org

Roeegg2o · Mar 15th 2023

yep

KM0201 · Mar 15th 2023

Can you post your swag stack without your email, domain, and token

Roeegg2o · Mar 15th 2023

Also added the log file

KM0201 · Mar 15th 2023

Quote from Roeegg2o

Also added the log file

Your stack is not correct.

Hold on, let me get you a proper one.

KM0201 · Mar 15th 2023

Code

version: "2.2"
services:
  swag:
    image: ghcr.io/linuxserver/swag
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=YOUR_PUID
      - PGID=YOUR_PGID
      - URL=YOUR_SUBDOMAIN.duckdns.org
      - SUBDOMAINS=wildcard
      - VALIDATION=duckdns
      - DUCKDNSTOKEN=DUCKDNS_TOKEN
      - TIMEZONE=YOUR_TIMEZONE
      - EMAIL=YOUR_EMAIL@email.com
    volumes:
      - /Your/Path/swag:/config
    ports:
      - 444:443
      - 81:80
    restart: unless-stopped

Display More

Adjust as necessary

Your specific issue are these two lines. Since you posted a pic,... (which is absolutely worthless by the way, use a codebox) I can' t cut and paste it...

Code

 - URL=YOUR_SUBDOMAIN.duckdns.org
 - SUBDOMAINS=wildcard

You have to define a subdomain in your URL section, or you can't pull a cert (as you are experiencing.

If you've set multiple subdomains in your duckdns account you want to use, add this envinronment variable:

Code

 EXTRA_DOMAINS= subdomain1,subdomain2,etc

This would then pull a cert for subdomain1.duckdns.org, subdomain2.duckdns.org,, etc. duckdns allows you a max of 5 subdomains.

help setting reverse proxy with nginx proxy manager with duckdns

ryecoaaron Mar 15th 2023

Participate now!

Tags