Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

I think I was able to install it but I think I have a problem with my isp router I can access nextcloud only outside of my local network.

I needed to change the proxy_max_temp_file_size from 2048 to 1024.

nginx: [emerg] "proxy_max_temp_file_size" directive invalid value in /config/nginx/proxy-confs/nextcloud.subdomain.conf:34

I know it is a docker question... On the docker compose are some volumes defined however on portainer these volumes aren't shown. Is this a normal behavior?

I'm trying to access nextcloud from local network. I tried to configure dnsmasq and it replied the ip address of nextcloud host however I still can't access it from local network:

ze-mac-2:~ ze$ curl https://nextcloud.mydomain.duckdns.org
curl: (7) Failed to connect to nextcloud.mydomain.duckdns.org port 443: Connection refused

There is any setting that I look into?

My config.php settings:

  'overwrite.cli.url' => 'https://nextcloud.mydomain.duckdns.org',
  'overwritehost' => 'nextcloud.mydomain.duckdns.org',
  'overwriteprotocol' => 'https',
  'trusted_domains' =>
  array (
    0 => '192.168.1.108:444',
    1 => 'nextcloud.mydomain.duckdns.org',
  ),

Zitat von macom

Did you see this in the docker-compose file:

Code

#    ports: # uncomment this and the next line if you want to bypass the proxy
#      - 450:443

so if you un-comment these lines you should have access to your nextcloud from within the network with

https://ip.of.you.server:450

in your case you have to replace 450 by 444

There is any disadvantage enabling it?

I still want to use the domain but inside my local network.

Thank you. So when I access it inside my local network there is no certificate?

Zitat von macom

When I use "subdomain.domain.de" I have a certificate

Even for local requests?

But when I access the server outside of my network the request is routed to a ip also. Can you explain me or redirect me for some documentation why do I need to bypass the proxy when on local network?

When I uncomment the line I got this error:

EDIT1:

Change to port 443 and now it is working but browser tell me it is insecure and that the certificate is invalid.

Also both mydomain.duckdns.org and nextcloud.mydomain.duckdns.org point to nextcloud.

EDIT2:

It looks like I messed up with dnsmasq. I disable dnsmasq and using my router dns I can access my nextcloud

EDIT3: now if I want to have another subdomain for another server it won't work if I use port 443

When I send a request to my router on port 443/80 it forward the request to my host, 192.168.1.108:444/81. Then swag got the request and forward it to nextcloud because I have set it on my nextcloud server:

'trusted_domains' => 
      array (
        0 => '192.168.1.108:443',
        1 => 'nextcloud.mydomain.duckdns.org',
      ),

Is that how it work?

For some reason, I am unable to get to the Nextcloud interface after installing it. Here is the code that I use in portainer (stacks)

version: "2"
services:  nextcloud:    image: linuxserver/nextcloud    container_name: nextcloud    environment:      
- PUID=1000 #change PUID if needed      
- PGID=100  #change PGID if needed      
- TZ=Asia/Kolkata #change Time Zone if needed    
volumes:      
- /srv/8844814c-4b4b-489e-84df-9522f98c7c8b/appdata/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted      
- /srv/8844814c-4b4b-489e-84df-9522f98c7c8b/appdata/nextcloud:/data     #/srv/dev-disk-by-label-disk1 needs to be adjusted    
depends_on:      
- mariadb    ports:      
- 8085:80      - 450:443    restart: unless-stopped  mariadb:    image: linuxserver/mariadb    container_name: nextclouddb    environment:      
- PUID=1000 #change PUID if needed      
- PGID=100  #change PGID if needed      
- MYSQL_ROOT_PASSWORD=xxxxxx  #change password      
- TZ=Asia/Kolkata #Change Time Zone if needed    
volumes:      
- /srv/8844814c-4b4b-489e-84df-9522f98c7c8b/appdata/mariadb:/config    #/srv/dev-disk-by-label-disk1 needs to be adjusted    
restart: unless-stopped  
swag:    image: linuxserver/swag         #swag is the replacement for letsencrypt (see link below)    
container_name: swag    
cap_add:      
- NET_ADMIN    
environment:      
- PUID=1000 #change PUID if needed      
- PGID=100  #change PGID if needed     
- TZ=Asia/Kolkata # change Time Zone if needed      
- URL=duckdns.org      
- SUBDOMAINS=sciden     
- VALIDATION=http      
- DUCKDNSTOKEN=xxxxxxxxxxx      
- EMAIL=xxxxxxxxx@gmail.com # define email; required to renew certificate    
volumes:      
- /srv/8844814c-4b4b-489e-84df-9522f98c7c8b/appdata/swag:/config      
ports:      
- 444:443      
- 82:80    
restart: unless-stopped

Also, do I need `swag` if I am using nginx-proxy manager?

Without swag, is the following code correct for portainer stacks:

```

version: "2"
services:  nextcloud:    
image: linuxserver/nextcloud    
container_name: nextcloud    
environment:      
- PUID=1000 #change PUID if needed      
- PGID=100  #change PGID if needed      
- TZ=Asia/Kolkata #change Time Zone if needed    
volumes:      
- /srv/8844814c-4b4b-489e-84df-9522f98c7c8b/appdata/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted      
- /srv/8844814c-4b4b-489e-84df-9522f98c7c8b/appdata/nextcloud:/data     #/srv/dev-disk-by-label-disk1 needs to be adjusted    
depends_on:      
- mariadb    
ports:      
- 8085:80      
- 450:443    
restart: unless-stopped  
mariadb:    
image: linuxserver/mariadb    
container_name: nextclouddb    
environment:      
- PUID=1000 #change PUID if needed      
- PGID=100  #change PGID if needed      
- MYSQL_ROOT_PASSWORD=xxxx  #change password      
- TZ=Asia/Kolkata #Change Time Zone if needed    
volumes:      
- /srv/8844814c-4b4b-489e-84df-9522f98c7c8b/appdata/mariadb:/config    #/srv/dev-disk-by-label-disk1 needs to be adjusted    
restart: unless-stopped

```

I have duckdns installed as a separate container. nginx-proxy will also be used.

For some reason, the codes don't work. Even though everything installs normally, the WebUI is always unreachable (192.168.1.118:8085 or port 450)

Have been trying for a few days. Also tried the nextcloudpi method. There too the installation wouldn't get activated. I will greatly appreciate some help in this.

Yes to everything, except letsencrypt. I will follow that too. One more thing; instructions say

• do not place the config folders on a mergerfs mount point

I have placed config on a unionFS mount point. Is that a problem?

Another change: I had made a user, user1 when I first installed OMV. I used that user instead of docker1.

Zitat von metRo_

When I send a request to my router on port 443/80 it forward the request to my host, 192.168.1.108:444/81. Then swag got the request and forward it to nextcloud because I have set it on my nextcloud server:

Code

'trusted_domains' => 
      array (
        0 => '192.168.1.108:443',
        1 => 'nextcloud.mydomain.duckdns.org',
      ),

Is that how it work?

Change my ip and port to this and it seems to be working as supposed.

'trusted_domains' =>
  array (
    0 => '192.168.1.108:444',
    1 => 'nextcloud.mydomain.duckdns.org',
  ),

What kind of download/upload speed do you get on nextcloud? The same as using samba shares?