Output from db show databases;
Nextcloud and Letsencrypt (swag)
-
- OMV 5.x
- MarcS
-
-
-
to check if your nextcloud container can resolve the connection to the database container via host name: sudo docker exec -it nextcloud bash -c "ping -c 4 swag"
-
I know this is late, but I've been working on the same thing....I've had a heck of a time trying to get everything just right...spent about 5 days on it. I originally tried to mount SMB shares to the docker ( those are the volumes I declared as external)
Codesudo docker volume create --driver local --opt type=cifs --opt device=//<IP>/NextCloud/files --opt o=username=nextcloud,password=<SMB share password>,uid=33,gid=33,file_mode=0777,dir_mode=0777 nextcloudData # the GUID 33 is www-data user to sudo docker volume create --driver local --opt type=cifs --opt device=//<IP>/NextCloud/config --opt o=username=nextcloud,password=<SMB share password>,uid=33,gid=33,file_mode=0770,dir_mode=0770 nextcloudConfig
Still working on the SWAG part, but here is my docker compose file:
Code
Alles anzeigenversion: '3.3' volumes: nextcloudHTML: nextcloudData: external: true nextcloudConfig: external: true nxtdb: networks: nextCloudPrivate: webservicesNet: external: name: webservicesNet services: nxtclddb: image: mariadb container_name: nxtclddb hostname: nxtclddb restart: unless-stopped command: --transaction-isolation=READ-COMMITTED --binlog-format=ROW volumes: - nxtdb:/var/lib/mysql:z - /etc/localtime:/etc/localtime:ro environment: - MYSQL_ROOT_PASSWORD=<SQLROOTPW> - MYSQL_PASSWORD=<anotherUserPASSWORD> - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud networks: - nextCloudPrivate nextcloud: image: nextcloud container_name: nextcloud hostname: nextcloud ports: - "4545:80" restart: unless-stopped volumes: - /etc/localtime:/etc/localtime:ro - nextcloudHTML:/var/www/html:z - nextcloudData:/var/www/html/data:z - nextcloudConfig:/var/www/html/config:z environment: - MYSQL_HOST=nxtclddb - MYSQL_PASSWORD=<anotherUSERPAssword> - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud - NEXTCLOUD_ADMIN_USER=admin - NEXTCLOUD_ADMIN_PASSWORD=<NEXTCLoudWEBAdminPassword> - NEXTCLOUD_TRUSTED_DOMAINS=""nextcloud.* localhost <my site example url>/nextcloud"" networks: - nextCloudPrivate - webservicesNet
-
tried to mount SMB shares to the docker
You can access SMB shares from Nextcloud using the "external storage app" which can be installed from within Nextcloud
-
You can access SMB shares from Nextcloud using the "external storage app" which can be installed from within Nextcloud
macom do you use this app? Is it possible to dig down and select just a subfolder in a SMB share?
Update: Reading the documentation. I see that I can. Now to figure how to write the file path, and if it will take a local ip.
Update2: Ha-wee! It works.
-
macom do you use this app? Is it possible to dig down and select just a subfolder in a SMB share?
Update: Reading the documentation. I see that I can. Now to figure how to write the file path, and if it will take a local ip.
Update2: Ha-wee! It works.
Can you tell me how you did it ?
I'm trying to get a shared OMV folder into Nextcloud, but I can't connect it with the external storage app.It seems I can't reach the IP of my server in the docker-container
-
Is the shared folder shared by smb?
Which image are you using for nextcloud. I read several times, that the official nextcloud image has samba not installed. One reason I use letsencrypt/nextcloud
-
Yes, the shared folder is shared by smb an I can use it via my Windows Client.
I've setup Nextcloud by this how to here in the forum: [How-To] Nextcloud with Letsencrypt using OMV and docker-compose (from you ?
-
Post a screenshot of your settings in the external storage app
-
-
Name of the shared folder in OMV is "FTP"?
That share is added to smb/cifs?
I did not tick "verify ACL..."
The user should be a user that has access to the smb/cifs share, so a user that you gave privileges in the GUI of OMV to that share.
-
Yeah, that was the trick. Thouhgt I could mount it with root, after changing user to my windows user it works.
THX !!!
-
I think if you add your IP address to the field Domain it also works (with ACL verify ticked)
-
Is it also possible to access Nextcloud via the local IP-Adress ?
When I try to access via https://192.160.10.1:443 I only get the swag screen:
-
Is it also possible to access Nextcloud via the local IP-Adress ?
When I try to access via https://192.160.10.1:443 I only get the swag screen:
Quote to "watch" this thread.
How did you configured SWAG/NC? As a *subfolder*? Or as a *subdomain*?
I have subdomain configured and can't access via LAN.
-
Is it also possible to access Nextcloud via the local IP-Adress ?
When I try to access via https://192.160.10.1:443 I only get the swag screen:
Have you seen this in the docker-compose file?
If you uncoment these lines, you should be able to reach nextcloud by
Edit:
-
tschensie Your host IP is: 192.168.10.1 ?????
I always thought that *.*.*.1 are dhcp servers
Sorry to take advantage of the this but, I did it that way.
Then added my host IP (other time I used hostname) to the "trusted domains" array of "nextcloud....config.php" with port and without and, nothing.
Maybe, since I'm using wireguardVPN to the LAN, something is different in the setting I need to make, O.o
If it adds any info, I'm using subdomain on SWAG.
-
and, nothing.
Changed the post. You need to add https://
just IP and port does not work for me
-
Changed the post. You need to add https://
just IP and port does not work for me
Ok, that makes more sense now.
Will try it in a few hours:
1 - Uncomment the 2 lines on docker-compose.yml
2 - docker-compose up -d nextcloud
3 - Check the "config.php" to see if the "trusted domains" array is correct and edit it accordingly.
4 - docker restart nextcloud
5 - docker logs -f nextcloud
Then try to access it via "https://myLANip:450" and fingers crossed,
[EDIT#1]
Ok, I've managed to reach NEXTCLOUD by https://myIP:450 while "VPN wireguarded" but I think it's making it jump to the "full web address" because of this lines on the "config.php"
Code'trusted_domains' => array ( 0 => 'https://LAN IP of HOST:450', <<<< ---- as talked above with @macom ---^^^^ 1 => 'nextcloud.my.url', <<<< ---- as instructed for access with "nextcloud.subdomain.conf" via Reverse Proxy SWAG ), 'overwrite.cli.url' => 'https://nextcloud.my.url', <<<< --- I think that this 'overwritehost' => 'nextcloud.my.url', <<<< --- and this is what forces it to change the IP to web address 'overwriteprotocol' => 'https',
As soon as I deactivate "wireguard connection", connecting to "https://myLANip:450" dies out with "Hmmm... it's not possible to access this page...." which is a good sign. It means that when on VPN, it accepts me as on LAN.
Maybe If I try to login via LAN and after deactivate the VPN, something will present itself., [EDIT#2] <<<<<----- SEE BELOW
Or maybe even better would be an enhancement setting that "If connected on the IP Range then go on LAN else go WAN" (my REALLY poor attempt on doing PROGRAMMING, )
[EDIT#2] Ok, it seems it worked. After login into NC, went to the "Settings->System" area and deactivated the "VPN" and NC shouted " Lost connection to the server".
After clicking anywhere else, it immediately resumed the page (I'm assuming it started using the WAN that I'm using) so, all is good.
I think I can only fully test this when I'm at home and try to sync/send some files (maybe some heavy ones) and see how fast the upload is.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!