Nextcloud with Letsencrypt using OMV and docker-compose - Q&A
-
- OMV 5.x
- WastlJ
-
-
I also have a subfolder setup.
-
ah ok,
i only removed the subdomain www from compose file - SUBDOMAINS= with - SUBDOMAINS=www i got an error, without it runs just fine - so i'm wondering about your "subdomain only"?
-
I followed the tutortial and after a few tweeks from the Q&A and other threads of this forum, everything was working like a charm for more than a month - until two days ago.
I was wondering, why my smartphone-app wasn't syncing and so I tried to visit the web-interface, but I couldn't get any connections.My configuration:
Raspi 3+
OMV 4
Letsencrypt, Nextcloud and MariaDB in docker (from the tutorial)What did I do so far:
Restarted the docker - no solution
docker logs -f nextcloud
Code
Alles anzeigen[cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 1003 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 40-config: executing... [cont-init.d] 40-config: exited 0. [cont-init.d] 50-install: executing... [cont-init.d] 50-install: exited 0. [cont-init.d] 60-memcache: executing... [cont-init.d] 60-memcache: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [01-Mar-2020 14:55:41] ERROR: No pool defined. at least one pool section must be specified in config file [01-Mar-2020 14:55:41] ERROR: failed to post process the configuration [01-Mar-2020 14:55:41] ERROR: FPM initialization failed
Ha! This is new.docker exec -it nextcloud bash
cat etc/php7/php-fpm.d/www.conf
Code: www.conf
Alles anzeigen[www] ; Per pool prefix ; It only applies on the following directives: ; - 'access.log' ; - 'slowlog' ; - 'listen' (unixsocket) ; - 'chroot' ; - 'chdir' ; - 'php_values' ; - 'php_admin_values' ; When not set, the global prefix (or /usr) applies instead. ; Note: This directive can also be relative to the global prefix. ; Default Value: none ;prefix = /path/to/pools/$pool ; Unix user/group of processes ; Note: The user is mandatory. If the group is not set, the default user's group ; will be used. user = abc group = abc ; The address on which to accept FastCGI requests. ; Valid syntaxes are: ; 'ip.add.re.ss:port' - to listen on a TCP socket to a specific IPv4 address on ; a specific port; ; '[ip:6:addr:ess]:port' - to listen on a TCP socket to a specific IPv6 address on ; a specific port; ; 'port' - to listen on a TCP socket to all addresses ; (IPv6 and IPv4-mapped) on a specific port; ; '/path/to/unix/socket' - to listen on a unix socket. ; Note: This value is mandatory. listen = 127.0.0.1:9000 ; Set listen(2) backlog. ; Default Value: 511 (-1 on FreeBSD and OpenBSD) ;listen.backlog = 511 ; Set permissions for unix socket, if one is used. In Linux, read/write ; permissions must be set in order to allow connections from a web server. Many ; BSD-derived systems allow connections regardless of permissions. ; Default Values: user and group are set as the running user ; mode is set to 0660 ;listen.owner = nobody ;listen.group = abc ;listen.mode = 0660 ; When POSIX Access Control Lists are supported you can set them using ; these options, value is a comma separated list of user/group names. ; When set, listen.owner and listen.group are ignored ;listen.acl_users = ;listen.acl_groups = ; List of addresses (IPv4/IPv6) of FastCGI clients which are allowed to connect. ; Equivalent to the FCGI_WEB_SERVER_ADDRS environment variable in the original ; PHP FCGI (5.2.2+). Makes sense only with a tcp listening socket. Each address ; must be separated by a comma. If this value is left blank, connections will be ; accepted from any ip address. ; Default Value: any ;listen.allowed_clients = 127.0.0.1 ; Specify the nice(2) priority to apply to the pool processes (only if set) ; The value can vary from -19 (highest priority) to 20 (lower priority) ; Note: - It will only work if the FPM master process is launched as root ; - The pool processes will inherit the master process priority ; unless it specified otherwise ; Default Value: no set ; process.priority = -19 ; Set the process dumpable flag (PR_SET_DUMPABLE prctl) even if the process user ; or group is differrent than the master process user. It allows to create process ; core dump and ptrace the process for the pool user. ; Default Value: no ; process.dumpable = yes ; Choose how the process manager will control the number of child processes. ; Possible Values: ; static - a fixed number (pm.max_children) of child processes; ; dynamic - the number of child processes are set dynamically based on the ; following directives. With this process management, there will be ; always at least 1 children. ; pm.max_children - the maximum number of children that can ; be alive at the same time. ; pm.start_servers - the number of children created on startup. ; pm.min_spare_servers - the minimum number of children in 'idle' ; state (waiting to process). If the number ; of 'idle' processes is less than this ; number then some children will be created. ; pm.max_spare_servers - the maximum number of children in 'idle' ; state (waiting to process). If the number ; of 'idle' processes is greater than this ; number then some children will be killed. ; ondemand - no children are created at startup. Children will be forked when ; new requests will connect. The following parameter are used: ; pm.max_children - the maximum number of children that ; can be alive at the same time. ; pm.process_idle_timeout - The number of seconds after which ; an idle process will be killed. ; Note: This value is mandatory. pm = dynamic ; The number of child processes to be created when pm is set to 'static' and the ; maximum number of child processes when pm is set to 'dynamic' or 'ondemand'. ; This value sets the limit on the number of simultaneous requests that will be ; served. Equivalent to the ApacheMaxClients directive with mpm_prefork. ; Equivalent to the PHP_FCGI_CHILDREN environment variable in the original PHP ; CGI. The below defaults are based on a server without much resources. Don't ; forget to tweak pm.* to fit your needs. ; Note: Used when pm is set to 'static', 'dynamic' or 'ondemand' ; Note: This value is mandatory. pm.max_children = 5 ; The number of child processes created on startup. ; Note: Used only when pm is set to 'dynamic' ; Default Value: min_spare_servers + (max_spare_servers - min_spare_servers) / 2 pm.start_servers = 2 ; The desired minimum number of idle server processes. ; Note: Used only when pm is set to 'dynamic' ; Note: Mandatory when pm is set to 'dynamic' pm.min_spare_servers = 1 ; The desired maximum number of idle server processes. ; Note: Used only when pm is set to 'dynamic' ; Note: Mandatory when pm is set to 'dynamic' pm.max_spare_servers = 3 ; The number of seconds after which an idle process will be killed. ; Note: Used only when pm is set to 'ondemand' ; Default Value: 10s ;pm.process_idle_timeout = 10s;
... and more commented out but to long for this message.
cat etc/php7/php-fpm.d/www2.conf
Code: www2.conf; Edit this file to override www.conf and php-fpm.conf directives and restart the container ; Pool name [www]
cat etc/php7/php-fpm.conf
Is this the problem? What should be in php-fpm.conf? And if this is the problem, why did it changed by itself? Background-Update?
To be honest, i'm quite new to OMV/docker/nextcloud.Thanks!
-
Hallo,
after Nextcloud is running well in subfolder mode i tryed to switch to the subdomian "mode".
After I changed my nextcloud config, changed the proxy-confs, add subdomian in letsencrypt and setup a cname record for my subdomian.
I got on my Subdomain only to the "Welcome to my Server" page.
My Network Setup
cloud.mydomain.de with cname record to mydomain.de
mydomain.de with dyndns to my fritz.box
fritzbox with port forwarding- port extern 443 to port 444 intern
- port extern 80 to port 81 intern
Here is my Docker compose
version: "2"
services:
nextcloud:
image: linuxserver/nextcloud
container_name: nextcloud
environment:
- PUID=1000 #change PUID if needed
- PGID=100 #change PGID if needed
- TZ=Europe/Berlin #change Time Zone if needed
volumes:
- /srv/dev-disk-by-id-ata-VBOX_HARDDISK_VB4b90c60d-28e9044f-part1/config/Nextcloud:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
- /srv/dev-disk-by-id-ata-VBOX_HARDDISK_VB4b90c60d-28e9044f-part1/data/Nextcloud:/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=1000 #change PUID if needed
- PGID=100 #change PGID if needed
- MYSQL_ROOT_PASSWORD=niklas97 #change password
- TZ=Europe/Berlin #Change Time Zone if needed
volumes:
- /srv/dev-disk-by-id-ata-VBOX_HARDDISK_VB4b90c60d-28e9044f-part1/config/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=1000 #change PUID if needed
- PGID=100 #change PGID if needed
- TZ=Europe/Berlin # change Time Zone if needed
- URL=mydomain.de #insert your domain name - yourdomain.url
- SUBDOMAINS=www,server,plex,cloud
- VALIDATION=http
- EMAIL=testletsencrypt@mydomain.de # define email; required to renew certificate
volumes:
- /srv/dev-disk-by-id-ata-VBOX_HARDDISK_VB4b90c60d-28e9044f-part1/config/letsencrypt:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
ports:
- 444:443
- 81:80
restart: unless-stopped
My config.phpPHP
Alles anzeigen<?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'trusted_proxies' => array ( 0 => 'letsencrypt', ), 'overwrite.cli.url' => 'https://cloud.mydomian.de', 'overwritehost' => 'cloud.mydomain.de', 'overwriteprotocol' => 'https', 'trusted_domains' => array ( 0 => 'cloud.mydomain.de', )
Subdomain conf
# make sure that your dns has a cname set for nextcloud
# assuming this container is called "letsencrypt", edit your nextcloud container's config
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
# 'trusted_proxies' => ['letsencrypt'],
# 'overwrite.cli.url' => 'https://nextcloud.your-domain.com/',
# 'overwritehost' => 'nextcloud.your-domain.com',
# 'overwriteprotocol' => 'https',
#
# Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:
# array (
# 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
# 1 => 'nextcloud.your-domain.com',
# ),server {
listen 443 ssl;
listen [::]:443 ssl;server_name cloud.*;
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_app nextcloud;
set $upstream_port 443;
set $upstream_proto https;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;proxy_max_temp_file_size 2048m;
}
} -
was does the letsencrypt log say?
-
Hey i dont now what happend but now it is working.
My Letsencrypt Log
GID/UID
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">-------------------------------------
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">User uid: 1000
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">User gid: 100
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">-------------------------------------
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[cont-init.d] 10-adduser: exited 0.
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[cont-init.d] 20-config: executing...
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[cont-init.d] 20-config: exited 0.
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[cont-init.d] 30-keygen: executing...
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">using keys found in /config/keys
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[cont-init.d] 30-keygen: exited 0.
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[cont-init.d] 50-config: executing...
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">Variables set:
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">0
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">PGID=100
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">TZ=Europe/Berlin
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">URL=
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">SUBDOMAINS=
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">EXTRA_DOMAINS=
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">ONLY_SUBDOMAINS=false
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">DHLEVEL=2048
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">VALIDATION=http
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">DNSPLUGIN=
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">EMAIL=
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">STAGING=
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">2048 bit DH parameters present
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">SUBDOMAINS entered, processing
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">SUBDOMAINS entered, processing
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">Sub-domains processed are:
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">E-mail address entered:
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">http validation is selected
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">Certificate exists; parameters unchanged; starting nginx
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">Starting 2019/12/30, GeoIP2 databases require personal license key to download. Please manually download/update the GeoIP2 db and save as /config/geoip2db/GeoLite2-City.mmdb
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[cont-init.d] 50-config: exited 0.
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[cont-init.d] 99-custom-files: executing...
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[custom-init] no custom files found exiting...
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[cont-init.d] 99-custom-files: exited 0.
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[cont-init.d] done.
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[services.d] starting services
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">[services.d] done.
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
-1 }" style="box-sizing: border-box; padding-right: 15px; padding-left: 15px; cursor: pointer;">Server readyEverything is working fine now.
Only i cant acess via lokal ip to nextcloud.
I add already to the config.php
1 => 'nas.lokal:444',
I got only to the "Welcome to me Server Site".
-
Hi,
I am trying to use Redis to speed-up my Nextcloud on OMV5 using docker.
I have followed the nextcloud documentation to update my config.php file, I have also edited my redis.conf file. My Redis Server is up but synchronisation failed and I have an error : RedisException: No such file or Directory
Config.php
'memcache.local' => '\OC\Memcache\APCu',
'memcache.locking' => '\OC\Memcache\Redis',
'filelocking.enabled' => true,
'redis' =>
array (
'host' => '/var/run/redis/redis.sock',
'port' => 0,
'timeout' => 0.0,
),
I have checked my nextcloud log file and I can not identified where the problem is.
Does anyone have successfully switched to Redis for memory caching ?
Thanks for you help
-
Hello,
i'm trying to use Nextcloud on my fresh OMV 5 installation on RPI 2.
I'm using the following tutorial: [How-To] Nextcloud with Letsencrypt using OMV and docker-compose
I follow the instructions but something is wrong during letsencrypt step (I suppose):
- The following errors were reported by the server:
HTML
Alles anzeigenDomain: www.xxxx.de Type: unauthorized Detail: Invalid response from http://www.xxxx.de/.well-known/acme-challenge/C4U5BpF8xqbQhjNht4P76Wmlsc3kR5aArQrxilJqv_A [185.53.177.50]: "<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>nginx</center>\r\n" Domain: xxxx.de Type: unauthorized Detail: Invalid response from http://xxxx.de/.well-known/acme-challenge/4vlppRjS75T8_Tkkz84Dq4JyzqM6GPzv95QYYKnK1cQ [185.53.177.50]: "<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>nginx</center>\r\n" To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container
my set-up for config.php:
PHP
Alles anzeigen<?php $CONFIG = array ( 'memcache.local' => '\OC\Memcache\APCu', 'datadirectory' => '/data', 'trusted_proxies' => array ( 0 => 'letsencrypt', ), 'overwritewebroot' => '/nextcloud', 'overwritehost' => 'cseb.is-gone.com', 'overwrite.cli.url' => 'https://cseb.is-gone.com/nextcloud', 'trusted_domains' => array ( 0 => 'cseb.is-gone.com:443', ), );
I know I forgot something but where it's my first experience/install with docker
Thanks
cseb
-
Hello,
i'm trying to use Nextcloud on my fresh OMV 5 installation on RPI 2.
I'm using the following tutorial: [How-To] Nextcloud with Letsencrypt using OMV and docker-compose
I follow the instructions but something is wrong during letsencrypt step (I suppose):
- The following errors were reported by the server:
HTML
Alles anzeigenDomain: www.xxxx.de Type: unauthorized Detail: Invalid response from http://www.xxxx.de/.well-known/acme-challenge/C4U5BpF8xqbQhjNht4P76Wmlsc3kR5aArQrxilJqv_A [185.53.177.50]: "<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>nginx</center>\r\n" Domain: xxxx.de Type: unauthorized Detail: Invalid response from http://xxxx.de/.well-known/acme-challenge/4vlppRjS75T8_Tkkz84Dq4JyzqM6GPzv95QYYKnK1cQ [185.53.177.50]: "<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>nginx</center>\r\n" To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container
my set-up for config.php:
PHP
Alles anzeigen<?php $CONFIG = array ( 'memcache.local' => '\OC\Memcache\APCu', 'datadirectory' => '/data', 'trusted_proxies' => array ( 0 => 'letsencrypt', ), 'overwritewebroot' => '/nextcloud', 'overwritehost' => 'cseb.is-gone.com', 'overwrite.cli.url' => 'https://cseb.is-gone.com/nextcloud', 'trusted_domains' => array ( 0 => 'cseb.is-gone.com:443', ), );
I know I forgot something but where it's my first experience/install with docker
Thanks
cseb
Hello,
I forgot to enter my Dyndns domain address. It's done but doesn't work
HTML
Alles anzeigenIMPORTANT NOTES: - The following errors were reported by the server: Domain: cseb.is-gone.com Type: unauthorized Detail: Invalid response from http://cseb.is-gone.com/.well-known/acme-challenge/PrSfLUK-sXqyC119HPJu_OkkUiGQJH-UUb9PAc-0n9M [81.64.34.243]: "<!DOCTYPE html>\n<html>\n\t<head>\n\t\t<title>openmediavault - HTTP 404 error</title>\n\t\t<meta charset=\"UTF-8\">\n\t\t<meta http-equiv=\"X-U" To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. - The following errors were reported by the server: Domain: www.cseb.is-gone.com Type: dns Detail: DNS problem: NXDOMAIN looking up A for www.cseb.is-gone.com - check that a DNS record exists for this domain ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container
Someone has an idea?
Thanks
cseb
-
hi,
the error happens right after run the compos file?
have you port forward 443 and 80 to your RPI2?
-
hi,
the error happens right after run the compos file?
have you port forward 443 and 80 to your RPI2?
Hi,
Just after the command "docker logs -f letsencrypt".
Into "docker-compose.yml" file I have:
config.php:
Code'overwritewebroot' => '/nextcloud', 'overwrite.cli.url' => 'https://cseb.is-gone.com/nextcloud', 'trusted_domains' => array ( 0 => 'cseb.is-gone.com:443', ),
On my router:
Thanks
cseb
-
hm hm
if i try to connect
i can get your OMV so i just wondering, cause, your omv will listen to port 80 for http if you haven't change it, and your config say you forward port 80 extern to port 81 in your network - and on 81 in your network is the letsencrypt listen container listen to - so: if i try to connect i have to reach your letsencrypt proxy OR have to get an error like page not available.
don't know your router, but dobblecheck the settings, maybe reboot it and recheck the settings - for me it looks like that letsencrypt can't do the needed checks on http and https to verify your domain and sign your certificate.
-
Hi everyone,
in case you want to connect for syncing your Nextcloud with a local LAN connection as well as out of your local LAN ( via duckDNS,spDYN,etc.), the following config adjusting works for me.
To enable a local connection, you have to forward the exposed Docker port 443 (80 if needed) to your wished port - here 444. The Nextcloud config needs little adjustment as well. Add your OMV IP with respective Nextcloud Docker port to the trusted_domain array.
Codetrusted_domains' => array ( 0 => 'your.domain-Nextcloud.com', //here should be your DuckDNS/DNSprovier Domain 1 => '192.168.2.3:444', //here should be the IP of your OMV with respective Nextcloud docker port forwarding ),
Furthermore, when you follow the provided instructions on how to setup the linuxserver/letsencrypt, you have to add following lines to your Nextcloud config:
Code# make sure that your dns has a cname set for nextcloud # assuming this container is called "letsencrypt", edit your nextcloud container's config # located at /config/www/nextcloud/config/config.php and add the following lines before the ");": # 'trusted_proxies' => ['letsencrypt'], # 'overwrite.cli.url' => 'https://nextcloud.your-domain.com/', # 'overwritehost' => 'nextcloud.your-domain.com', # 'overwriteprotocol' => 'https',
Here you have to change the 'overwrite.cli.url entry and delet or mark as comment overwritehost in the Nextcloud config:
Code'overwrite.cli.url' => 'https', //instead of 'https://nextcloud.your-domain.com/' 'overwritehost' => 'nextcloud.your-domain.com', <- delete this line or marks as a comment
Restart your Nextcloud Docker.
Now you should be able to open Nextcloud with your local IP as well with your own domain. But be aware, if you log in locally and share a folder/file, the created link will be with your local IP and therefore not accessible from outside of your network. You can either replace the IP from the created link with your domain
Codelocally created shared link: https://192.168.2.3:444/s/jkyY6jP2dnzDdEF replace the IP with your domain to make link accessible for public: https://your.domain-Nextcloud.com/s/jkyY6jP2dnzDdEF
or you have to login with your domain on Nextcloud and create the share link from there.
-
What is the best (correct, or preferred) method for renewing the letsencrypt cert under this setup?
-
Should be done automatically
-
Hi
I'm trying to follow this guide (many thanks for putting it together!) on a RPI4 with OMV5. I've installed the docker images, and got to the point where I check the Letsencrypt logs with docker logs -f letsencrypt. I see invalid response error messages for all domains that were checked; at the end it says 'ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container'.
I'm installing with duckdns (I've followed these instructions) and a subdomain (followed these instructions). I'm very new to all of this, and I don't know where to start looking for an answer. I've checked the docker-compose yml, and can find no error. I've followed the instructions for my router to configure port forwarding, but I don't know how to test if the configuration is correct. Could you please help?
-
More information is necessary. Maybe provide a picture of your port forward’s
-
More information is necessary. Maybe provide a picture of your port forward’s
Thanks for responding so quickly. See screenshot attached.
-
There are already some errors. 80-81 means that you opened a range of ports.
Also I need some more detailed infos. Can you show a screenshot of the options window when press edit of the http-server and https-server?
Did you follow the guide regards the port assignments of the docker containers?
Mine looks likes this:
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!