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

Zitat von ohiskyy

Trying to set up Popcorn hour transformer on OMV4 (rock64)

Keep getting

Bash

"proxy_max_temp_file_size" directive invalid value in /config/nginx/proxy-confs/nextcloud.subfolder.conf:33

What am I doing wrong?

My config:

Bash

version: "2"
services:
  nextcloud:
    image: linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=1001 #change PUID if needed
      - PGID=100  #change PGID if needed
      - TZ=Europe/Moscow  #change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-label-disk1/appdata/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
      - /srv/dev-disk-by-label-disk1/appdata/nextcloud/data:/data     #/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: linuxserver/mariadb
    container_name: nextclouddb
    environment:
      - PUID=1001 #change PUID if needed
      - PGID=100  #change PGID if needed
      - MYSQL_ROOT_PASSWORD=mariadbpassword_TRY  #change password
      - TZ=Europe/Moscow #Change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-label-disk1/appdata/nextclouddb:/config    #/srv/dev-disk-by-label-disk1 needs to be adjusted
    restart: unless-stopped
  letsencrypt:
    image: linuxserver/letsencrypt
    container_name: letsencrypt
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1001 #change PUID if needed
      - PGID=100  #change PGID if needed
      - TZ=Europe/Moscow # change Time Zone if needed
      - URL=ohiskyy.duckdns.org  #insert your domain name - yourdomain.url
      - SUBDOMAINS=www,
      - VALIDATION=http
      - EMAIL=ohiskyy@gmail.com # define email; required to renew certificate
    volumes:
      - /srv/dev-disk-by-label-disk1/appdata/letsencrypt:/config  #/srv/dev-disk-by-label-disk1 needs to be adjusted
    ports:
      - 444:443
      - 81:80
    restart: unless-stopped

Alles anzeigen

Alles anzeigen

There's nothing wrong with your nextcloud docker. Rather with your nextcloud.subfolder.conf file. Change the "proxy_max_temp_file_size from 2048m to 1024m. That's what's worked for me.

As the error message states there is a problem in your nextcloud.subfolder.conf
What is the value of proxy_max_temp_file_size?

@Morlan @pug_ster
I don't seem to have nextcloud.subfolder.conf created...?
(All steps done in accordance with the guide though)

Also, I noticed this time I tried to follow the guide from the beginning once again, it gives me waaay fewer parametres in GUI

And this is the content of

/srv/dev-disk-by-label-disk1/appdata/nextcloud/config/www/nextcloud/config/config.php

'trusted_proxies' =>
  array (
    0 => 'letsencrypt',
  ),
  'overwritewebroot' => '/nextcloud',
  'overwrite.cli.url' => 'https://ohiskyy.duckdns.org/nextcloud',
  'trusted_domains' =>
  array (
    0 => 'ohiskyy.duckdns.org:443',
  ),


  ),

Your nextcloud.subdomain.conf file is located in letsencrypt docker's configs, not in nextcloud.

/srv/dev-disk-by-label-disk1/appdata/letsencrypt/nginx/proxy-confs

Zitat von macom

Configuration of proxy

cd /srv/dev-disk-by-label-disk1/appdata/letsencrypt/nginx/proxy-confs /srv/dev-disk-by-label-disk1 has to be adjusted

cp nextcloud.subfolder.conf.sample nextcloud.subfolder.conf this will copy the sample configuration file for nextcloud and removes the .sample so that the file will become active

Alles anzeigen

Zitat von pug_ster

/srv/dev-disk-by-label-disk1/appdata/letsencrypt/nginx/proxy-confs

Thanks!
Made an edit, now it looks like this

server {
    listen 443 ssl;
    listen [::]:443 ssl;


    server_name nextcloud.*;


    include /config/nginx/ssl.conf;


    client_max_body_size 0;


    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_nextcloud nextcloud;
        proxy_max_temp_file_size 1024m;
        proxy_pass https://$upstream_nextcloud:443;
    }
}

Still getting the same error, even after full restart

try to comment out the line

hi,
trying omv5 on a virtualBox

after setup nextcloud and letsencrypt i got only "Internal Server Error"

followed the how-to

<?php
$CONFIG = array (
  'memcache.local' => '\OC\Memcache\APCu',
  'datadirectory' => '/data',
  );
 'trusted_proxies' =>
  array (
    0 => 'letsencrypt',
  ),
  'overwritewebroot' => '/nextcloud',
  'overwrite.cli.url' => 'https://mydom.org/nextcloud',
  'trusted_domains' =>
  array (
    0 => 'mydom.org:443',
  ),

mydom of corse is my dyn domain.

the how-to say after seting that all i should get a page to set the db connection .. but; only error

thx
draddy

€dit: OMG ... and insert the text from the box below at the end, but befor the ");" - change "your.url" to your domain ... if you just quick quick overfly the things ... dat "but before the ");" i just combine with change your.url - as a hint "here you got to change ..." - well done general - sitdown, "f" (in deutsch: setzen, 6)

€dit2: Ok Other Problem: i can't connect to the DB:

what i'm doing wrong?

Zitat von draddy

€dit2: Ok Other Problem: i can't connect to the DB:

I have the same problem, this help me.

allright that helps, mybe macom can change / add this in the how-to <-- done ... thats fast! xD

how can i use that letsencrypt for omv it self? emby is running and using it (found a proxy sample in /letsencrypt/nginx/proxy-confs) <-- got it here

next: btw. don't know if i go offtopic to much - just say and i start over with new topic.
atm the letsencrypt nginx is listn to port 80 and 443 from extern call (router forward) and port 81 and 444 on local side ... on localside 80 and 443 is omv ... would it be a problem to change that?

so we could use local just 192.168.x.x/omv to connect the omv - or all other stuff we proxy with dat nginx - can't we?

and, for reason something crash or we need to access omv direct without that docker - we can just use the alternate port, like 8080 or what ever we set in "General Settings Port".

and, for lets encrypt we can't block port 80 ... but, what can i do again that

Welcome to our server

The website is currently being setup under this address.

For help and support, please contact: me@example.com

if i enter without any subfolder?

what you folks think?

@Morlan the solution was to change DHLEVEL in GUI for 1024
for some reason, setting/commenting this line in config didn't work

However, still can't get it working:
Nextcloud created, but I cannot access it, crome gives "connection refused error:(

Port-forwarding for 443 and 80 is set for BOTH and enabled

On the other hand it would be great to troubleshoot it and update the guide.

Zitat von ohiskyy

@Morlan the solution was to change DHLEVEL in GUI for 1024

This is strange cause this something not related to proxy_max_temp_file_size
On which machine are running this?

Can you restart letsencrypt again and post the logs?

@draddy There are several threads about accessing omv interface via letsencrypt reverse proxy. Try these first.

Hi,
Here is the full lof of letsenc logs attached

The next step in the guide is opening up the link, but it chrome gives connection refused error
What to do next?

* Popcorn Hour Transformer, which is rock64 as I guess

Zitat von KM0201

Have you tried just following the old guide?

Which exactly?
I tried to follow technodad's guide bilion of years ago, never succeeded

The log looks good. The container including the nginx server is running. So the issue is host likely in the .conf files or your nextcloud config.php

Zitat von KM0201

Are you comfortable with Docker-Compose?

No, not exactly. Guided mode only

Zitat von Morlan

So the issue is host likely in the .conf files or your nextcloud config.php

Any suggestions where to look?

Are you using subfolder or subdomain method? In ealier posts you seemed to use subfolder method according to the guide. In the recent posts you used the subdomain.conf (even though you dont have a nextcloud subdomain specified in your letsencrypt config).