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

Zitat von Draky50110

No more proxy conf.

line: 17, You've given complete command & control with: /var/run/docker.sock. I feel you should never do this and the articles that suggest situations where this could be O.K. are crazy. If you have ZERO skills in programming and/or the understanding of RTFM, then I understand, but you _should_ create a proxy container to communicate between the system and your current docker namespace exclusively. However, there has to be MANY Docker containers out there that already do this, it's just a matter of finding one.

I don't use SWAG but I did use it a couple years ago when it was still called letsencrypt.linuxserver.io and I remember it had proxy templates you could use, what was wrong with that method?

This mounting point comes from linuxserver : https://github.com/linuxserver…ods/tree/universal-docker

Maybe a docker proxy should be used you're right.

This solution permits to not rely on .conf and was ok for me.

Repo of conf is here : https://github.com/linuxserver…e-proxy-confs/tree/master

After some trial and error, I got this up and running!

An idea to add to the guide, would be to clarify the point of the data folder in the nextcloud container. I figured it out thanks to this post: RE: How to share folders with Nextcloud, but I suppose it couldn't hurt to instruct people from the beginning that they should include there every shared OMV folder they would like to access.

Thanks to everyone!

I don't know what's wrong

help pls

I don't know what to do, if I don't do anything the same thing happens, I've already deleted everything from nextcloud, swag and mariadb and it's still like that.

Zitat von ChachoCl

I don't know what to do, if I don't do anything the same thing happens, I've already deleted everything from nextcloud, swag and mariadb and it's still like that.

Post all YMLs used.

Hide sensible data.

Hi together,

I'm fairly new to Linux and Container but I followed the respective guide of this thread to setup NC with swag on my Raspi 5.

I just have two questions as, after digging into a bunch of threads and googling a lot I could not find matching answers.

1. Where is the data folder that is used when setting up NC? As no volumes were created in the yml for the file storage I cannot find it in the appdata folder on my external drive but it's located somewhere on my microSD as the var/lib/docker is on it.

2. How can I increase the upload file size limit? I already looked into the php-local.ini within the nextcloud appdata folder and placed this in it:

upload_max_filesize = 16G
post_max_size = 16G

But still face the issue of being limited to 512 MB.

Thanks in advance.

Zitat von Fatality2024

Where is the data folder that is used when setting up NC?

Post the YML used but omit sensible INFO (password, email, url, etc)

Zitat von Fatality2024

2. How can I increase the upload file size limit?

Did you restarted nextcloud after editing that file?

And how did you edit it?

Which permissions are on the HOST php-local.ini file?

It has to be owned by the UID:GID that is on the YML.

And what shows on the Nextcloud System Page?

Hi Soma,

thanks for your reply.

This my yml:

version: "2"
services:
  nextcloud:
    image: ghcr.io/linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=${PUID} #change PUID if needed
      - PGID=${PGID}  #change PGID if needed
      - TZ=Europe/Berlin #change Time Zone if needed
      - PHP_UPLOAD_LIMIT=8G
      - PHP_MEMORY_LIMIT=8G
    volumes:
      - CHANGE_TO_COMPOSE_DATA_PATH/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
    depends_on:
      - mariadb
#    ports: # uncomment this and the next line if you want to bypass the proxy
#      - 450:443
    restart: unless-stopped
  mariadb:
    image: ghcr.io/linuxserver/mariadb
    container_name: nextclouddb
    environment:
      - PUID=${PUID} #change PUID if needed
      - PGID=${PGID} #change PGID if needed
      - MYSQL_ROOT_PASSWORD=XXXXXXX #change password
      - TZ=Europe/Berlin #Change Time Zone if needed
    volumes:
      - CHANGE_TO_COMPOSE_DATA_PATH/nextclouddb:/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=${PUID} #change PUID if needed
      - PGID=${PGID}  #change PGID if needed
      - TZ=Europe/Berlin # change Time Zone if needed
      - URL=XXXXXXX.duckdns.org #insert your domain name - yourdomain.url
      - SUBDOMAINS=wildcard,
      - VALIDATION=DUCKDNS
      - DUCKDNSTOKEN=XXXXXXXXXXXXXXXXX
      - EMAIL=MAIL@MAIL.de # define email; required to renew certificate
      - DOCKER_MODS=linuxserver/mods:swag-dashboard
    volumes:
      - CHANGE_TO_COMPOSE_DATA_PATH/swag:/config  #/srv/dev-disk-by-label-disk1 needs to be adjusted
    ports:
      - 444:443
      - 81:80
      - 82:81
    restart: unless-stopped
  redis:
    image: redis
    container_name: redis
    hostname: redis
    volumes:
      - CHANGE_TO_COMPOSE_DATA_PATH/redisDocker:/data    #--> needs to be changed to your config
    restart: unless-stopped    

Forgot to mention that I also followed another post and added the following commands under environment:

      - PHP_UPLOAD_LIMIT=8G
      - PHP_MEMORY_LIMIT=8G

