I've read and re-read the following  https://github.com/nextcloud/all-in-one/blob/main/local-instance.md

It seems clear, but I'm missing something.  Because I cannot get passed the domain check.  I've tried with NGINX Proxy Manager (official) as the reverse proxy and now the recommended Caddy using the example compose, caddyfile, and docker start string. 

 

The UI gives the error:

The server is not reachable on Port 443. You can verify this e.g. with 'https://portchecker.co/' by entering your domain there as ip-address and port 443 as port.

 

I have port 80 open as what I got from the documentation linked above is that for internal you *only* need to open 80.  I have AdguardHome running as DNS for the whole network already and it has an entry for  my.example.tld that points  to the private IP of my Unraid server.  There's mention of modifying the daemon.json file to include the DNS server but I'm unsure how to do that.  I did, however confirm that the Unraid GUI was pointed to 192.168.1.1, my router IP.  My router IP has the AdguardHome instance as the only DNS server.  But I also tried with unraid pointed to ip of the Pi that is running the DNS (192.168.1.24). 

 

I saw that there is an option to bypass the domain check, but it almost seems like that is required for a local only instance?  But it didn't work that way either (though that was when I was trying to get NPM running).

 

I do have domains sitting with Cloudflare, but I have no interest in running through a tunnel so I have the A and CNAME records pointing to the private IP of the server.  I'm set up with Wireguard between the server  and all devices I care about so I can reach  any of  my docker containers remotely without exposing them to the internet, which is what  I'd like to do with Nextcloud.

 

Here is the docker run I kicked things off with:

 

sudo docker run \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 8090:8080 \
--env APACHE_PORT=11000 \
--env APACHE_IP_BINDING=127.0.0.1 \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
nextcloud/all-in-one:latest

 

Here is the contents of my Caddyfile:

 

{
  http_port  8080
  https_port 8443
}

:8080 {
  log {
    output file /config/logs/access.log
  }
  root * /app/www
  file_server
}
https://my.example.tld:443 {
    header Strict-Transport-Security max-age=31536000;
    reverse_proxy localhost:11000
}

 

I'm completely lost.  I've been scouring the internet for  days trying to get this working and it seems that most folks are doing the standard internet accessible method and not a local only.  And I see @szaimen all over the internet talking about this, so I'm understanding that he's the master and commander of AIO. 

 

Please help me understand.  I'm still learning all of this and want to connect the dots, but I'm floundering on my own.

 

NOTE: One of the domains I have is a .pro, would that negatively affect the ability to get this working?  I do have a .com as well and I did try with a duckdns.org domain also.  Nothing I'm trying is working.

Figured it out.  NPM couldn't talk to the other containers.  Settings -> Docker -> Host Access to custom Networks: Enabled

This is probably not the recommended method to do this, but it was the only way I could find to get NPM on the br0 network to see Nextcloud on the bridge/nextcloud-aio network

 

EDIT: Should mention I went back to NPM since I couldn't wrap my head around Caddy.  But the above setting still needed to change in order for it to communicate with the other containers.

 

 

Edited August 16, 20232 yr by Father_Redbeard

Hi Father_Redbeard,

more then two years later I have the same problem and I think still nobody wants to limit the access of nextcloud to the local network.

I'm stuck with the following error on the initial config page (with i can access over my domain locally

"The domain is not reachable on Port 443 from within this container. Have you opened port 443/tcp in your router/firewall? If yes is the problem most likely that the router or firewall forbids local access to your domain. You can work around that by setting up a local DNS-server."

Also I get this error in the dockerlogs

NOTICE: PHP message: Info: It seems like the ip-address of domain is set to an internal or reserved ip-address. (It was found to be set to '192.168.119.49')

You got it working and iam wondering if you could share your NPM config?

Greetings

hetral