Hello, let's say to reach my nextcloud I need to go to https://Jb.ddns.net/nextcloud. How can I do https://jb.ddns.net instead to reach it? What kind of configuration would I need so that I don't have to add the /nextcloud at the end?
![](https://forum.openmediavault.org/wsc/images/avatars/12/191-1257c2aeec82e7b0ded3471234b694ebb16152e2.jpg)
Nextcloud with Letsencrypt using OMV and docker-compose - Q&A
-
- OMV 5.x
- WastlJ
-
-
I have read all the posts here, but still cant understand,
Followed all the instructions here:
[How-To] Nextcloud with Letsencrypt using OMV and docker-compose
Now I can access to Nextcloud from local network from 192.168.88.248:450.
But when i try to connect via cloud.myserver.lv, i get only the welcome page
Where to look? What to check?
-
I have read all the posts here, but still cant understand,
Followed all the instructions here:
[How-To] Nextcloud with Letsencrypt using OMV and docker-compose
Now I can access to Nextcloud from local network from 192.168.88.248:450.
But when i try to connect via cloud.myserver.lv, i get only the welcome page
Where to look? What to check?
You're suposed to go to 192.168.88.248:450/nextcloud to get it but you have to follow the step under "configuration of proxy" also it will be cloud.myserver.lv/nextcloud. I am trying to figure out how to just get it to be cloud.myserver.lv or for me jr.ddns.net in my case without the /nexcloud
-
I have configured to make it work as subdomain, so cloud.myserver.lv,not subfolder - myserver.lv/cloud that is why it is working as 192.168.88.248:450
-
The „Welcome Tipp our server” message means that Nginx is not properly configured. Any hints in the letsencrypt log?
You're suposed to go to 192.168.88.248:450/nextcloud to get it but you have to follow the step under "configuration of proxy" also it will be cloud.myserver.lv/nextcloud. I am trying to figure out how to just get it to be cloud.myserver.lv or for me jr.ddns.net in my case without the /nexcloud
Check post #4 of this thread
-
This is my /letsencrypt/nginx/proxy-confs/config.php
I put # in front of # 'overwritehost' => 'cloud.mydomain.lv', because it automatically redirects me from local IP to cloud.mydomain.lv where only Welcome page lives
Code
Alles anzeigen$CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'trusted_proxies' => array ( 0 => 'letsencrypt', ), 'overwrite.cli.url' => 'https://cloud.mydomain.lv', # 'overwritehost' => 'cloud.mydomain.lv', 'overwriteprotocol' => 'https', 'trusted_domains' => array ( 0 => '192.168.88.248:450', 1 => 'cloud.mydomain.lv', ),
And nextcloud.subdomain.conf looks like this
Code
Alles anzeigenserver { 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_app nextcloud; set $upstream_port 443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; # proxy_max_temp_file_size 2048m; } }
-
server_name nextcloud.*
cloud.mydomain.lv
These don’t match. Change server_name to cloud.*
-
These don’t match. Change server_name to cloud.*
Hello, if I want to access nextcloud via jrblessing.ddns.net rather than jrblessing.ddns.net/nextcloud (currently). Might you please give some recommendations? Thanks. I think I'm currently using the subfolder mode because for me both links work
-
These don’t match. Change server_name to cloud.*
Now I have error in browser when i connect to cloud.mydomain.lv from home network. Seems that it is working fine from outside
ZitatThis site can’t provide a secure connection
cloud.mydomainlv uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Im using Cloudflare.
Added my email and api to cloudflare.ini
# With global api key:
dns_cloudflare_email = cloudflare@example.com
dns_cloudflare_api_key = 0123456789abcdef0123456789abcdef01234567
THis is my docker coposer
Code
Alles anzeigenversion: "2" services: nextcloud: image: linuxserver/nextcloud container_name: nextcloud environment: - PUID=1000 - PGID=100 - TZ=Europe/Riga volumes: - /srv/dev-disk-by-label-Data/appdata/nextcloud/config:/config - /srv/dev-disk-by-label-Data/appdata/nextcloud/data:/data depends_on: - mariadb ports: - 450:443 restart: unless-stopped mariadb: image: linuxserver/mariadb container_name: nextclouddb environment: - PUID=1000 - PGID=100 - MYSQL_ROOT_PASSWORD=mypass - TZ=Europe/Riga volumes: - /srv/dev-disk-by-label-Data/appdata/nextclouddb:/config restart: unless-stopped letsencrypt: image: linuxserver/letsencrypt container_name: letsencrypt cap_add: - NET_ADMIN environment: - PUID=1000 - PGID=100 - TZ=Europe/Riga - URL=cloud.mydomain.lv - VALIDATION=dns - DNSPLUGIN=cloudflare - EMAIL=myemail volumes: - /srv/dev-disk-by-label-Data/appdata/letsencrypt:/config ports: - 444:443 - 8080:80 restart: unless-stopped
-
Hello, if I want to access nextcloud via jrblessing.ddns.net rather than jrblessing.ddns.net/nextcloud (currently). Might you please give some recommendations? Thanks. I think I'm currently using the subfolder mode because for me both links work
You should change nextcloud.subfolder.conf back to nextcloud.subfolder.conf.sample and use nextcloud.subdomain.conf instead
And make changes in letsencrypt proxy conf to make similar as mine. What exactly, i cant say while mine is not working properly
my proxy conf
Code
Alles anzeigen$CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'trusted_proxies' => array ( 0 => 'letsencrypt', ), 'overwrite.cli.url' => 'https://cloud.mydomain.lv', 'overwritehost' => 'cloud.mydomain.lv', 'overwriteprotocol' => 'https', 'trusted_domains' => array ( 0 => '192.168.88.248:450', 1 => 'cloud.mydomain.lv', ),
-
Jonlive maybe this guide helps https://blog.linuxserver.io/20…rypt-nginx-starter-guide/
-
No, this is something in my network
Data always goes shortest way. If I have server locally, when I open cloud.myserver.lv while being in the same network (e.g. Computer address 192.168.1.5 and server local address is 192.168.1.6 connection is going directly to server 65.66.12.24 and therefore ssl certificate error happens. If I go to server from other real ip e.g 67. 23.56.75 it goes from my computer ip 192.168.1.5 to some other external IP e.g. 87.25.89.43 and then to my servers address 65.23.56.75. Then ssl certificate is valid and everything happens.
Basically I need to make NAT rules in my Mikrotik router so all connections to my server goes outside my network and back
-
hi folks,
just updated my Nextcloud to 18.0.8 and do a routine check in Settings to check its all right ... but what i see: Nextcloud 19.0.2 available
anyone have done it? - some little how to about it? - something critical to know?
thx
-
Worked for me. Three warnings after upgrade in the securty check, which could be solve by
sudo -u abc php occ db:add-missing-indices
sudo -u abc php occ db:add-missing-columns
I redeployed the Nextcloud container and made sure the latest image was pulled.
-
thx!
will try it - if my omv is working again -.-
€dit: works
-
Hi, ich habe die Konfiguration entsprechend dem HowTo vorgenommen und so weit funktioniert auch alles, jedoch wenn ich aus dem LAN auf Nextcloud mit https://192.168.178.55:450 zugreife wird nach https://nextloud.your.url aufgelöst und die Verbindung doch wieder über das WAN hergestellt. Ich habe auch mal die DSL-Verbindung unterbrochen und festgestellt, dass zu Nextcloud mit https://192.168.178.55:450 im LAN keine Verbindung hergestellt werden kann. Was muss ich machen, damit der Zugriff aus dem LAN auch über das LAN abgewickelt wird?
Meine config.php und docker-compose.yml sehen folgendermaßen aus:
config.php
PHP
Alles anzeigen<?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'trusted_proxies' => array ( 0 => 'letsencrypt', ), 'overwrite.cli.url' => 'https://nextloud.your.url', 'overwritehost' => 'nextcloud.your.url', 'overwriteprotocol' => 'https', 'trusted_domains' => array ( 0 => '192.168.178.55:450', 1 => 'nextcloud.your.url', ), );
docker-compose.yml
Code
Alles anzeigenversion: "2" services: nextcloud: image: linuxserver/nextcloud container_name: nextcloud environment: - PUID=1002 #change PUID if needed - PGID=100 #change PGID if needed - TZ=Europe/Berlin #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=1002 #change PUID if needed - PGID=100 #change PGID if needed - MYSQL_ROOT_PASSWORD=mariadbpassword #change password - TZ=Europe/Berlin #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=1002 #change PUID if needed - PGID=100 #change PGID if needed - TZ=Europe/Berlin # change Time Zone if needed - URL=your.url #insert your domain name - yourdomain.url - SUBDOMAINS=nextcloud - VALIDATION=http - ONLY_SUBDOMAINS=true - EMAIL=info@your.url # 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
-
-
'overwrite.cli.url' => 'https://nextloud.your.url',
This is the culprit
-
This is the culprit
Danke, jetzt sieht's so aus und funktioniert:
-
Is there a tutorial how to add Redis to my already running nextcloud system?
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!