[robweber]

I cannot get the Dropbox backup to work. I have the DBX app created (have my key/secret in place and configured in the addon) but once the following message appears...

... I simply cannot find the appropriate log. As the the documentation says:

"(...) When you see the prompt regarding the Dropbox URL Authorization DO NOT click OK. Check your Kodi log file for a line from "script.xbmcbackup" containing the authorization URL. (...)"

I immediately ssh into my machine but it seems like that there is no log created (or I was not able to find it). Do I need to activate systemwide logging manually beforehand? Or is the log meant to be created in the addon folder?

OpenELEC:~/.kodi/addons/script.xbmcbackup # ls -all
total 84
drwxr-xr-x 3 root root 4096 Jan 3 22:45 .
drwxr-xr-x 46 root root 4096 Jan 3 22:45 ..
-rw-r--r-- 1 root root 1069 Jan 3 22:45 LICENSE.txt
-rw-r--r-- 1 root root 9252 Jan 3 22:45 README.txt
-rw-r--r-- 1 root root 20620 Jan 3 22:45 addon.xml
-rw-r--r-- 1 root root 5053 Jan 3 22:45 changelog.txt
-rw-r--r-- 1 root root 2357 Jan 3 22:45 default.py
-rw-r--r-- 1 root root 9152 Jan 3 22:45 icon.png
drwxr-xr-x 4 root root 4096 Jan 4 14:27 resources
-rw-r--r-- 1 root root 5586 Jan 3 22:45 scheduler.py

Can somebody tell me where that logfile is created (or which log is meant exactly) to pick up that auth url?

Many thanks for this great addon!

The URL is in the main xbmc log file. Looks like you are using OpenElec so something like /storage/.kodi/temp/xbmc.log.

Running Backup v1.0.1 on my Amazon Fire TV (Android) "Kodi 14.0 Helix" install. I cannot get to function after configuring. I receive a "Error: Script Failed! Backup" message when trying to run a backup job.

Once I disable the setting to "compress", I get the script to appear to function, but am warned that the write destination to my SMB share is detected ("Write Error Detected"). I proceed, the Add-On runs like it's backing up, I go onto my Windows box and see that the backup directories were created, but all folders are empty.

Please include a debug log. This is most likely due to a file write issue on the network share but the debug log would confirm.