Only two devices can reach my nextcloud.local instance

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, , , ,
1

I’ve been troubleshooting this issue for a few days now, and I’m pretty stumped.

Setup

  • Latest version of Nextcloud AIO in Docker on my Raspberry Pi (has a static IP, let’s say it’s 192.168.1.100)

  • NGINX Proxy Manager with a proxy host that routes nextcloud.local to http://192.168.1.100:11000. The scheme is HTTP, Block Common Exploits and Websockets Support are enabled. An SSL Cert is attached, and Force SSL and HTTP/2 Support are enabled.

  • Another proxy host routing aio.nextcloud.local to http://192.168.1.100:8080. The scheme for this one is HTTPS, both Block Common Exploits and Websockets Support are enabled.

  • Manual DNS entries on my Verizon router for the AIO and main page; the previous mentioned domains both pointing towards 192.168.1.100.

  • I have a Dynamic DNS on FreeDNS that points to my network’s public IP. Let’s say it’s example.domain.sx, I used that as the domain when Nextcloud AIO asked during the setup.

    • I could not access nextcloud.local anywhere until I made the SSL Cert on NGINX Proxy Manager using this domain.

  • Nextcloud AIO compose:

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

networks:
  proxy:
    external: true
  aio-backend:
    driver: bridge

services:
  nextcloud-aio-mastercontainer:
    image: nextcloud/all-in-one:latest
    container_name: nextcloud-aio-mastercontainer
    init: true
    restart: always
    ports:
      - "8080:8080"
    environment:
      APACHE_PORT: "11000"
      APACHE_IP_BINDING: "0.0.0.0"
      APACHE_ADDITIONAL_NETWORK: "proxy"
      SKIP_DOMAIN_VALIDATION: "true"
      NEXTCLOUD_MOUNT: "/media/pi/OS"
      NEXTCLOUD_DATADIR: "/media/pi/OS/Nextcloud"
    networks:
      - proxy
      - aio-backend
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /media/pi/OS/Nextcloud/Skeleton:/mnt/skeleton

The two devices that are able to access nextcloud.local have a NextDNS private DNS server, which I’ve set to route all .local domains to 192.168.1.100.

I’m just lost. I don’t know what’s missing that’s stopping any other device on the network from accessing these sites.

  • https://192.168.1.100:11000 gives me the "This site can’t provide a secure connection ERR_SSL_PROTOCOL_ERROR.
  • http://192.168.1.100:11000 gets redirected to nextcloud.local/login correctly, but here I get a “This site can’t be reached DNS_PROBE_POSSIBLE”.

Would it make any difference if I used my Verizon router’s built-in Dynamic DNS capability? Any clues or extra help would be greatly appreciated!