search

pymedusa / Medusa

Automatic Video Library Manager for TV Shows. It watches for new episodes of your favorite shows, and when they are posted it does its magic.
https://pymedusa.com
GNU General Public License v3.0
1.8k stars 276 forks source link

Search Settings changes don't stick #3705

Closed snowybunting closed 6 years ago

snowybunting commented 6 years ago

Master branch CentOS 7.3

I make changes in the Search Settings/Torrent Search, changing from "Blackhole" to Transmission, I enter in all the transmission fields, hit the "Test Connection", that is successful. I save the changes, go to another tab, then go back to the Torrent Search, it has reverted back to Blackhole settings.

This is a working Transmission setup for SickRage, the difference is Medusa is on a CentOS box and transmission is on an Ubuntu box on the same local network. SickRage is also on the Ubuntu box, that setup works as expected.

I can pick a show to download, it will send the torrent to transmission and download it, but it won't process it any further - the status on the show page shows it as "Snatched".

Let me know what I can provide to further diagnose this.

medariox commented 6 years ago

Before submitting your issue: Enable debug logging in Medusa settings, reproduce the error (be sure to disable after the bug is fixed)

Please reopen once you have debug logs posted.

snowybunting commented 6 years ago

I wouldn't be posting the entire log, just the relevant parts?

medariox commented 6 years ago

Just the relevant parts.

fernandog commented 6 years ago

Isn't this easy to reproduce?

fernandog commented 6 years ago

I don't think debug logs will point an UI issue. Except error logs. And seems there is no one

medariox commented 6 years ago

I can't reproduce the issue, so I can't do anything without debug logs.

snowybunting commented 6 years ago

I'm not certain what exactly the issue was, but it seems to be connected to Firefox. When I connected to Medusa's webgui thru Chrome, the issue was not there. I tried a couple of different browsers late last night, the only problem was on my default Firefox browser. I'll try to flesh it out later, but it seems to have something to do with the security settings in Firefox.

There was no sign of this in the logs.

fernandog commented 6 years ago

@snowybunting open developer tab in FF and check if there is any error there