ken-ji

I've updated the contained dropbox.py with something built/extracted from the official sources.

Happily updated to 6.8 from 6.7.2. Don't see any issues.

I'll try to look for one...

I've never seen the tornado warnings myself. But AFAIK, its usually access issues between the dropbox app, and your files

Yeah, I saw that - I am considering my options as my personal convictions want me to use a Slackware base for the docker image, but Slackware 14.2 is old and doesn't come with a native python3 build.

The entire /mnt/user is a FUSE filesystem called shfs - which is what Unraid uses to merge all the disks together into a single virtual filesystem. Dropbox is being anal by just checking the fs in use and rejecting "unsupported" ones out of hand. Also if Dropbox wasn't being anal, storing your Dropbox files on the array would cause issues unless use cache disk is turned off, else watch Dropbox delete your files when the mover kicks in. The workaround for this is to locate the Dropbox files on a specific disk ie /mnt/disk1/Dropbox or /mnt/cache/Dropbox (like I do). Another workaround, if you must store it on the array, is to create a loopback disk image on the array and format it ext4, then mount it ie /mnt/disks/Dropbox then point Dropbox there.

I think the problem is that the data directory is in the array as there have been known issues with sqlite and the array user shares filesystem. This issue seems to be fixed in the the current RCs. For the time being you can put the docker data in /mnt/cache/Dropbox via the settings and editing the Container Path: /dropbox/Dropbox You might want to show the Host path settings that you have so we can see why yours became /mnt/user/Dropbxox/Dropbox If you do this *changing the location of the Dropbox files*, make sure to either start fresh with empty Dropbox and appdata directories, or move the files in as Dropbiox might decide you emptied your folder and proceed to nuke all your files.

I think the error is because when you run Dropbox on the array, it correctly sees the filesystem as shfs which is artificially unsupported. Some users have just created a ext4 loopback image. I suppose with the container working again, you can have it on the cache drive

you'll need to delete .dropbox-dist from the appdata folder - by default /mnt/user/appdata/dropbox the broken versions have left incomplete .dropbox-dist folders which is now screwing it up.

I've rebuilt the docker image. and it seems to be running on my setup (but I have not linked it to my account as I do not have a free slot at the moment) as an FYI, the docker image is built with whatever is the latest dropbox download available. While the container is running, it can upgrade itself (as the dropbox app expects to be able to do so) and the upgrade is stored in the appdata folder. So the container in theory should never become too old (unless Dropbox deprecates the app), but I need to rebuild the docker image to contain a fresh app version. It should be possible to add routines to upgrade the docker container after install, but I'll need to see and test that approach.

Apologies, as I've been busy with a whole bunch of other things, living away from my server, and am considering relegating Dropbox to a lower usage tier - because I don't like their decision to limit the free tier to 3 or less devices. I'm going to rebuild the docker image and see if it still works.

Finally took a look and i probably won't be using this thing as a docker - it requires way too many capabilities than what I'd like to limit it too. Its very nature is that the docker needs to be in host mode to create multiple bridges and connect the client to a bridge then mess with the firewall rules to allow whatever you have. I'm sure I was hitting conflicts with my setup but yeah I never go it to work with my LAN at all. This might one of those applications I'd rather it run as a VM. But I might have a better look with this when I have time, hoping somebody else works out the issue. In hindsight just realized the reason I couldn't even get it to work is that I set the thing to routed mode for everything, but OpenVPN-AS does not readily show you all the subnets they generated, which needed to be programmed into my router. Talk about complicated if you are trying to do all of this remotely.

I'm going to have to give this a try. I'm not using the openvpn-as container myself (though I used to) as I've left VPN capabilities to a VPS that my router has an IPSEC connection with - since my provider is slowly rolling out CGNAT and I got selected as an early bird with no way out it seems. (Business grade plans need you to be a real business and no other non CGNAT ISP provider in the area)

The only thing I see that could be wrong is that your openvpn-as copintainer is in host mode right? if so, make sure its bound to br0 not eth0 (I think that's how bridges should be used.) Does the openvpn-as container work in custom network mode work? (set to br1 with own IP address)

@Jenardo can you show the actual network settings? ip addresses and routes? and the same info from within the openvpn-as container?

Also, if you have VLAN support, your docker network on the vlan is able to talk to unraid. AFAIK, openVPN works very well with its own dedicated IP ( as long as the docker network is either on a different VLAN, or interface from the Unraid )

Running a Mikrotik hEX Router https://mikrotik.com/product/RB750Gr3 Its quite a bit of a learning curve for people coming from "point-n-click routers" but should be fairly straightforward for most technical users. What I really like about it is the QoS (quite a challenge) capability, and the support for VPN options (though still missing OpenVPN in UDP mode) There are some rough spots still like the built in DNS server only supporting A/AAAA records (but has regex matching) It also has builtin AP management (these need to be Mikrotik AP though) so new APs just need to be plugged in to the network and told to look for the head unit. The main feature I've loved about it until my ISP started placing users on CGNAT is how easy it is to create a site-to-site VPN between routers, just plug in the public IP on both ends and you are done.

Been an Unraid user for 4+years and counting. Convinced my brother to have one at his house to manage his stuff using old hand me down parts without real issues (save for the impossibility to automatically upgrade in the latest versions with only 2GB of RAM). Never had major issues or surprise gotchas. Still have an unused license from the old pro two packs

I'm considering dropping this Dropbox image given that I'm personally moving away from Dropbox, because of their limit to 3 devices policy. I'm experimenting on rclone and checking on how I can work with my workflow on it. That said, I'd like to look into a way to automate dropbox + fixed size loopback image for the Dropbox data directory.

Create a user, and use that user to connect to the share. The root account is not allowed to connect to shares over the network, unless the share is in Guest mode

Except the NVidia build is not a Limetech build but a community addon. Maybe if the guys added traps to the Unraid OS update mechanism as part of their plugin... but until then, user beware.

Upgraded from 6.7.0 remotely without issue.

My entire array is in an external JBOD enclosure

Yes. That's my setup. The secondary NIC is used to create a docker network on the same IP space as the host and all the needs to be local IP dockers are there.