Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
But ... the history is in the file history1.db (in the hidden sab folder -> admin), which is a sqlite file, which is editable with sqlitebrowser ... as long as SABnzbd is not running.
Safihre: Wrong. I do not find them embarrassing. I use the history log to know what I have acquired but made a few title mistakes that needs to be corrected, that's all. The software should allow the user to correct these errors as required. It is simple and logical.
But ... the history is in the file history1.db (in the hidden sab folder -> admin), which is a sqlite file, which is editable with sqlitebrowser ... as long as SABnzbd is not running.
Sander, thanks for your constructive idea. I know of the history1.db file and tried to edit it with textedit but when I did, SABnzbd wiped out my history log with a bunch of errors. After removing the edits, the History logs came back. At the time SABnzbd was open and perhaps this was why it failed. I will look into sqlitebrowser too.
But ... the history is in the file history1.db (in the hidden sab folder -> admin), which is a sqlite file, which is editable with sqlitebrowser ... as long as SABnzbd is not running.
Sander, used sqlitebrowser, now called "DB Browser for SQLite" and it worked great. Thank you for all your support on this. Hope this helps others with the same issue.