Unable to connect to subsonic server
Closed this issue · 7 comments
I have been using a local copy of Jamstash 3.3 for a long time and it has worked fine. But when I now try and upgrade to the newest version 4.3 I get an error as soon as I save my setting "Unable to connect to Subsonic Server". I can connect to the demo server. My server uses a different port - 4040 - but the demo server has no port specified. Maybe that can be an issue.
I have also tried the Chrome App. I uninstalled it and installe it again. I get the same error in the Chrome app.
I have tried to enable "debug mode" but I cannot see any debug info.
I am running Chrome on Windows 8.1
Same exact issue. Running Ubuntu 14.04 and also replicated in Windows 7. Running latest paid version of Subsonic server and Jamstash 4.3
- Try changing Settings > Protocol
- Hit F12 and look at the Console and Network tab
- Are you using http/https?
Ok, I tested and I can see that I need to use jsonp. It seems to connect to the server but I still see no artists and songs. I get another error when doing so.
scripts.min.4c7ea77d.js:1 Logged In: true
scripts.min.4c7ea77d.js:1 Current Path: /settings
vendor.min.65dc2836.js:5 TypeError: Cannot read property 'status' of undefined
at http://jamstash.com/scripts/scripts.min.4c7ea77d.js:2:17223
at k (http://jamstash.com/scripts/vendor.min.65dc2836.js:5:7014)
at http://jamstash.com/scripts/vendor.min.65dc2836.js:5:7675
at k.$eval (http://jamstash.com/scripts/vendor.min.65dc2836.js:5:12931)
at k.$digest (http://jamstash.com/scripts/vendor.min.65dc2836.js:5:11456)
at k.$apply (http://jamstash.com/scripts/vendor.min.65dc2836.js:5:13250)
at i (http://jamstash.com/scripts/vendor.min.65dc2836.js:4:24010)
at r (http://jamstash.com/scripts/vendor.min.65dc2836.js:4:26418)
at XMLHttpRequest.w.onreadystatechange (http://jamstash.com/scripts/vendor.min.65dc2836.js:4:26994)
Uncaught TypeError: undefined is not a functionscripts.min.4c7ea77d.js:2 (anonymous function)
I've noticed an error in the settings when hitting "save", I think it's related to that.
in main-controller.js
, line 69 :
$scope.ping().then(function(data) {
if (data["subsonic-response"].status == 'ok') {
I think the server responded XML instead of json, causing the error. Haven't digged further but hopefully it's a start
Pushed a few changes to http://beta.jamstash.com that should fix the errors.
thanks! fixed it for me.
Frank
On Mon Jan 05 2015 at 5:28:39 PM tsquillario notifications@github.com
wrote:
Pushed a few changes to http://beta.jamstash.com that should fix the
errors.—
Reply to this email directly or view it on GitHub
#192 (comment)
.
When I try beta.jamstash.com I get "No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://beta.jamstash.com' is therefore not allowed access." when I use both json and jsonp. Should I set som setting somewhere?