Posts by KM0201

post the output of:

id your_username

then

ls -l /path/to/share

obviously your_username is you omv username, and /path/to/share is whatever path you're having issues with.

You having a user doesn't change my opinion on doing this.

To quote myself from reddit:

I personally wouldn't do it, and I sure as hell wouldn't do it everyone read/write.

Like I said.. can you? Yes. Should you? My personal opinion is no. Use the system the way it was designed.

As I told you on Reddit, you can do this, but I wouldn't (below is just one reason).

Next cloud OMV5 RPI

Create a folder, "6T" for example... and organize all your data that users will access (music, movies, documents, etc..) under that folder. Anything users don't need access to (Container folders, etc.).. put outside of the 6T folder.

Quote from Reekon

After we setup OMV5 over Debian, is the user account (created during setup) useful for anything? Does the default admin account need to be the main admin account? Can it be deleted?

I would keep a user account, but that's juts me. If you want to delete it, and then add one via the webUI, you can do that as well

You can give users admin privileges, but I don't think you can delete the admin account (I'm not sure why anyone would want to do either, but it comes up constantly for some reason)

Quote from cmmc01988

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:

Code

root@raspberrypi:/# ls -l /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/media/nextcloud
total 4
drwxrwxrwx 1 root root 4096 Jun 15 09:21 data
root@raspberrypi:/#
root@raspberrypi:/#

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

ls -l /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/

That is probably going to shoot the same permissions as everything else, thus affecting the permissions of everything under it.

Quote from Soma

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:

Code

pi@xxxxxxxx:~ $ ls -al /srv/dev-disk-by-label-wolf1/@data/nextcloud/
drwxrws--- 1 pi   users 248 Feb  2 22:21 data

Code

pi@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

Display More

If you have created the folder previously, it might give issues

Display More

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)

ken@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:~$ 

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

chmod -R 0770 /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/media/nextcloud/data

Quote from cmmc01988

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:

Code

ls -l /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/media/nextcloud/data

Outputs this:

Code

root@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

Quote from ryecoaaron

I added it a year ago - https://github.com/OpenMediaVa…cdb5127a58cccc19974af6b7e

All you have to do click install Docker again. This will update the drive list and docker-compose.

That's probably the reason we've seen less and less of this problem. Honestly wasn't aware you'd made an effort to resolve that.

Quote from cmmc01988

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..

ls -l /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/media/nextcloud/data

I can't understand where you're going wrong.

Question, did you create the folder 'Appdata' in the webUI?

Quote from cmmc01988

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

Display More

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

On the OMV webUI for most browsers,

Hold Control, and hit F5 (or click your browsers Refresh Button). This will clear the webUI cache and reload everything, w/o having to clear your entire web cache.

Quote from uaytac

The last row repeated and I have deleted it from the log.

cc.txt

Did you setup a mysql database root password, etc?

Quote from David B

I made this change and it worked! I don't quite understand what the implications are to deleting the files that ryecoaaron mentions in his post though. I assume that the change was never integrated into OMV-extras though.

Oh I have no doubt what he said worked... that wasn't the question. Even he mentioned though there's a limitation as it's not going to auto update if drives are removed/added... the delay script doesn't have that limitation.

Quote from uaytac

How can I check database container error logs?

If you named your database container nextclouddb, as the tutorial suggests

docker logs -f nextclouddb

Well the nextcloud container looks OK, so I have no idea what could be wrong.

Is your nextcloud database container throwing any log errors?

I've never personally had a database error w/ nextcloud... so this would surprise me unless you're doing something weird.

post the output of (you might need to edit out your url)... but if it's a config issue, you should get a repeated error showing which line the error is on. You had to change the config file during the setup of the container.. your edits are in there.

docker logs -f nextcloud

(use Cntrl C to exit the log)

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)

Quote from macom

Maybe you installed omv-extras/docker before this was implemented. But you can retrofit it as described in the post.

Interesting.

I'd never seen that solution, I always just suggested the delay script you posted a couple years ago (and have always heard back that it worked perfectly). I'm assuming this would work fine, but I think the delay script might be a more permanent solution given it doesn't self update... Especially since we are talking Pi's and other SBC's which may have drives getting moved around, etc.

Choices... 1 isn't enough, 2 is to many...

Quote from Agricola

I was curious about that too. Your trusted_ domains and trusted _proxies are identical.

That's how I've always set it up, never referenced the swag container (although I know some do). The trusted proxy, is because if you don't do that, it will throw an "error" under basic settings in Nextcloud (or at least I always do, maybe because I don't reference swag, that is why). It's really not an error, as if you actually read it it's confirming the proxy is working... I could remove my IP address, as I disable local access anyway, but usually when I add this line I just copy/paste my trusted domains. The IP address is just so if you want to enable local access without getting a security warning.... Otherwise you can just delete that line. I disable local access from my stack/docker-compose... so I should probably delete it anyway, I just never have.

RE: Nextcloud Bad Gateway

Quote

Some users may also get this error.

Code

There are some warnings regarding your setup.

The reverse proxy header configuration is incorrect, or you are accessing Nextcloud from a trusted proxy. If not, this is a security issue and can allow an attacker to spoof their IP address as visible to the Nextcloud. Further information can be found in the documentation.

If you read it, this isn't an error at all and simply confirms you're accessing nextcloud from a trusted proxy. However, to clear this, is very simple.

1. navigate to /config/nextcloud/www/nextcloud/config

2. nano config.php

3. Add the following at the end, before the );

Code

  'trusted_proxies' =>  
  array (    
    0 => 'your.ip:450',    
    1 => 'nextcloud.YOUR_SUBDOMAIN.duckdns.org',  
),

4. docker restart nextcloud

5. When done, refresh your nextcloud settings page and all errors should be clear.

Display More