About a week ago I switched from Sickrage to Sonarr for the better interface and features. Downloading shows seems to go perfectly fine, but the thing is that i can’t access to Sonarr interface anymore. When I try to open the web interface almost nothings happens. My browser starts loading a webpage but then simply stops. Sometimes I get to the loading screen with the moving circles, but it just doesn’t go any further.
When I was setting up Sonarr I had no problem with loading the interface, the problem only came the day after everything was set up. I already tried rebooting the NAS that I am running Sonarr on and stopping/starting the package but nothing seems to make any difference. I checked the log but didn’t see any strange requests there either, just the searching/finding of shows.
Does anyone recognizes this problem and maybe knows a solution? I would really hate to have to switch back to Sickrage.
Any errors in the log files?
Are you accessing it via the correct port, the logs will show the port on startup as well as the config file (up on directory from the logs).
Yes I am sure that I am using the correct port, I use the default port (8989).
I checked the logfile (/usr/local/nzbdrone/var/.config/NzbDrone/logs/nzbdrone.txt) but that file only shows information about show updates and things like that. Is there maybe an other log file that I should look into?
I exited Sonarr, removed the log and then started Sonarr again. The log file is showing this:
16-1-27 23:05:29.0|Info|OwinHostController|Listening on the following URLs:
16-1-27 23:05:29.0|Info|OwinHostController| http://*:8989/
16-1-27 23:05:30.9|Debug|OwinAppFactory|Attaching NzbDroneVersionMiddleWare to host
16-1-27 23:05:30.9|Debug|OwinAppFactory|Attaching SignalRMiddleWare to host
16-1-27 23:05:31.1|Debug|OwinAppFactory|Attaching NancyMiddleWare to host
16-1-27 23:05:32.1|Info|NancyBootstrapper|Starting NzbDrone API
16-1-27 23:05:42.0|Trace|EventAggregator|Publishing ApplicationStartedEvent
16-1-27 23:05:59.8|Trace|EventAggregator|ApplicationStartedEvent -> UserService
16-1-27 23:06:00.3|Trace|EventAggregator|ApplicationStartedEvent <- UserService
16-1-27 23:06:00.3|Trace|EventAggregator|ApplicationStartedEvent -> DownloadClientFactory
16-1-27 23:06:00.3|Debug|DownloadClientFactory|Initializing Providers. Count 9
16-1-27 23:06:03.4|Trace|EventAggregator|ApplicationStartedEvent <- DownloadClientFactory
16-1-27 23:06:03.4|Trace|EventAggregator|ApplicationStartedEvent -> IndexerFactory
16-1-27 23:06:03.4|Debug|IndexerFactory|Initializing Providers. Count 14
16-1-27 23:06:03.7|Trace|EventAggregator|ApplicationStartedEvent <- IndexerFactory
16-1-27 23:06:03.7|Trace|EventAggregator|ApplicationStartedEvent -> ReconfigureLogging
16-1-27 23:06:43.6|Info|SceneMappingService|Updating Scene mappings
16-1-27 23:06:47.6|Info|HousekeepingService|Running housecleaning tasks
16-1-27 23:06:51.2|Info|Database|Vacuuming Log database
16-1-27 23:06:52.0|Info|Database|Log database compressed
16-1-27 23:07:00.2|Info|Database|Vacuuming Main database
16-1-27 23:07:03.8|Info|Database|Main database compressed
16-1-27 23:07:52.7|Info|RssSyncService|Starting RSS Sync
16-1-27 23:09:54.5|Warn|KickassTorrents|KickassTorrents server is currently unavailable. https://kat.cr/tv/1/?rss=1&field=time_add&sorder=desc The request timed out
16-1-27 23:09:56.3|Info|DownloadDecisionMaker|Processing 100 releases
16-1-27 23:10:31.4|Info|RssSyncService|RSS Sync Completed. Reports found: 100, Reports grabbed: 0
16-1-27 23:06:03.4|Trace|EventAggregator|ApplicationStartedEvent -> IndexerFactory
16-1-27 23:06:03.4|Debug|IndexerFactory|Initializing Providers. Count 14
16-1-27 23:06:03.7|Trace|EventAggregator|ApplicationStartedEvent <- IndexerFactory
16-1-27 23:06:03.7|Trace|EventAggregator|ApplicationStartedEvent -> ReconfigureLogging
16-1-27 23:06:43.6|Info|SceneMappingService|Updating Scene mappings
16-1-27 23:06:47.6|Info|HousekeepingService|Running housecleaning tasks
16-1-27 23:06:51.2|Info|Database|Vacuuming Log database
16-1-27 23:06:52.0|Info|Database|Log database compressed
16-1-27 23:07:00.2|Info|Database|Vacuuming Main database
16-1-27 23:07:03.8|Info|Database|Main database compressed
16-1-27 23:07:52.7|Info|RssSyncService|Starting RSS Sync
16-1-27 23:09:54.5|Warn|KickassTorrents|KickassTorrents server is currently unavailable. https://kat.cr/tv/1/?rss=1&field=time_add&sorder=desc The req
16-1-27 23:09:56.3|Info|DownloadDecisionMaker|Processing 100 releases
16-1-27 23:10:31.4|Info|RssSyncService|RSS Sync Completed. Reports found: 100, Reports grabbed: 0
After trying to acces Sonarr the last few days with no result, it suddenly worked a few minutes ago. I did not change anything and the strange thing is that I can access Sonarr now with Firefox, but I can’t get it to load with Chrome or Safari (I am using a Mac). As Safari is my primary browser I would prefer to use it for Sonarr as well, I think that shouldn’t be a problem because is has worked before…
Try clearing the browser cache, something might be stale in there thats causing issues. Checking the developer tools in your browser would likely show an issue in the console as well, if you want to check that before clearing the cache.
Sorry for the late reply, the notifications for this topic accidentally ended up in my spam folder.
markus101: I tried clearing the cache but it did not have any effect. I do see the developer tools with the error console in my browser but it is greyed out. I think because the browser isn’t getting any response at all from Sonarr.
meffect: I am using a Synology DS112j NAS.
I could access Sonarr a few times through Firefox, but at the moment it is giving the exact same result as in Safari and Chrome: nothing is happening. I am not even getting the ‘loading dots’ anymore.
According to the services Sonarr was still running but it wasn’t responding to anything anymore. I tried restarting Sonarr but that didn’t work, so I rebooted the NAS itself. I can get in the Sonarr interface again with Firefox but still not with Safari or Chrome, it gets stuck at the ‘loading dots’. The Safari developers menu error console gives the following errors:
[Error] Failed to load resource: Time-out of the request. (ui, line 0)
[Error] TimeoutError: DOM Exception 23: A timeout occurred.
(anonieme functie)
fire
add
get
(anonieme functie) webpack_require
(anonieme functie) webpack_require
(anonieme functie) webpack_require
(anonieme functie) webpack_require
(anonieme functie) webpack_require
(anonieme functie) webpack_require
(anonieme functie)
(anonieme functie)
[Error] Failed to load resource: Time-out of the request (status, line 0)
[Error] TimeoutError: DOM Exception 23: A timeout occurred.
(anonieme functie)
fire
add
get
(anonieme functie) webpack_require
(anonieme functie) webpack_require
(anonieme functie) webpack_require
webpackJsonpCallback
(anonieme functie)
Chrome Dev Tools wasn’t showing anything, I think because the page wasn’t loading at all. I think because Sonarr wasn’t giving any response anymore, just like a few days ago. Rebooting the NAS got in Sonarr again but episode pages weren’t loading.
I switched back to SickRage for now. Maybe I will give Sonarr a try again in the feature. Thanks for your help anyway!
Same issue. In chrome dev tools it says:
jquery.js:9625 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check https://xhr.spec.whatwg.org/. jquery.js:9625