PDA

View Full Version : Logitech squeezebox controller app (and possible other apps) not functioning



servies
2013-03-29, 06:26
As my server is connected to the internet (so that I can stream to my workplace) I set a user and password to access squeezeserver.
This resulted in the Logitech squeezebox controller app no longer being able to find my SB Touch.
It appears to still be able to connect to the server but for the rest no result...
Is this a known problem and do the other apps have the same problem? I'm reluctant to buy another 3rd party app to find out afterwards it also isn't able to manage my Touch...

pippin
2013-03-29, 06:29
If its able to connect to the server and browse the library then the problem is probably between the touch and the server and not related to the App. Did you enter the credentials on the Touch, too?

Try to reboot the touch and reconnect to the server.

There are a few Apps out there that don't support authentication but all the major ones support it, including Logitech's although for me Logitech's App sometimes doesn't show artwork with authenticating servers.
But whenever there is a problem with this it will be mainly upon connection, there will not be issues with the players due to App issues with authentication.

servies
2013-03-30, 14:34
Thanks for the answer, I'll try to reconnect the Touch.
Currently I let Apache handle the authentication, but I'll try this tomorrow...

pippin
2013-03-30, 23:01
That will probably not work. Does Aoache handle authentication on all ports? I believe port 3483 (for the streaming) never authenticates and I'm not sure about SlimProto over 9000 (certainly not via http authentication) so Apache might block your Touch's access to the server.

I believe most Apps will actually work although I never tried it so can't be sure. I'd be confident for iPeng because it uses the iOS authentication support even for the cometd connections so all forms of http auth should be covered. No idea how others handle this, some might just manually add a header.

servies
2013-04-02, 05:34
That will probably not work. Does Aoache handle authentication on all ports? I believe port 3483 (for the streaming) never authenticates and I'm not sure about SlimProto over 9000 (certainly not via http authentication) so Apache might block your Touch's access to the server.

I believe most Apps will actually work although I never tried it so can't be sure. I'd be confident for iPeng because it uses the iOS authentication support even for the cometd connections so all forms of http auth should be covered. No idea how others handle this, some might just manually add a header.
I know, my reply was a bit incomplete... I'm wasn't blocking the ports, but I was blocking the (proxied) webinterface by Apache (Now I don't need to remember the exact portnumber, just an url...) The real ports are indeed still open to the world...

pippin
2013-04-02, 06:10
But doesn't Apache then block the whole port? Usually LMS will use port 9000 for the bulk of it's communication: web interface, slimproto and cometd. If that's what Apache gets in the way of then the Squeezebox will have no control interface unless it can handle Apache's authentication.

servies
2013-04-03, 06:39
But doesn't Apache then block the whole port? Usually LMS will use port 9000 for the bulk of it's communication: web interface, slimproto and cometd. If that's what Apache gets in the way of then the Squeezebox will have no control interface unless it can handle Apache's authentication.
Nope, I'm just doing the authentication for the apache url. The original ports are still unauthenticated.
Normally with portforwarding you have to enter something like http://mydomain.com:9000 to get to the squeezeboxserver pages. When you set up Apache to create a proxy to port 9000 you can acces it like http://sbserver.mydomain.com or whatever you want (ofcourse you need a working domain etc...).
Apache authentication is at the proxylevel, not on the squeezeboxserver pages, so it's as insecure as it already was, only the very convenient url is secured...

pippin
2013-04-03, 09:26
Ok, then I'd say your problem is unrelated to the authentication....