Sonarr version (exact version): 184.108.40.20670
Mono version (if Sonarr is not running on Windows): 220.127.116.11
OS: DietPI on rpi3b
Debug logs: https://pastebin.com/4HqYKSzH
Description of issue: When I try to add a series using the “Add” or “Add and search for missing episodes”, nothing happens. The button changes to the animation for adding, but stays there. if I reload, it’s like I never added anything. Sonarr is setup exactly the same way as Radarr, but Radarr works fine. I don’t know what’s wrong honestly. Any help is appreciated.
Sonarr version (exact version): 18.104.22.16870
Not seeing any issues on the logs, do trace logs show the API call being received?
Also checking the dev tools of the browser (Network and Console tabs) may show something.
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help http://xhr.spec.whatwg.org/ [jquery.js:9625](webpack:///src/UI/JsLibraries/jquery.js) starting application [main.js:31](webpack:///src/UI/main.js) starting signalR [SignalRBroadcaster.js:9](webpack:///src/UI/Shared/SignalRBroadcaster.js) Loading failed for the <script> with source “http://piwik.sonarr.tv/piwik.js”. [addseries:1:1](http://192.168.2.139:8989/addseries) SignalR: [connecting] [SignalRBroadcaster.js:32](webpack:///src/UI/Shared/SignalRBroadcaster.js) XML Parsing Error: no root element found Location: http://192.168.2.139:8989/signalr/negotiate?apiKey=bc732b4500bf4167bb1795e3c024d360&_=1541358589595 Line Number 1, Column 1: [negotiate:1:1](http://192.168.2.139:8989/signalr/negotiate?apiKey=bc732b4500bf4167bb1795e3c024d360&_=1541358589595) SignalR: [disconnected] [SignalRBroadcaster.js:32](webpack:///src/UI/Shared/SignalRBroadcaster.js)
In the the networks tab, there are two errors:
GET /piwik.js HTTP/1.1 Host: piwik.sonarr.tv User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:63.0) Gecko/20100101 Firefox/63.0 Accept: */* Accept-Language: es-AR,en;q=0.8,es;q=0.5,en-US;q=0.3 Accept-Encoding: gzip, deflate Referer: http://192.168.2.139:8989/addseries DNT: 1 Connection: keep-alive Cookie: __cfduid=d3e3cd864bb2a9776ab0aa44ea00ced7d1540422211 Pragma: no-cache Cache-Control: no-cache HTTP/1.1 404 Not Found Server: nginx/1.10.3 (Ubuntu) Date: Sun, 04 Nov 2018 19:15:30 GMT Content-Type: text/html Transfer-Encoding: chunked Connection: keep-alive Content-Encoding: gzip
Are you using a VPN or proxy?
Looks like Cloudflare is not responding to the request, which can happen if the source IP is blocked it seems (though we’re not setting it to block anything).
No VPN or proxy. I tried a different browser, disabling all add-ons, etc. but no luck…
http://skyhook.sonarr.tv/v1/tvdb/shows/en/121361 load in your browser?
yes, it does. I can see the JSON file/structure.
If you restart Sonarr do you see same thing?
Any issues connecting to indexers?
Looks similar to this
Yes, I tested the connection with all indexers. I am using almost the same ones with Radarr, with different categories, and everything works fine in Radarr. Restarting the service doesn’t fix anything…
Can you run
nslookup skyhook.sonarr.tv from the system running Sonarr and the system you loaded the skyhook URL from?
I’d also be interested in seeing the result if you use Sonarr through a proxy, something like Fiddler or Charles proxy (or any other SOCKS/HTTP proxy), that would help eliminate an issue with mono hitting the skyhook service when cached through Cloudflare.
Hello. This is the return of the nslookup from the rpi:
root@DietPi-rpi:~# nslookup skyhook.sonarr.tv Server: 22.214.171.124 Address: 126.96.36.199#53 Non-authoritative answer: Name: skyhook.sonarr.tv Address: 188.8.131.52 Name: skyhook.sonarr.tv Address: 184.108.40.206
The proxy thing, I’m afraid I don’t know how to do it. I downloaded charles, but that affects only my computer, should I install it on the rpi or if it can capture my browser connections and that is useful also?
Im having the exact same issue.
Sorry, I forgot to respond earlier.
You may be able to proxy Sonarr through Charles, at least that’s my understanding.
We’ve also had a number of issues with mono 5.16, which are similar or the same as this issue. At this point I’d recommend downgrading mono.
If it’s the exact same issue with the same version of mono, downgrade mono. If it’s something else, open a new thread with the requested information.