-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding nzb to nzbget not working. #163
Comments
Try the Mirabis branch, it's much more up-to-date: |
Already tried that fork earlier, not any difference for me at least. |
It's not just you, I couldn't get that to work either. |
Could it be related to the Warping issue in v0.55 that affected sending to SABnzbd as well? In #158 I was able to solve the problem in v0.55 by Enabling Warping in the settings. I eventually just downgraded back to v0.53 before those changes were implemented rather than struggle with the warping issue. |
I'll add a plus one to this. Won't work for me either and I have tried several different forks. Using the default credentials, I get this message: 2015-11-06 19:47:53,660 - TERMINAL - INFO - http://nzbget:[email protected]:6789/xmlrpc |
the old version works quite well for me - but the codebase for this is really a mess |
Maybe try downgrading NZBGet and see if that fixes it. If it does, then at least we know the source of the problem. |
I got it to work after talking to the guys on /usenet over at reddit. It only worked if I used the non-ssl port to send to nzbget. The version that worked is nzbget 16.3 and nzbmegasearch ver. 0.47 -- # 2 -- 0byte |
+1 with this issue. Keep getting error with the headers. Maybe one of the forks might solve it ... but it seems most of the people are using sabnzb on those |
Undeadhunter, are you using nzb.su? I could get them all to work but that one. I had to change the set up page from api+manual to just manual. This made dog and omgwtfnb work. |
@staticn0de tried your manual setting, however keep getting the It seems to be an issue with the sending of nzb to nzbget |
I think the problem lays somewhere in the res = self.wrp.beam(pulrlparse) like @oppsig said Bug testing doesn't even allow me to print something after that line, it seems like it can't fill up the res variable. However my knowledge of Python is 0, so I can't even to begin to figure out where it goes wrong. |
Good news. Please find a working version on: I'll make some pull requests to pull it down |
@Undeadhunter will have to check both your pull request and the pending one today ; ) |
@Mirabis Thanks! I didn't clean the code, so might be best to remove the old code? To be fair, pretty much my first time using git ... |
@Undeadhunter somehow the results in sonarr are limited, but manual search works fine ;S |
I noticed it as well with CP, however I didn't touch any of that part of On Wed, Nov 11, 2015, 01:49 Moreno Sint Hill [email protected]
|
when adding nzb to nzbget from nzbmegasearch i get the following error.
"megasearch - INFO - Error connecting server or downloading nzb: 'NoneType' object has no attribute 'headers'"
Seams like a problem with the "tonzbget" method in megasearc.py.
When iIfollow the code "res = self.wrp.beam(pulrlparse)" there is no res.headers!
The text was updated successfully, but these errors were encountered: