dlandon

Watch for special characters in the user and password.

Stop all dockers and then start them one at a time. You should see them work until you get to 4 or 5 , if I remember correctly, and then they will start to give the issue.

Maybe not, but until linux or limetech fixes it, it's the only thing I found to get around the problem.

It also seems to depend on how many dockers have a static ip.

Based on your post, what is the reason you want this?

Post diagnostics so we can help you.

Limetech is concerned about security and I appreciate their efforts towards better security. Just because it is an inconvenience is no reason to blow past good security. In the beta testing there were issues that surfaced about trying to run scripts from the flash drive. Several of my plugins had to be modified to run scripts from /tmp. Running a script from the flash under 6.8 is as simple as copying the script to /tmp and execute it from there. I'm not sure why you would want to do this anyway. 'User Scripts' can be used to run custom scripts. Limetech is working on a more automated way to have the flash device backed up to the cloud as changes on the device occur. Until that is ready for prime time, find an alternative to backing up the flash. You could use 'User Scripts' to do a timed backup.

I saw this issue in the beta testing of 6.8. I solved it by remapping the ip addresses of my dockers. You probably have unique ip addresses set up for your dockers. Set the network type to something other than 'Custom:br0'. This will then use the ip address of the Unraid server. Assign a unique port to the docker and access the docker that way.

Put the data in the data directory.

You need to remove the docker, and the owncloud appdata and start over.

This is where the data goes. Move your data there. This is not correct. It should be: 'datadirectory' => '/data', When you started ownCloud the first time, this is the setting used for the data.

This is an incorrect mapping. If you just did the manual update, you need to check your work. It should be: mnt/user/appdata/ownCloud/www/owncloud/ With the owncloud files showing in that directory.

I'm very confused. What does "no window would appear" mean? What does "SSL does work but not webUI" mean? You'll have to provide more meaningful information. Show a screen shot of what is or is not working.

The deleted files don't replace files in the recycle bin. They are versioned.

Never seen or had any reports of the recycle bin doing that. I suspect the files were corrupted when they were deleted.

Just remove the historical device.

It's probably because you had the disk in UD and then put it in the array. Please show a screen shot and post diagnostics.

Your best bet is to restore from a backup. Once you've restored the files, set the 'filesystem_check_changes' to '1' in config.php and ownCloud will re-synch the database to the actual files found. If you have another computer synching with ownCloud, you might be able to restore the files that way.

I see several issues you need to look into: Sep 24 19:45:56 MIKESDESKTOP kernel: CIFS VFS: Autodisabling the use of server inode numbers on \\WORKHORSE\SABnzbd. This server doesn't seem to support them properly. Hardlinks will not be recognized on this mount. Consider mounting with the "noserverino" option to silence this message. Sep 25 01:55:14 MIKESDESKTOP shfs: cache disk full Sep 25 07:33:16 MIKESDESKTOP move: error: move, 397: No such file or directory (2): lstat: /mnt/cache/Media/Television/The Good Doctor/Season 03/The Good Doctor - s3e01 - Disaster [WEBDL-1080p] [h264 AC3] [ 5.1 Audio] [8bit].mkv Sep 25 08:01:07 MIKESDESKTOP kernel: Status code returned 0xc000006d STATUS_LOGON_FAILURE Sep 25 08:01:07 MIKESDESKTOP kernel: CIFS VFS: Send error in SessSetup = -13 This last one would imply incorrect credentials.

Remove the preclear plugin to start.

It can sometimes take a while before showing up as an SMB share. Turn it on and give it several minutes. It will show up. It's not always immediate.

There's a reason you can't enter that password in the GUI.

The '@' symbol is not allowed.

Don't know. I don't follow the development that closely.

The docker now sets up the hook processing and installs all the correct files so you no longer have to do a manual setup. I recommend you do the following: - Remove the Zoneminder docker. - Remove the appdata/Zoneminder/hook folder. - Go to CA and use the latest Zoneminder template and set the new hook variables for your needs. - Apply your settings to the objectconfig.ini file.