SABnzbd Forums

Hi,

I just installed sabnzbd on my mac mini (Lion X 10.8.2), but I am not able to configure it. When I go to Folders and enter the paths, I click "Save". Then I go to a different link, and when I click back on Folders, it has the default settings again.

Am I doing something wrong?

(I am a complete Mac newbie - this is my first Mac, got it several days ago...)

Thanks!

OSX10.8.2, Safari, Javascript enabled.

OK, I just manually edited the sabnzbd.ini file with the correct location of the download folder. I restarted sabnzbd and it overwrote the file with the default settings, renaming the manually edited as sabnzbd.ini.bak...

Any help will be highly appreciated.

Thanks.

Trashed and reinstalled SABnzbd - same problem. Very frustrating....

Are you sure the paths you entered are valid?
Especially the "complete" path isn't checked on entry.

Hi Shypike: I drag the folders to the field and it populates the exact path. They *should* be correct.

As a test, I installed SABnzbd on a Windows machine and it's working properly, but on the Mac it's driving me crazy:-)

Thanks.

"Drag folders to the field", huh?
What does the field show exactly?

/Volumes/Drive/Downloads/Usenet/_Incomplete - for Temporary Download Folder
/Volumes/Drive/Downloads/Usenet/ - for Completed Download Folder, etc.

Problem is when I hit Save, it reverts to the default settings. Nothing is saved.

And you're sure that those folders exist and are writeable?
Did you try the "Browse" buttons?
I cannot reproduce your problem at all.
Have you tried a local path instead of an external one?
(So local hard disk and not an attached external drive or network share).
BTW: it's better not to use an external one for "temporary download folder".

I assume SABnzbd is running on the Mac and not some other system?

Hi, the folders do exist, but I'll have to check and see if they are writable. I assumed they were:-)

In any way, is there an error log I can check? Thanks!

Yes: Status page, set to level Debug. Some some stuff and open the log file on the Status page.

Thanks, I'll do that tonight.

Many THANKS! It was a permissions issue, just as you suggested.

All fixed now!

Yeah, our error handling isn't always great.