-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spotify - no connect possible #141
Comments
Please check your server.log file (Settings/Information) for hints about the failure. |
i just see endless entries to start the helper app
Running this command on command line produce an error because of the brackets. Don't know if the real call of the command use -n "Spotify Anmeldung (fs)" instead. |
Running the command with strace i got following output ...
|
What if you run the command with quotes where they need to be? Or simplify the name (you can put anything there, just a single word is simplest)? |
i used the command with quotes of course, i also used just the word spotty instead, as mentioned in the help as default value. There is also no difference. The command does not raise anything on the network. No DNS request, no connect to any IP. i have seen two lines which may be related to the issue ...
|
I used the plugin since years, but with the issues the last days i installed 4.11.9 and moved back to 4.11.2 later on. But the spotty binary does not start anymore. I removed the plugin, the prefs and cache and tried it again. I just arrive at the plugin config page and nothing happens. There was an issue with SSL.pm, which is solved in the meanwhile.
My understanding was the plugin need the client ID somehow before it initiate the connect?
The text was updated successfully, but these errors were encountered: