Cannot enable Torznab providers

[renhardy]

I have just installed Mylar in a docker container and I cannot enable the torznab providers. I have tried to manually change the config.ini file to no avail.

Here is the debug log

2020-02-28 20:54:41	DEBUG	ReScheduled job: Auto-Search to 2020-02-29 02:54:41
2020-02-28 20:54:41	WARNING	There are no search providers enabled atm - not performing an Force Check for obvious reasons
2020-02-28 20:54:41	INFO	[SEARCH] Running Search for Wanted.
2020-02-28 20:54:41	INFO	[Auto-Search (trigger: interval[6:00:00], next run at: 2020-02-29 02:30:24 UTC)] Now force submitting job for jobid search
2020-02-28 20:54:39	DEBUG	If you can read this message, debug logging is now working
2020-02-28 20:54:39	INFO	Verbose (DEBUG) logging is enabled
2020-02-28 20:54:26	ERROR	Could not locate exceptions.csv file. Make sure it is in datadir: /config/mylar

Is there any way I can get the torznab providers enabled?

Thanks

[evilhero]

Enabling seems to be working fine here:

How are you trying to enable them ?

In the configuration, if you click on the Providers tab, Torrents, and then Enable Torznab, you'll see an Add Torznab button. Click on that to show the dialog boxes where you need to enter in the relevant information. Once that's done, you have to click on the Save Config option at the very bottom of the page (Clicking on Add Torznab will just open up a blank torznab entry to allow for an additional torznab to be entered).

In case you weren't aware, you also cannot edit the config.ini file when Mylar is running, as the .ini files are loaded into memory on startup / save.

[renhardy]

I can enter a few torznab feeds and test them successfully, but when I click the checkbox to enable that provider and save the changes, I get the "changes saved successfully" message, and right after all the enable checkboxes revert back to empty.

I have tried stopping the container and changing the value from 0 to 1 in the config.ini file, but upon restart the checkboxes remain empty.

[evilhero]

Sorry, didn't realize it was for multiple torznabs. We patched this in the Mylar3 version, but with the code-freeze we didn't update this version. But the fix is now in both development and master branches.

[renhardy]

All right,

Thanks for the quick reply