Omgwtfnzbs - Can't Connect

Sonarr version (exact version):
Mono version (421):
OS: Win10
Debug logs:
System.Xml.XmlException: The ‘br’ start tag on line 45 position 206 does not match the end tag of ‘center’. Line 45, position 299.
at System.Xml.XmlTextReaderImpl.Throw (System.Exception e) <0x41f08810 + 0x000a3> in :0
at System.Xml.XmlTextReaderImpl.Throw (System.String res, System.String[] args) <0x41f10150 + 0x000ab> in :0
at System.Xml.XmlTextReaderImpl.ThrowTagMismatch (System.Xml.NodeData startTag) <0x41f0b0e0 + 0x00163> in :0
at System.Xml.XmlTextReaderImpl.ParseEndElement () <0x413f3740 + 0x00103> in :0
at System.Xml.XmlTextReaderImpl.ParseElementContent () <0x413ef120 + 0x00297> in :0
at System.Xml.XmlTextReaderImpl.Read () <0x413e99a0 + 0x00057> in :0
at System.Xml.Linq.XContainer.ReadContentFrom (System.Xml.XmlReader r) <0x414a2ad0 + 0x0059f> in :0
at System.Xml.Linq.XContainer.ReadContentFrom (System.Xml.XmlReader r, LoadOptions o) <0x414a1d20 + 0x00057> in :0
at System.Xml.Linq.XDocument.Load (System.Xml.XmlReader reader, LoadOptions options) <0x414a19b0 + 0x0024b> in :0
at System.Xml.Linq.XDocument.Load (System.Xml.XmlReader reader) <0x41d01fa0 + 0x0000f> in :0
at NzbDrone.Core.Indexers.RssParser.LoadXmlDocument (NzbDrone.Core.Indexers.IndexerResponse indexerResponse) <0x41d00f70 + 0x000f7> in :0

Description of issue:
I am unable to connect to omgwtfnzbs. When I perform a test, I receive a cant connect to server message. I checked my account and even generated a new API key, but I am still not able to connect. I don’t see any specific settings in sonarr, so I don’t know where to go from here.

That error “feels” like the indexer is returning html instead of the xml RSS feed. Did you reach a quota, or is there a proxy in between or something?

You can try to enable debug logging, trigger a search. You will see the url that sonarr is calling (without api key). Copy/paste this url in your browser and add the api key again, see what kind of response you get in the browser.

Thanks for the response. I am guessing that the issue was on the other end. Everything seems to be working now.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.