gr8zatara

What I would do is make a dropbox that only has a few files so it doesn't take so long to see what goes wrong. Can you please send a pic of your docker container config screen?

So after messing around with settings and linking /opt/dropbox in container to some folder inside the container's Dropbox settings in appdata. Basically, I made a Russian nesting doll that caught on fire. This made me have to delete the entire directory and start the whole Dropbox container like it was my first time installing. So here is the steps to make it work in middle/late 2023. - there are other Dropbox 'apps' in community apps tab of unraid but this is the best one, thanks @mgutt! - first, log into your Dropbox and make sure you don't have 3 devices linked to your Dropbox if you're using their free tier pricing. - then after the docker container template windows pops up in unraid, change the 'repository' to 'otherguy/dropbox:1.9.0' otherwise if you use the latest Dropbox version, it will give you '[ALERT]: Dropbox needs to rename your existing folder or file named Dropbox to finish installing. Please close any open documents and try again.' endless cycle after you link your machine to their server. - add the 'DROPBOX_SKIP_UPDATE=true' variable to template before spinning up the container. - look in log for url link to authorize your device on their server, copy and paste that in browser and get that done. - when you look back in the log, it will cycle through 'syncing' forever. - this is because the version you're using is 1.9.0 and you told it to NOT update to latest. - stop the container, change repository to 'otherguy/dropbox', set the variable you made, 'DROPBOX_SKIP_UPDATE=false' so it can update to newest once container spins up. Finally, in advance view toggle near top, add '--restart unless-stopped' in extra parameter line, because this container will sh*t the bed from time to time due to Linux Dropbox being the second rated citizen red headed step child of the Dropbox team - spin up the container again, and watch it update and start syncing in the log. Sit back and enjoy! This took me 2 days to fix and figure out because during this time, something screwy happened in dropbox's server side. It decided to give me a new 'Please visit https://www.dropbox.com/cli_link_nonce?xxxxx to link this device' with a new number every second so I couldn't get it done. It ended up fixing itself after 2 days on it's own. I even tried the solution here: https://www.dropboxforum.com/t5/Create-upload-and-share/Audio-files-not-showing-on-Linux-Fedora-mounted-directory/m-p/702489#M72240 I was as happy as a teenage girl at a Taylor Swift concert when I finally got same authorized request link for more than a second to link my computer to Dropbox only to get a '[ALERT]: Dropbox needs to rename your existing folder or file named Dropbox to finish installing. Please close any open documents and try again.' endless cycle. I threw a tantrum like a trans lost in middle of a Trump rally and finally came here to find ideas on how to fix it, so here is my write-up to hopefully help you future unraider use the Dropbox in unraid without going through what I endured, Cheers!

I can confirm that as of 8/23/2020, if you create a fresh install of Firefly-III (v.5.3.3), you need to do the following. 1. spin up a mariadb container. 2. create the database, user , and password for user as firefly container will not but expect it to be there. a. console into mariadb container b. type following: mysql -uroot -p <enter the root password you created in spinning up the mariadb container> CREATE USER 'firefly' IDENTIFIED BY 'firefly'; (this creates the user firefly with password firefly) CREATE DATABASE IF NOT EXISTS fireflydb; GRANT ALL PRIVILEGES ON fireflydb.* TO 'firefly' IDENTIFIED BY 'firefly'; quit c. return to unraid gui 3. spin up the firefly-iii container via community applications 4. remove the line 'Host Port 1' as that is not updated with what latest version of container changed 5. go down toward end and 'Add another Path, Port, Variable, Label or Device' a. here in 'Container Port:' put '8080' b. in 'Host Port:' you can put what ever you want, the default was '5080' c. click apply and spin up new container 6. go to <ipofunraid:5080> and finish up creating a user account and oddly requirement of 16 char password. Hope this helps anyone who's trying to get this program running.