Maybe I'm totally off base, but i seem to remember reading somewhere that duckdns did not allow subfolders (I've always used subdomains, so I never put it to the test)
Next cloud OMV5 RPI
-
-
Maybe I'm totally off base, but i seem to remember reading somewhere that duckdns did not allow subfolders (I've always used subdomains, so I never put it to the test)
When I first follow the guide, I was doing subfolder with no issues.
Only after having it running, I changed to subdomain so, long story shorted: yes, it works but with an access as:
-
I also found a different config file to before?
Ok, there's still errors hapening on your config but the one I really don't understand is line #13: 'version' => '17.0.1.1',
It should be 21.0 something.
Also, lines #51 to line #59 must be above line #50. The "config.php" always ends with );
It's better to delete everything and start over. According to your paths, you have to run:
rm -rf /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/Appdata/appdata/swag
rm -rf /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/Appdata/appdata/nextclouddb
rm -rf /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/Appdata/appdata/nextcloud/config
rm -rf /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/Appdata/appdata/nextcloud/data
If you don't have any other files under Appdata other than those folders just delete all:
rm -rf /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/Appdata
After that, simplify the path to a shorter one (you have "appdata" under "Appdata"):
Code
Alles anzeigenversion: "2" services: nextcloud: image: linuxserver/nextcloud:latest #<<- To prevent Portainer DL all images (been happening) container_name: nextcloud environment: - PUID=1000 - PGID=100 - TZ=Europe/London volumes: - /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/appdata/nextcloud/config:/config - /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/media/nextcloud/data:/data depends_on: - mariadb ports: - 450:443 restart: unless-stopped mariadb: image: linuxserver/mariadb:alpine #<<-- Instead of Bionic. Prevents issues with Nextcloud v21 container_name: nextclouddb environment: - PUID=1000 - PGID=100 - MYSQL_ROOT_PASSWORD=MYPASSWORD - TZ=Europe/London volumes: - /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/appdata/mariadb/config:/config restart: unless-stopped swag: image: linuxserver/swag:latest #<<-- To prevent Portainer DL all images (been happening) container_name: swag cap_add: - NET_ADMIN environment: - PUID=1000 #change PUID if needed - PGID=100 #change PGID if needed - TZ=Europe/London - URL=MYDOMAIN.duckdns.org - SUBDOMAINS=wildcard #<<-- All containers will have a cert - VALIDATION=duckdns - DUCKDNSTOKEN=yourTOKENfromDUCKDNS - EMAIL=MYEMAIL volumes: - /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/appdata/swag/config:/config ports: - 444:443 - 81:80 restart: unless-stopped
-
Thanks Soma,
I've removed everything and started again. I got to the login/install page but now just get:
Error
- Your data directory is readable by other users
Please change the permissions to 0770 so that the directory cannot be listed by other users
- Your data directory is readable by other users
-
Thanks Soma,
I've removed everything and started again. I got to the login/install page but now just get:
Error
- Your data directory is readable by other users
Please change the permissions to 0770 so that the directory cannot be listed by other users
Did you reinstall w/ the old data directory? I'm assuming so. Unless you have a reason not to, I would delete all associated directories , then run the stack/docker-compose file, and let it create the directories. If you're gonna start over, really start over
- Your data directory is readable by other users
-
Did you reinstall w/ the old data directory? I'm assuming so. Unless you have a reason not to, I would delete all associated directories , then run the stack/docker-compose file, and let it create the directories. If you're gonna start over, really start over
I created the docker-compose file using Somas example above after deleting all directories that I could find from my multiple failed installs.
-
I can't understand where you're going wrong.
Question, did you create the folder 'Appdata' in the webUI?
-
I created the docker-compose file using Somas example above after deleting all directories that I could find from my multiple failed installs.
Also, please post the output of this command..
-
Ok my SD card died so i've installed everything from scrratch but I still get:
NextcloudError
- Your data directory is readable by other users
Please change the permissions to 0770 so that the directory cannot be listed by other users.
Nextcloud – a safe home for all your data
The command:
Outputs this:
Coderoot@raspberrypi:/# ls -l /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/media/nextcloud/data total 8 drwxrwxrwx 1 root root 0 Jun 15 09:21 Craig drwxrwxrwx 1 root root 0 Jun 15 09:21 appdata_ocenhlql2o57 -rwxrwxrwx 1 root root 0 Jun 15 09:21 index.html -rwxrwxrwx 1 root root 7738 Jun 15 09:21 nextcloud.log
- Your data directory is readable by other users
-
It appears your drives root directory is set to read/write by everyone. This is a terrible practice, IMO.. but that is another story. I'm assuming when you create the directory /media/nextcloud/data, it is inheriting the permissions of the root directory, thus causing your error....
You can *TRY* this, but I'm not sure you'll have much luck, given the permissions that are above the nextcloud folder..... it might fix the problem.. but there's a good chance at some point the permissions will be overwritten by the root directory again.
You really need to properly set permissions on your drive
Nextcloud
Error
- Your data directory is readable by other users
Please change the permissions to 0770 so that the directory cannot be listed by other users.
Nextcloud – a safe home for all your data
The command:
Outputs this:
Coderoot@raspberrypi:/# ls -l /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/media/nextcloud/data total 8 drwxrwxrwx 1 root root 0 Jun 15 09:21 Craig drwxrwxrwx 1 root root 0 Jun 15 09:21 appdata_ocenhlql2o57 -rwxrwxrwx 1 root root 0 Jun 15 09:21 index.html -rwxrwxrwx 1 root root 7738 Jun 15 09:21 nextcloud.log
- Your data directory is readable by other users
-
Run instead ls -l /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/media/nextcloud
It must be "pi:users" since it was created via the YML but it will have a special flag:
Codepi@xxxxxxxx:~ $ ls -al /srv/dev-disk-by-label-wolf1/@data/nextcloud/ drwxrws--- 1 pi users 248 Feb 2 22:21 data
Code
Alles anzeigenpi@xxxxxxxx:~ $ ls -al /srv/dev-disk-by-label-wolf1/@data/nextcloud/data/ total 46884 drwxrws--- 1 pi users 248 Feb 2 22:21 . drwxr-sr-x 1 root users 8 Apr 5 14:51 .. -rw-r--r-- 1 pi users 542 May 27 21:41 .htaccess -rw-r--r-- 1 pi users 0 May 27 21:41 .ocdata drwxr-sr-x 1 pi users 146 Feb 3 22:20 appdata_xxxxxxxxx drwxr-sr-x 1 pi users 62 Mar 29 20:25 xxxxxxxxxx drwxr-sr-x 1 pi users 26 Feb 24 20:08 files_external -rw-r--r-- 1 pi users 0 May 27 21:41 index.html drwxr-sr-x 1 pi users 20 Feb 2 17:53 xxxxxxxxxx -rw-r----- 1 pi users 47934624 May 29 23:51 nextcloud.log drwxr-sr-x 1 pi users 34 Apr 6 16:28 xxxxxxxxxx drwxr-sr-x 1 pi users 74 May 27 21:41 updater-xxxxxxxxxx -rw-r--r-- 1 pi users 66477 May 27 21:41 updater.log
If you have created the folder previously, it might give issues.
Zitat- s – This indicated the setuid/setgid permissions. This is not set displayed in the special permission part of the permissions display, but is represented as a s in the read portion of the owner or group permissions.
Understanding Linux File Permissions - Linux.com
Changing any permissions after it's running, I trust it will create more issues
-
KM0201, Tried that command but didnt work. I'm not sure how my permissions have ended up like that! I did have a plugin installed that allowed users to create folders within root, I've unistalled that now.
Soma, this is what I get when i run that command:
-
Run instead ls -l /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/media/nextcloud
It must be "pi:users" since it was created via the YML but it will have a special flag:
Codepi@xxxxxxxx:~ $ ls -al /srv/dev-disk-by-label-wolf1/@data/nextcloud/ drwxrws--- 1 pi users 248 Feb 2 22:21 data
Code
Alles anzeigenpi@xxxxxxxx:~ $ ls -al /srv/dev-disk-by-label-wolf1/@data/nextcloud/data/ total 46884 drwxrws--- 1 pi users 248 Feb 2 22:21 . drwxr-sr-x 1 root users 8 Apr 5 14:51 .. -rw-r--r-- 1 pi users 542 May 27 21:41 .htaccess -rw-r--r-- 1 pi users 0 May 27 21:41 .ocdata drwxr-sr-x 1 pi users 146 Feb 3 22:20 appdata_xxxxxxxxx drwxr-sr-x 1 pi users 62 Mar 29 20:25 xxxxxxxxxx drwxr-sr-x 1 pi users 26 Feb 24 20:08 files_external -rw-r--r-- 1 pi users 0 May 27 21:41 index.html drwxr-sr-x 1 pi users 20 Feb 2 17:53 xxxxxxxxxx -rw-r----- 1 pi users 47934624 May 29 23:51 nextcloud.log drwxr-sr-x 1 pi users 34 Apr 6 16:28 xxxxxxxxxx drwxr-sr-x 1 pi users 74 May 27 21:41 updater-xxxxxxxxxx -rw-r--r-- 1 pi users 66477 May 27 21:41 updater.log
If you have created the folder previously, it might give issues
I don't see where the difference in the path matters, since it is complaining about the data drive (which he has marked to /media/nextcloud/data)
His permissions are still completely out of whack (.Nextcloud is my data directory)
Code
Alles anzeigenken@openmediavault:~$ ls -l -a /srv/dev-disk-by-label-D1/Disk_1/Media/ total 112 drwxrwsr-x 15 ken users 4096 Jun 11 08:14 . drwxrws---+ 4 ken users 4096 Jun 4 19:48 .. drwxrwx--- 5 ken users 4096 Jun 11 02:24 .Nextcloud drwxr-sr-x 2 ken users 4096 Dec 22 2019 .Playlists drwxr-sr-x 2 ken users 4096 Dec 22 2019 .Podcasts drwx--S--- 5 ken users 4096 Dec 2 2019 .Trash-1000 drwsrwsr-x 4 ken users 36864 Jun 7 10:31 Movies drwxrwsrwx 249 ken users 12288 Jan 21 09:55 Music drwxrwsr-x 4 ken users 4096 Jan 2 2020 Photos drwxr-sr-x 16 ken users 4096 Jun 1 14:28 Piwigo drwxrwsr-x 2 ken users 12288 May 31 08:46 Random_Videos drwxr-sr-x 4 ken users 4096 Jun 11 09:12 Syncthing drwxrwsr-x 42 ken users 4096 May 28 12:17 TV drwxr-sr-x 6 ken users 4096 Nov 12 2020 Torrents drwxrwsr-x 35 ken users 4096 Jun 1 15:22 eBooks ken@openmediavault:~$ ls -l /srv/dev-disk-by-label-D1/Disk_1/ total 8 drwxrws--- 7 ken users 4096 Jun 4 21:25 Data drwxrwsr-x 15 ken users 4096 Jun 11 08:14 Media ken@openmediavault:~$ ls -l /srv/dev-disk-by-label-D1/ total 32 drwxrwsr-x 12 ken users 4096 Jun 11 08:53 AppData drwx--x--x 14 root users 4096 Jun 10 17:43 Containers drwxrws---+ 4 ken users 4096 Jun 4 19:48 Disk_1 drwxrwsr-x+ 3 root users 4096 Mar 9 03:36 Home drwx------ 2 root root 16384 Mar 24 2020 lost+found ken@openmediavault:~$
-
How are you launching the YML? With what user?
What is the output of:
ls -al /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/appdata/nextcloud/
-
KM0201, Tried that command but didnt work. I'm not sure how my permissions have ended up like that! I did have a plugin installed that allowed users to create folders within root, I've unistalled that now.
Soma, this is what I get when i run that command:
His command is going to show the same as mine, that's not in debate. It's clearly inheriting permissions from the root directory of the drive.
My hope was the chmod command would change the nextcloud folder, but clearly it didn't. When I'm talking about the root directory, I don't mean root directory of your OS drive (which I think is what that plugin does), I mean the root of the data drive.
What is the output of
That is probably going to shoot the same permissions as everything else, thus affecting the permissions of everything under it.
-
I don't see where the difference in the path matters, since it is complaining about the data drive (which he has marked to /media/nextcloud/data)
For comparing the Permissions,
As you see on your's, it also as the "s" flag.
Yeah, having that plugin sharing the root of the external drive have given weird permissions.
[EDIT]Or maybe it's because He's logged as root and maybe launching the YML as "root"?!?
-
Running Command:
gives this:
Code
Alles anzeigen$ ls -l /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/ total 12 drwxrwxrwx 1 root root 0 Jun 1 15:33 '$RECYCLE.BIN' drwxrwxrwx 1 root root 8192 Jun 15 08:43 Appdata drwxrwxrwx 1 root root 4096 Jun 4 11:35 Data drwxrwxrwx 1 root root 0 Jun 16 11:44 Films2 drwxrwxrwx 1 root root 0 Jun 1 15:44 Pictures3 drwxrwxrwx 1 root root 0 Jun 1 15:40 'System Volume Information' drwxrwxrwx 1 root root 0 Jun 16 10:24 TVSeries2 drwxrwxrwx 1 root root 0 Jun 15 08:58 appdata drwxrwxrwx 1 root root 0 Jun 15 09:08 dev-disk-by-uuid-20A00CCAA00CA7FC drwxrwxrwx 1 root root 0 Jun 8 11:15 duckdns drwxrwxrwx 1 root root 0 Jun 15 08:58 media $
and running:
hives this:
Codetotal 4 drwxrwxrwx 1 root root 0 Jun 15 08:58 . drwxrwxrwx 1 root root 0 Jun 15 08:58 .. drwxrwxrwx 1 root root 4096 Jun 15 08:58 config
When I created myt user profile in OMV I added it to all groups so it does have root access
-
You seem to use a NTFS drive, correct?
I think it won't do, Linux don't deal with NTFS permissions well.
As far as my knowledge goes, you need a (at least) ext4 filesystem.
-
Are you saying that NTFS is Not The File System for OMV?
-
You seem to use a NTFS drive, correct?
I think it won't do, Linux don't deal with NTFS permissions well.
As far as my knowledge goes, you need a (at least) ext4 filesystem.
I've never heard NTFS causing this much of a problem, but I'm at a loss as to what else it could be.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!