Signalr problem

Help & Support
#1

The last few releases of the develop branch are having a problem with not updating the UI when searching, etc. Nothing was really showing up in the logs, even with it turned all the way up to “trace”. I turned web debugging on in Firefox and found that the call to /signar/negotiate was returning a 500 error:

It’s fairly easy to duplicate with cUrl:

$ curl -v "http://192.168.242.3:8989/signalr/negotiate?_=1432861240909"
*   Trying 192.168.242.3...
* Connected to 192.168.242.3 (192.168.242.3) port 8989 (#0)
> GET /signalr/negotiate?_=1432861240909 HTTP/1.1
> User-Agent: curl/7.40.0
> Host: 192.168.242.3:8989
> Accept: */*
> 
< HTTP/1.1 500 Internal Server Error
< Server: Mono-HTTPAPI/1.0
< Date: Fri, 29 May 2015 01:12:59 GMT
< Content-Length: 0
< Connection: close
< 
* Closing connection 0

I’m not sure if this is a bug in Sonarr or something I’ve done - I’ve been changing around how I run Sonarr so I could have messed something up but everything else seems fine.

I’m running version 2.0.0.3189 currently but I’ve been seeing this problem for a little while.

Sonar will not import, spins foever
#2

I should have mentioned that I’m using Fedora 22 and using Mono 4.0.1 from https://copr.fedoraproject.org/coprs/tpokorra/mono/

#3

This thread had the same issue on FreeBSD, it might prove helpful in your case: GUI Update Issues

#4

Ah, excellent! Yes, setting XDG_CONFIG_DIR to a path that Sonarr could write to fixed the problem. I guess I broke it when I was redoing the container that I run Sonarr in and I didn’t give the “media” user a writeable home directory. Something in SignalR wants to create a file $XDG_CONFIG_DIR/.mono/keypairs/[1][][-1].xml.

#5