Beiträge von Mapluil

Zitat von Zoki

I think I see where the problem is:

You are forwarding our public IP (80,443) to 192.168.25.21 (90, 450) which is the nginx proxy manager

Then you ask the nginx proxy manager to forwart 192.168.25.21 (90, 450) to 192.168.25.21 (90, 450) (this is a loop, making nginx proxy manager forward to itself)

nginx proxy manager should forward to 192.168.25.21:443 (which is nextcloud) You do not have a http port for nextcloud.

But setting up swag with a tutorial supported here is the better idea.

The guide is here: [How-To] Nextcloud with swag (Letsencrypt) using OMV and docker-compose

Alles anzeigen

Thank you Zoki. I'll try this tutorial and the port modification you suggested.

Zitat von Soma

Mapluil

Looking at your portainer, I can only guess that you used/follow a "DBTech guide" (I recall some showing the different steps for Nextcloud and then adding Nginx Proxy Manager).

Sorry but for me this is confusing and I can't see/understand the interactions between the several stacks.

Speccially, between NPM and the stack of Nextcloud.

Most people here use SWAG or Traefik, instead of NPM.

NPM is using a DB just for it and then you have another instance of mariaDB (running with port 41953) for Nextcloud.

And, more confusing is why you're using 2x domains with duckdns.org on NPM.

If you want to access to Nextcloud from WAN, you should only be using HTTPS.

Again, I don't have any experience with NPM other than I gave up trying to use it since SWAG is more straight-forward (for me, at least)

If you can/want to start fresh and change to SWAG, say so and we can guide you easely to try to solve your problem.

Alles anzeigen

I appreciate your help. I'd like guidance to configure openmediavault with nextcloud and swag. Can you point me to a tutorial that I can follow?

Zitat von Zoki

Both domains resolve to 187.58.72.151 Is this correct for today?

Because there is no response to ping, http or https.

That's right. It's my current public IP.

Zitat von Soma

Post your YML in a codebox and some screenshot of your portforward of the router.

Hide any sensible data

version: "3"
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      # These ports are in format <host-port>:<container-port>
      - '90:80' # Public HTTP Port
      - '450:443' # Public HTTPS Port
      - '81:81' # Admin Web Port
      # Add any other Stream port you want to expose
      # - '21:21' # FTP
    environment:
      DB_MYSQL_HOST: "db"
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: XXXXXX
      DB_MYSQL_PASSWORD: XXXXXX
      DB_MYSQL_NAME: XXXXXX
      # Uncomment this if IPv6 is not enabled on your host
      # DISABLE_IPV6: 'true'
    volumes:
      - /srv/dev-disk-by-uuid-735354fd-0573-48ef-8570-6c519475f6ab/docker/nginx-proxy-manager/data:/data
      - /srv/dev-disk-by-uuid-735354fd-0573-48ef-8570-6c519475f6ab/docker/nginx-proxy-manager/letsencrypt:/etc/letsencrypt
    depends_on:
      - db

  db:
    image: 'jc21/mariadb-aria:latest'
    restart: unless-stopped
    environment:
      MYSQL_ROOT_PASSWORD: XXXXXX
      MYSQL_DATABASE: XXXXXX
      MYSQL_USER: XXXXXX
      MYSQL_PASSWORD: XXXXXX
    volumes:
      - /srv/dev-disk-by-uuid-735354fd-0573-48ef-8570-6c519475f6ab/docker/mariadb/data/mysql:/var/lib/mysql

Nginx Proxy Manager

Portainer

Router

I think I didn't express myself well, but the problem is not my IP update in duckdns. I checked and the container I installed to do the IP updates is working normally. I believe that the problem is with the configuration of ports on my network, but I honestly don't know how to fix it.

Good night,

I have a NAS working with openmediavault, nextcloud, nginx proxy manager and duckdns. In my internal network everything works perfectly, however when I try to establish the external connection I am facing an annoying problem. When my ISP updates my external IP, my duckdns subdomains are able to reach the server, but after some time, the url no longer resolves. When my ISP makes a new update of my IP, I can again access my server externally, and the access is interrupted again shortly after. Even with external access interrupted, I can ping my subdomains through the terminal, but in the browser the pages are not displayed. Does anyone have an idea what it could be? Thanks.