Configuring Multiple Self Hosted Server Applications To be Accessible From Anywhere Using External Website

Zitat von DanTheTechMan

Here is the docker-compose file I used to get SWAG up and running:

You can't have a YML for SWAG with just a SUBDOMAIN as you have.

From what I read, you have been doing things your way so, it will be difficult to help sort things out.

The most basic way to run SWAG as a reverse-proxy is giving it the control of the HTTPS server.

For this to work, your DUCKDNS domain need to point to your WAN IP and you need a router portforward from WAN 443 to OMV LAN IP 444.

And this is the only port that you need to open to the outside world.

Then, the YML need to be like this (I only copy and edited what need to be edited. Since you pasted without IDENTs, you will have to fix it)

---
services:
swag:
image: lscr.io/linuxserver/swag:latest
container_name: swag
cap_add:
- NET_ADMIN
environment:
- PUID=1002
- PGID=100
- TZ=America/New_York
- URL=xxxxxxxxxxxxx.xxx # This is the subdomain you have + .duckdns.org
- VALIDATION=duckdns
- SUBDOMAINS=wildcard
- EMAIL=xxxx@email.com # NOT OPTIONAL. YOU NEED A VALID EMAIL FOR REVALIDATION
#- EXTRA_DOMAINS=xxx.xxxxxxxxxxxxx.xxx,xxxxxxx.xxxxxxxxxxxxx.xxx # WHATFOR???
- DUCKDNSTOKEN=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
volumes:
- /var/lib/docker/appdata/swag/config:/config
ports:
- 444:443
#- 8080:80 #NOT NEEDED FOR DNS VALIDATION
restart: unless-stopped

As said above, having the config volume on the root OS is bad.

Although SWAG is a simple container, if you lose the config folder and you have proxy samples edited (as you will need since you have services running outside of docker), you will have to redo them again.

Once the SWAG is launched (as I made it above), you will have HTTPS access to it via https://www.<YOUR.SUBDOMAIN>.duckdns.org

When it is done, I can tell you the rest.

Zitat von DanTheTechMan

I have Emby, which is installed directly on the host, not through docker. The website is hosted through a domain provider, not on my NAS. So I need a way to link Emby and the other application to my website, which is why I have DuckDNS.

???

Website hosted on a domain provider?

Emby on host?

For what is the website running? Or it's just a web domain that point's to your WAN ip?

If you have EMBY installed AND running on your OMV host, and you don't mind having a sub.sub-domain.duckdns.org (4 words) website, duckdns is all you need.

Something is a bit weird here. It sounds as if you had a domain like domain.com and additionally you use duckdns for NAS services?

Zitat von DanTheTechMan

What are the next steps?

Do you see a secured https://www.<YOUR-SUBDOMAIN>.duckdns.org swag Park webpage?

Zitat von DanTheTechMan

Unfortunately, no. What's strange is when I load the HTTP variant of my DuckDNS URL I get my OMV login page, however when I load the HTTPS variant, I get ERR_CONNECTION_REFUSED in my browser.

Recheck the portforwards you have on the router.

The only one required is from WAN 443 to OMV LAN IP 444.

Zitat von DanTheTechMan

That's correct. I'm basically trying to link the two (make certain applications running on my NAS accessible via subdomains on my main website).

Ok so I don‘t get why you would do that. Duckdns is basically sth you use when you’ve got no ‚real‘ domain at all. When I wanna add sth. like emby.domain.com I go to my domain company dashboard and add a dns entry that points to my NAS.

Also I wonder what your website has to do with that. When my website is hosted somewhere else I go to domain dashboard and add a entry for eg. http://www.domain.com that simply points to where the website is..

Still don’t get where I would bring duckdns into play. It just sounds really weird while your needs and ‚what you want to achieve‘ sounds quite common at the same time.

Zitat von HannesJo

Ok so I don‘t get why you would do that.

I don't either.

For now, the idea is to make services available via swag/duckdns.

Once everything is running, changing to only webdomain, is easy (although I see no advantage other thatn having a 3 name URL instead of 4).

Between using duckdns or a paid hosted name, I still use the duckdns.

If using a free webhost is a concern, then you can always add cloudflare to reduce that concern.

But only duckdns is more than enough.

Not sure if this topic is resolved or not but I have been working on something similar (I think) and have it all working. Here is what I have done and I hope it is some help.

1. get swag (docker container) running on OMV with duckdns as the DDNS / SSL provider - see compose below (and note the

SUBDOMAINS=wildcard ENV variable as this is important)

2. start swag and check it starts up and generates the ssl cert (should see 'server ready' at end of start log)

3. setup port forwarding of tcp 443 to OMV on your router so that you can access from outside (and inside) of your LAN

4. test you see the swag web holding page from outside of your LAN using https://<your-sub-domain>.duckdns.org

Once you have got the above working, then you can start to work through reverse proxies to either dockers or other hosts on your LAN. I have one setup for home assistant (docker) and another for a proxmox host server on my network. To do this you need to create reverse proxy config files for each service you want to access either on the LAN or externally.

Importantly when you create/edit these config files you need to make sure they end with .conf (not .conf.sample)

1. create or rename reverse proxy files in the docker swag config (e.g. appdata/swag/nginx/proxy-confs) - see example below

2. restart the swag docker container to 'enable' the config changes

Hope this helps. Example compose for swag and proxy config file below.

Compose file for swag docker on OMV - using the default docker bridge network config.

 services:
  swag:
    image: lscr.io/linuxserver/swag
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - URL=<sub-domain>.duckdns.org
      - SUBDOMAINS=wildcard
      - VALIDATION=duckdns
      - DUCKDNSTOKEN=xxxxxxxxxx
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /symlinks/omv-system/appdata/swag:/config
    ports:
      - 443:443
##      - 80:80
    restart: unless-stopped

Proxy file - to access the web interface for proxmox server on my network.

This will provide access to proxmox web interface using https://macmini.<your-sub-domain>.duckdns.org

It basically forwards to my proxmox server IP using https on port 8006

# make sure that your dns has a cname set for proxmox if not using IP address

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name macmini.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {

        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app 192.168.100.119;
        set $upstream_port 8006;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    }
}