Need help Port Forwarding/Firewall/Virtual Server

Zitat von Morlan

He could choose duckdns as a validation method. Then only a port forward of port 443 is needed. The port should be available if you don't use omv gui over ssl (which can also be changed). So it would be an easy port forward 443->443. The config of letsencrypt would need to be changed accordingly.

I've went through that stack line by line, it's right.

I just took down my personal nextcloud and fired up vbox. After redirecting the ports to my virtual machine, I had "mycloudtest.duckdns.org" up in in about 10min.

version: "2"
services:
  nextcloud:
    image: linuxserver/nextcloud:latest
    container_name: nextcloud
    environment:
      - PUID=1000
      - PGID=100
    volumes:
      - /srv/dev-disk-by-label-VirtualDisk/AppData/nextcloud:/config
      - /srv/dev-disk-by-label-VirtualDisk/VDisk/Media/.Nextcloud:/data
      - /etc/localtime:/etc/localtime
    depends_on:
      - mariadb
    ports:
      - 449:443
    restart: unless-stopped
  mariadb:
    image: linuxserver/mariadb:latest
    container_name: nextclouddb
    environment:
      - PUID=1000
      - PGID=100
      - MYSQL_ROOT_PASSWORD=my_password
    ports:
      - 3306:3306
    volumes:
      - /srv/dev-disk-by-label-VirtualDisk/AppData/nextclouddb:/config
      - /etc/localtime:/etc/localtime
    restart: unless-stopped
  duckdns:
    image: linuxserver/duckdns
    container_name: duckdns
    environment:
      - PUID=1000
      - PGID=100
      - SUBDOMAINS=mycloudtest
      - TOKEN=My-Token
    volumes:
      - /srv/dev-disk-by-label-VirtualDisk/AppData/duckdns:/config
      - /etc/localtime:/etc/localtime
    restart: unless-stopped
  letsencrypt:
    image: linuxserver/letsencrypt
    container_name: letsencrypt
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=100
      - URL=duckdns.org
      - SUBDOMAINS=mycloudtest
      - VALIDATION=http
      - EMAIL=myemail@gmail.com
      - ONLY_SUBDOMAINS=true
    volumes:
      - /srv/dev-disk-by-label-VirtualDisk/AppData/letsencrypt:/config
      - /etc/localtime:/etc/localtime
    depends_on:
      - duckdns
    ports:
      - 450:443
      - 90:80
    restart: unless-stopped

The only thing different on his, is he's on a 192.168.0.xxx vs me being on 192.168.1.xxx, so it has to be some sort of port issue between whatever 2 devices those are.

I just realized in that first stack, I didn't put a duckdns volume. I don't think it would be causing this issue however, as it would have just written the volume to the container, but I just edited it in.

Zitat von Morlan

I did not question your configuration. Maybe the port redirection just don't work on that router. That's why I proposed the alternative config.
I will provide a stack when I get home.

It's just weird... I've set up Nextcloud more times than I really care to think, and I don't think I've ever had a significant issue (mostly during testing of omv 5, etc.).

I still can't understand why you're having issues... your settings are right.

I wonder if a firmware update might be in order for the router, the image gives the firmware version as 1.09 but the D-Link site does display a later version.

Port forward also gives a how to on port forwarding for this router

Yeah I saw that but Port forward suggests that whatever you are forwarding too the server should have a static ip.

The failure points to networking, or as you have suggested stale configs.