I did restart the container but I also read somewhere that, when using swag, those parameters have also to be set for swag but I did not know where exactly.

This is what my php-local.ini:

The permissions for the file are:

-rw-r--r-- 1 appuser users 49 Apr 25 23:35 php-local.ini

And this is what the System Page shows

Thanks in advance.

Zitat von Fatality2024

Forgot to mention that I also followed another post and added the following commands under environment:

Post the link to the post where you saw that, please.

Those envs don't exist on the linuxserver image.

Remove them.

Zitat von Fatality2024

- PUID=${PUID}

- PGID=${PGID}

Where is this env set?

I find it better to use the proper number.

Run on CLI id appuser and use that number. Should be 1000 or bigger, depending how many users you created.

Same goes for GID. In your case will be 100.

- PUID=1000 # Or 1001, or 1002, etc
- PGID=100

Since you didn't set a DATA volume, your data is volatile.

You don't want that and need to have the volume on a seperate drive.

You should start fresh and follow the guide proper because it is mentioned there:

      - /srv/dev-disk-by-label-disk1/appdata/nextcloud/data:/data     #/srv/dev-disk-by-label-disk1 needs to be adjusted

Your YML should be something like:

services:
  nextcloud:
    image: lscr.io/linuxserver/nextcloud:latest
    container_name: nextcloud
    environment:
      - PUID=1000 # Or the output of id appuser
      - PGID=100
      - TZ=Europe/Berlin
    volumes:
      - /srv/dev-disk-by-uuid-xxx/nextcloud/config:/config #/srv/dev-disk-by-uuid-xxx needs to be adjusted
      - /srv/dev-disk-by-uuid-xxx/nextcloud/data:/data #/srv/dev-disk-by-uuid-xxx needs to be adjusted
    depends_on:
      - mariadb
    ports: # these are commented AFTER initial install
      - 450:443 # these are commented AFTER initial install
    restart: unless-stopped
  mariadb:
    image: lscr.io/linuxserver/mariadb:latest
    container_name: nextclouddb
    environment:
      - PUID=1000 # Or the output of id appuser
      - PGID=100
      - MYSQL_ROOT_PASSWORD=XXXXXXX #change password
      - TZ=Europe/Berlin #Change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-uuid-xxx/nextclouddb/config:/config    #/srv/dev-disk-by-uuid-xxx needs to be adjusted
    restart: unless-stopped
  swag:
    image: lscr.io/linuxserver/swag:latest
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000 # Or the output of id appuser
      - PGID=100
      - TZ=Europe/Berlin
      - URL=XXXXXXX.duckdns.org
      - SUBDOMAINS=wildcard
      - VALIDATION=DUCKDNS
      - DUCKDNSTOKEN=XXXXXXXXXXXXXXXXX
      - EMAIL=MAIL@MAIL.de
      - DOCKER_MODS=linuxserver/mods:swag-dashboard
    volumes:
      - /srv/dev-disk-by-uuid-xxx/swag/config:/config  #/srv/dev-disk-by-uuid-xxx needs to be adjusted
    ports:
      - 444:443
#      - 81:80 # Not needed when using DUCKDNS validation. Port can be closed on the router 
      - 82:81 # Do not open this port on the router
    restart: unless-stopped
  redis:
    image: redis
    container_name: redis:latest
    hostname: redis
    volumes:
      - /srv/dev-disk-by-uuid-xxx/redis/data:/data    #/srv/dev-disk-by-uuid-xxx needs to be adjusted
    restart: unless-stopped

Zitat von chente

https://wiki.omv-extras.org/do…l_environmental_variables

https://wiki.omv-extras.org/do…bal_environment_variables

Fatality2024

Then it's better to open a new thread because this QA refers a specific created guide that expects a stablished set of lines on the YML.

If followed verbatim, it's easy to help and figure where there's issues.

Zitat von Soma

Post the link to the post where you saw that, please.

I found this here: https://www.reddit.com/r/NextC…_file_size_2mb_in_docker/

Zitat von Soma

Where is this env set?

I find it better to use the proper number.

The env is set in the Docker Compose OMV plugin as chente pointed out. The variables are set accordingly for PUID and PGID. That should not be the problem as everything else works using those.

The variables are set as follows:

PUID=1001
PGID=100
TZ=Europe/Berlin

Zitat von Soma

Since you didn't set a DATA volume, your data is volatile.

You don't want that and need to have the volume on a seperate drive.

You should start fresh and follow the guide proper because it is mentioned there:

Code

      - /srv/dev-disk-by-label-disk1/appdata/nextcloud/data:/data     #/srv/dev-disk-by-label-disk1 needs to be adjusted

OMG, I can't believe I missed that. I went over the YML again and again and totally lost that line. That explains a lot. Especially as I sometimes faced the "missing .ocdata" error when landing on the nc main page :).

I will directly add that and start over again.

But still, the question is, in which I files I will have to set the respective parameters to increase my upload limit.

So, if you could tell me this, I think I might be good to go.

Thanks again and sorry for missing that in my yml.