ASUSTOR Community Forum

The settings file for NZBGet (admin user) is not being saved to the correct folder.

At app install, and NAS bootup, the settings for NZBGet appear to be being read from the following folder:
However, once changes are made within the NZBGet UI, and "Save All Changes" is selected, the settings are saved to a new file located at:
This then results in the incorrect settings file being loaded on a clean boot of the NAS. If a reload of the UI is performed (i.e from the SYSTEM -> Reload) option, the settings appear to be being read from the file located in the second folder. However if booting clean, and any changes are made, this will replace the one in the app folder with the one from the config folder plus the changes you've made to this point from the default config folder, thus wiping out any extensive changes made up till that point. Will also result in settings regression to defaults upon a NAS reboot, because the (now) incorrect stock config file is being used.

I'm assuming here that there ought to be a symlink in place here pointing from the app folder to the config folder so saved settings are redirected to the "config" folder. This is not occurring for me with this version of the addon.

Tested on: Asustor AS5104T
Firmware: 2.4.2.RIG1
NZBGet Version: 15.0
Addon Version: 20150706

Dan / Gib.

Hi Dan,

The config/nzbget.conf file is linked to nzbget/nzbget.conf on App start. I thought this should have preserved changes in both locations, but as you have pointed out there is a difference between a reload from within NZBGet and an app restart...

Can you please test this version and tell me if this works correctly for you? (note, this actually moves the file from config to nzbget... but then backs up to config again as part of future app updates)
https://www.dropbox.com/s/bn881tv45xdqq ... 12_any.apk

Hello Clinton,

Recently I switched to NZBGet and ran into the same issue as Dan.
I can confirm the custom .APK you provided fixes this issue; all settings remain after a NAS reboot.

Thank you.

Maarten

If Maarten says it's now working, that's good enough for me.

Not had chance to test this yet as I'm working through a clean setup on an addon-by-addon basis, and have not got to this one yet. Efforts also being frustrated by bugs in ADM 2.5.0 which I should of known better than to try out.

I too ran into this issue and have installed the updated APK and it looks to be working with this updated version for me as well!