PDA

View Full Version : "You are not authorized"=Sirius & "You are logged in in another location"=Slacker



mkanet
2009-11-10, 20:36
In the past, I've just been shrugging it off when I sometimes get the "you are not authorized to listen" message for Sirius or "You are logged in another location" for Slacker. I just select the station again and push play again and it works the next time. However, they're starting to get pretty annoying. I'm hoping to prevent unnecessary error messages if possible.

Are these two errors related? Are they known issues? When doing searches, I do find references to these messages, but didnt find a solution.

When I get these messages, my other clients arent even on. I have never given my account information to anyone else before. Is there a way to prevent these bogus errors from showing?

I've seen this ever since server version 7.0. I still see it in 7.4.

andyg
2009-11-11, 10:03
Both of these errors occur when the backend Sirius/Slacker servers tell us your account is being used somewhere else and that we need to stop streaming to you. Unfortunately it's hard to track down the source of this problem if you really aren't using your account on another PC or device.

toby10
2009-11-11, 10:23
You can try logging your computer onto those accounts, then make sure you click on "log off" before you exit their web page.
Might be that your computer is still logged into the providers online account (or those services think your computer is logged in).
Worth a shot to check.

Also try doing the same with your MySB.com account, completely log off your computer from any MySB login. Then try to access those services from the hardware player.
I know for a while some providers considered your computer logged into MySB and the hardware player as two distinct login's and would not function.
This may have been corrected since then and may no longer apply.

mkanet
2009-11-11, 10:26
Thanks for the quick reply Andy. Does this mean that there's actually someone trying to use my account logins? It seems more plausible that connections arent handled correctly from the source all the way to the client playing back the audio verses someone outside my home logging in using my accounts. My slacker account is free.

If there isnt actually someone logging in my with accounts somewhere else, is the problem with my clients? Are there instances where this happens on certain clients verses others under certain circumstances? I would like to at least know where to start looking.

Thanks again for any help you can offer Andy.

mkanet
2009-11-11, 10:28
I dont login anywhere else. I only use my squeezebox clients.


You can try logging your computer onto those accounts, then make sure you click on "log off" before you exit their web page.
Might be that your computer is still logged into the providers online account (or those services think your computer is logged in).
Worth a shot to check.

Also try doing the same with your MySB.com account, completely log off your computer from any MySB login. Then try to access those services from the hardware player.
I know for a while some providers considered your computer logged into MySB and the hardware player as two distinct login's and would not function.
This may have been corrected since then and may no longer apply.

cornflakeguy
2009-11-13, 07:13
Same here and I've been getting that scrolling across the top of my Radio since day 1.

mkanet
2009-11-13, 09:22
I am curious how we go about fixing this problem. It's obviously reproducible; and, not an isolated incident.

qtech
2010-02-05, 10:55
Hello,

I have signed up for Sirius/XM online couple of days ago to get my SbRadio online. I setup the Sirius/XM via phone and got online to verify my access was correct. Everything was setup correctly. I logout online Sirius/XM account. Went into SBS and setup for Sirius/XM plugins and account access.

I factory default my SbRadio and setup for SBS and connected. I menu to Sirius Radio and play favorite stations. It play for hour and then music stopped "You are not authorized". This was confusing as I know my account was setup correctly.

I even reboote my computer to make sure it flush all logins and account access reset. Still after couple of hour playing Sirius, same thing "Your are not authorized".

How can I get rid of the connection authentication issue?


Much appreciate any help.

mkanet
2010-02-05, 11:20
There seems to be a couple of different issues related to this. The first issue can be resolved by defining more than one account for each music service on mysqueezebox.com (for example, I now have two Internet user accounts for sirius/xm radio (which I pay extra for). I also have two users accounts defined for the other subscription based music services on mysqueezebox.com. This at least protects this issue from happening every 5-10 minutes.

However,

There is another related issue with the mysqueezebox.com backend in respect to problem; whether the developers want to admit it or not. I'm using a completely different setup than you (using good old faithful softsqueeze.jar clients. This issue seems to happen even in cases where there are only one player. However, any little hickcup; such as a pause in the audio stream; caused by another possibly unrelated TCP/IP connection with a greater QOS precedence (disrupting the currently playing autio stream, is enough to trigger this error message when trying to recover from it and playback from the same subscription based music provider.

Unfortunately, no matter how many people complain about this or post bug reports; dont seem to get a definitive fix for this. I'm guessing most of the developers are either dialed into the logitech network via VPN or physically close to their mysqueezebox.com server(s) which would reduce the likelyhood of the audio stream getting disrupted.

I guess if I had a dedicated point-point circuit to the mysqueezebox.com server or on the same LAN, I wouldn't have this issue unless mysqueezebox.com server is bogged down with too many user requests being proxied from the music provider source.

There are probably settings in Squeezebox server which can increase the streaming buffer; but, could possibly cause other adverse side effects. I only have the default 3 second buffer under audio settings using LAME at full quality and no transcoding (original bitrate from music provider). I also have a high quality sustainable 62mbps downstream Internet connection; which is definitely not the issue.

We are at the mercy of a developer kind enough to investigate this issue. I dont want to open up multiple duplicate bug reports. They will either fix this issue or not. I never had this issue before Logitech came into the scene and the backend was changed.

-MKA


Hello,

I have signed up for Sirius/XM online couple of days ago to get my SbRadio online. I setup the Sirius/XM via phone and got online to verify my access was correct. Everything was setup correctly. I logout online Sirius/XM account. Went into SBS and setup for Sirius/XM plugins and account access.

I factory default my SbRadio and setup for SBS and connected. I menu to Sirius Radio and play favorite stations. It play for hour and then music stopped "You are not authorized". This was confusing as I know my account was setup correctly.

I even reboote my computer to make sure it flush all logins and account access reset. Still after couple of hour playing Sirius, same thing "Your are not authorized".

How can I get rid of the connection authentication issue?


Much appreciate any help.

mkanet
2010-02-05, 17:27
It happened again. I tried using direct stream instead of proxied audio stream... however, I got the same result. I am certain I dont have any players using this same slacker account. It's pretty straight forward to setup. Whatever it is, there needs an adjustment to the backend which handles Internet subscrption based services. I never EVER see this happen to my radio stations which go directly to the source instead of depending on the clunky logitech subscriber proxies. One way to fix it is to revert back to what you guys had back before Logitech got a hold of your backend services; although, there were less services that were supported. This issue never happened using Squeezecenter 7.2.1 and whatever the backend was at the time.

http://i67.photobucket.com/albums/h283/mkanet/Slacker.jpg

qtech
2010-02-05, 17:50
Thanks for the information...it was helpful to understand the systemic issues that has been reported. Since I am running the SBS and SBRadio on a corp network, I could have QOS enable and manage the traffic. How do I go about looking for network specs/requirement that I can provide to our corp NT engineers.

The ports for traffic to allow firewall permission:
•Port number: 3483 (TCP) - Name: SlimServer Control
•Port number: 3483 (UDP) - Name: SlimDiscovery
•Port Number: 9000 (TCP) - Name: SlimServer Web

I like to test in our corporate environment.

Thanks for the help.

qtech
2010-02-05, 19:09
An update on using XM Online plugins vs. Sirius plugins. I have loaded this afternoon using XM Radio Online (v3.5.1) by Neil. It's been solid so far 6 hrs.

mkanet
2010-02-05, 19:10
I dont want to burst your bubble... I'm one of our firewall engineers for a US Federal Agency I cant disclose.... and, allowing those access-lists will not help the this issue. I have a strong suspicion this issue is related to some sort of ghost/duplicate account mishandled by mysqueezebox.com... in certain cases when there's obviously only one client at your home playing a single stream.

This might be related to timing/time-outs when switching radio stations/songs; and, mysqueezebox.com NOT telling the music provider that the audio stream has stopped. The music service is tolerant for a short while under the same account to play two different radio stations for a ew minutes or so (length of the song), but eventually, it will stop your current stream.


Thanks for the information...it was helpful to understand the systemic issues that has been reported. Since I am running the SBS and SBRadio on a corp network, I could have QOS enable and manage the traffic. How do I go about looking for network specs/requirement that I can provide to our corp NT engineers.

The ports for traffic to allow firewall permission:
•Port number: 3483 (TCP) - Name: SlimServer Control
•Port number: 3483 (UDP) - Name: SlimDiscovery
•Port Number: 9000 (TCP) - Name: SlimServer Web

I like to test in our corporate environment.

Thanks for the help.

mkanet
2010-02-05, 19:11
This is an issue with slacker as well. (Read above theory)....


An update on using XM Online plugins vs. Sirius plugins. I have loaded this afternoon using XM Radio Online (v3.5.1) by Neil. It's been solid so far 6 hrs.

JJZolx
2010-02-05, 21:44
I gave up on Slacker a long time ago due to this issue.

mkanet
2010-02-05, 22:10
It's actually not slackers fault. Nor Sirius radio which has a very similar message. It's the people who maintain the code for mysqueezebox.com. They screwed up sometime a little after Logitech took over. I've been tring to get his to andy's attention; however, it's not something simple he can just revert to quickly. A lot of changes were made since the time it was working correctly; such as adding more services.

There's really no way around this; even if you have multiple legitamate accounts; which tried. The problem is with the same account, same player... mysqueezebox.com seems to somehow leave some kind of lingering ghost audio stream behind after a song change... making the music service provider like sirius/slacker to think there are two songsbeing played at the same time on the same machine. The sad thing is I dont think this is something I can control even on my firewall by killing the older duplicate audio stream since I think the issue is at the logitech backend and they way it provisions audio streams for each music service.

Ohhhhh Andy... feel like fixing this once in for all instead of passing it on to another backend server engineer by asking for a bugzilla report? I'm sure there's at least been a couple of reported already.

*RANT MODE ON*
I really wish Logitech/mysqueezebox.com would just get out of the way and allow direct connections between our squeezebox servers and the music providers. This would also prevent those down times when mysqueezebox.com isnt down for maintenance; also, reducing lag. I can name several reasons actually.

*RANT MODE OFF*



I gave up on Slacker a long time ago due to this issue.

JJZolx
2010-02-05, 22:26
It's actually not slackers fault.

I suspect it's mysb.com as well, but that really doesn't matter. It's just not worth the bother.

mkanet
2010-02-06, 09:07
Yeah, but this is something Logitech mysqueezebox.com engineers do need to bother with. That's one of their primary responsibilities.

Eventually instead of having squeezebox users give up using mysqueezebox dependant services, it would be a good idea to at least look into what could cause this issue; or, at least let people know this issue is currently being investigated with some encouraging fixes.


I suspect it's mysb.com as well, but that really doesn't matter. It's just not worth the bother.

mkanet
2010-02-07, 00:42
I have tried everything in my power to help eliminate these error messages with various setting changes in squeezebox server such as:

-Power On Resume: Stop at power off/Reset playlist at power on
-Changing the player's Audio MP3 Streaming Method to Direct Streaming
-Disable UPnP Client
-Server priority= -6 Above Normal

I have also added multiple fully registered accounts to Slacker and Sirius Radio (I had to pay more for these extra accounts) and added these secondary accounts to separate Squeezebox clients.

I'm not sure which of these helped or not, but the frequency of getting these error messages (mentioned in the thread title) are less frequent.

I can't pinpoint what is left to eliminate these errors once in for all; however, I am hoping that Andy could please offer any suggestions that could prevent these errors.

I still think it would be a good idea for Andy to take a closer look at the way clients start/stop audio streams; and, see if there's a provision that could be made on mysqueeebox.com to flush old audio streams (even if the audio stream is already stopped on the client). As long as the music service provider doesn't continuing to receive a "ghost"/stray audio stream caused by a squeezebox/client audio stream anomaly via forgotten/lost-track-of TCP sockets, we should be fine.

All I'm hoping for Andy (I know its a PITA), but having an extra provision to cleanly stop any previous audio streams under a user account for respective music service (that's not heard on the client), it would be greatly appreciated by not only the end user; but, also by the Internet service provider as well. This would also help reduce issues on mysqueezebox with audio stream leaks which can prevent having to restart the mysqueezebox.com backend (possibly caused by audio stream leaks such as this).

Of course, the above paragraph is all pure speculation. Not knowing the technical reasons behind having a backend mysquezebox.com "proxy", in general it makes sense to move over these functionalities to the user's personal mysqueezebox server... where the user can manually enter their username/passwords for each music service. This would reduce lag time, less dependancies, less money/time/resources to maintain mysqueezebox.com; and just offer an auto-updater for squeezebox.com server for critical changes. Bottom line, this would also reduce the likelihood of unaccounted for audio streams going into the mysqueezebox.com abyss due to Internet connection hiccups, timeouts, etc since there's an extra component that's in between the user's squeezebox server and each music service provider.

Anyway, please.. in the short term goal at least add a provision to use a more aggressive method to cut off any previous "ghost"/remnant audio connections to the respective music service (caused by TCP/IP connection "hiccups" which may not be recovered correctly) before starting a new song/station from the same service provider.

Thanks for your time to help improve the reliability of your service.

Sincerely,
Michael
Anonymous Senior Network Engineer from a Federal Government Agency

toby10
2010-02-07, 04:27
mkanet,

I don't use Sirius, but I do use Slacker quite often. The only time I get such Slacker "duplicate login" errors is when I actually do have a duplicate login (computer on Slacker UI or another player).

A long time ago there was an issue with the SqueezeNetwork UI (this is now MySqueezeBox.com) where Slacker would see your computer logged into SqueezeNetwork and your player(s) as "duplicate logins".
That issue was corrected, but I wonder if the issue is back for some network setup configurations?

As a *very* long shot, try logging off any instances of MySqueezeBox.com UI logins.
Other than making double sure you have no current logins (MySB or Slacker) and no other players accessing Slacker, I wouldn't know what else to suggest. :(

mkanet
2010-02-07, 14:57
Toby, thank you so much for replying and trying to help. I'm a network engineer for over 18 years; and understand some things are very hard to prove without a very good logging system on the backend/protocol analyzer (on the mysqueezebox.com side).

I definitely got rid of all other instances of slacker. The key thing to realize is it's not related to just one mysqueezebox.com dependant service. Also, the services I use (Slacker and Sirius) worked great a while back before your backend was changed; hence, looking at the mysqueezebox.com component as a factor. I have seen this issue happen a little after Logitech bought this technology; and, changes started happening after SqueezeCenter 7.2.1 to the backend. Let's face it, there aren't a whole lot of options to work with on my local Squeezebox server; and, I only have two squeezebox clients. Whatever it is, I use two separate accounts on the mysqueezebox.com side for each music service... and MOST IMPORTANTLY... this doesnt happen to simple music stations that use mp3 playlists (which my clients contact directly to; instead of getting mysqueezebox.com in the mix.

Whatever the problem is, it wasn't a problem when we used the older backend along with squeezecenter 7.2.1 (which isnt that long ago). Whoever works on the back end should probably have a clue what changed during that period along with the hints I posted. I sure as heck hope, the engineers dont just sweep this issue under the rug hoping people will stop complaining about it. It doesnt happen to many people, but there are certain configurations which trigger this and cause mysqueezebox.com to muff things up.



mkanet,
...
As a *very* long shot, try logging off any instances of MySqueezeBox.com UI logins.
Other than making double sure you have no current logins (MySB or Slacker) and no other players accessing Slacker, I wouldn't know what else to suggest. :(

mkanet
2010-02-15, 16:58
Andy, I hope you dont mind that I share with others having this issue that you're completely aware of this issue and actively working on it.

Here's the update guys:
According to Andy, this doesnt appear to be an issue with our hardware/software; you could have a perfectly legitimate configuration and setup; but still have this problem. He said, "could be an obscure bug, I'll have to go through the code and see"

I did think it was kind of unusual that he didnt need any form of debug information when the error occurs. I think he's definitely on the right track... he knows that this happens in Sirius and Slacker only; since we have to depend on mysqueezebox.com clustered servers to reach sirius.com a slacker.com.

In a perfect world, the squeezebox software would just access the music sevices directly to avoid "network outages" and issues like this, less lag time, etc. It doesnt make sense to depend on an extra "proxy" to get to the music service. This appears to be a licensing/legal-type issue. However, if that's the only way it can be done, then I'm grateful we at least have this ability. It would be even better once it works correctly for us.

Knowing Andy's past encounters in fixing obscure bugs like a cyborg, I wouldn't be surprised if he figures it out relatively soon; afterall, he knows the "code" better than anyone I've see here.

Good luck Andy and please keep us posted!

-Michael


Both of these errors occur when the backend Sirius/Slacker servers tell us your account is being used somewhere else and that we need to stop streaming to you. Unfortunately it's hard to track down the source of this problem if you really aren't using your account on another PC or device.

mkanet
2010-02-20, 15:48
Hey Andy, any news on this? It sure would be nice to get this "kink" worked out. I am willing to give you any log files, reproduce it whenever you need me to...


http://i67.photobucket.com/albums/h283/mkanet/Screenshot-1052.jpg

http://i67.photobucket.com/albums/h283/mkanet/Screenshot-1053.jpg

toby10
2010-02-20, 16:21
Oddly I just ran into this today on Slacker. It said I was logged on another device and I am absolutely certain I was not.
Pressing Play again corrected this and started the stream. I presume this "kicked" the mysterious rogue device.

Very strange and has never happened before unless I was indeed logged in on another device.

mkanet
2010-02-20, 16:35
Toby, Andy definitely knows about this issue. He even knows its related just to slacker and sirius and his side of things. I just quietly knudged him a few moments ago to take a look at it again. According to him its nothing we're doing wrong; and, suggested this issue isn't an easy one to track down. The good news is Andy has never dropped the ball (that I know of) on any issue before. BTW. I rolled all the way back cleanly to squeezecenter 7.2.1 (which never gave me any issues at all), but still saw the issue happen.. maybe just a little less frequently.


Oddly I just ran into this today on Slacker. It said I was logged on another device and I am absolutely certain I was not.
Pressing Play again corrected this and started the stream. I presume this "kicked" the mysterious rogue device.

Very strange and has never happened before unless I was indeed logged in on another device.

toby10
2010-02-21, 06:06
Toby, Andy definitely knows about this issue. He even knows its related just to slacker and sirius and his side of things. I just quietly knudged him a few moments ago to take a look at it again. According to him its nothing we're doing wrong; and, suggested this issue isn't an easy one to track down. The good news is Andy has never dropped the ball (that I know of) on any issue before. BTW. I rolled all the way back cleanly to squeezecenter 7.2.1 (which never gave me any issues at all), but still saw the issue happen.. maybe just a little less frequently.

Andy is a pitbull when he tackles a problem. ;)

I'm on beta 7.5 so going forward won't help you either. :(

I've never seen the "no longer authorized" one, just the duplicate login issue.
Have you been able to clear all of the duplicate login errors by simply pressing Play?
Mine happened on my Boom so I don't know if this can be so easily cleared with the newer players Radio & Touch.

mkanet
2010-02-21, 15:06
Yeah, I just push play, and it continues... it doesnt really seem to be client-related. Mine happens regularly on my softsqueeze based clients; which are more sensitive to this issue. Things were pretty stable until some of the newer players came out; which, Im not in the market for.


Andy is a pitbull when he tackles a problem. ;)

I'm on beta 7.5 so going forward won't help you either. :(

I've never seen the "no longer authorized" one, just the duplicate login issue.
Have you been able to clear all of the duplicate login errors by simply pressing Play?
Mine happened on my Boom so I don't know if this can be so easily cleared with the newer players Radio & Touch.

tebrown
2010-05-07, 16:17
I had squeezebox server running on an old, old Mac for a couple months (SBS 7.4.x and 7.5) and never/rarely saw the "not authorized" message when using Sirius. I switched over to a new computer running Ubuntu 10.04 (SBS 7.5) and it is happening with annoying frequency now. I know the client side isn't supposed to be the root cause, but perhaps there is something else going on that the clients are doing that is a catalyst for this? I can tolerate this, but my wife will soon divorce me :)

frankef
2010-05-11, 19:23
I also have the "no longer authorized" problem on Sirius, but with a slight twist. I have no problem listening to Sirius via mysqueezebox.com (on a Duet) but if I link the Duet to my local Squeezebox Server, or try to listen from the PC using Squeezeslave or any other software player, the stream always stops after ~50 sec. with the "no longer authorized" message.

I am, of course, able to use the Sirius embedded player in IE (doesn't work in Firefox), but I don't see a way to log off of that player, as someone on this thread has suggested might help.

Hope Andy gets to the bottom of this soon!

Frank

frankef
2010-05-11, 19:23
I also have the "no longer authorized" problem on Sirius, but with a
slight twist. I have no problem listening to Sirius via
mysqueezebox.com (on a Duet) but if I link the Duet to my local
Squeezebox Server, or try to listen from the PC using Squeezeslave or
any other software player, the stream always stops after ~50 sec. with
the "no longer authorized" message.

I am, of course, able to use the Sirius embedded player in IE (doesn't
work in Firefox), but I don't see a way to log off of that player, as
someone on this thread has suggested might help.

Hope Andy gets to the bottom of this soon!

Frank


--
frankef
------------------------------------------------------------------------
frankef's Profile: http://forums.slimdevices.com/member.php?userid=21909
View this thread: http://forums.slimdevices.com/showthread.php?t=71255

flemming
2010-05-12, 07:22
Disable the official Sirius plugin and try using the one I wrote instead.

http://notsosirius-squeezecenter.googlecode.com/

Robert

frankef
2010-05-12, 22:36
Many thanks, Robert. I had not tried your plug-in because it was not clear to me from the description that it supported the 128k Sirius feed. Of course, it does.

And I love the not-so-Sirius dog!

--Frank

mkanet
2011-02-10, 06:46
not-so-Sirius is officially broken and unusable. It looks like flem (plugin author is already aware of it. Thats really too bad; as that was the only plugin that actually played sirius radio correctly on my clients. Just for kicks I tried the native sirius plugin from Squeezebox, within 2-3 seconds I still get the error message, "Stream stopped, you are no longer authorized to listen."

Guy48065
2011-02-10, 10:44
@mkanet,
So 15+ months down the road and there was never a fix for this problem, or just never posted? As a XM subscriber I was blissfully ignorant of the issue until 2/4 when SXM again monkeyed with the service and threw me into the pit with the other Sirius sufferers.
Is the (not so ) Sirius plugin (if & when re-written) my best hope for an uninterrupted stream? Should SXM hire flemming? :)

I like the discussion in this thread & it looks like things were close to a resolution at one point. I'm going to subscribe to this one.

garym
2011-02-10, 10:57
@mkanet,
So 15+ months down the road and there was never a fix for this problem, or just never posted? As a XM subscriber I was blissfully ignorant of the issue until 2/4 when SXM again monkeyed with the service and threw me into the pit with the other Sirius sufferers.
Is the (not so ) Sirius plugin (if & when re-written) my best hope for an uninterrupted stream? Should SXM hire flemming? :)

I like the discussion in this thread & it looks like things were close to a resolution at one point. I'm going to subscribe to this one.

Why can't you use the official Sirius plugin rather than the unofficial "not so sirius" plugin? I'm an xm user and after the changes last weekend, moved to the official sirius plugin and all has worked perfectly once I figure out how to login (had to change my internet streaming login name from my email that I used for logging into XM).

mkanet
2011-02-10, 12:10
Hi Gary, the problem "You are not authorized..." was caused by the native plugin. I'm guessing this issue doesnt happen on newer squeezebox clients. It was suggested by a fellow user with the same issue to use the Notsosirius plugin to avoid that error; which it fixed the problem immediately. I've been very happy with the Notsosirus for several months. However, now that Sirius changed their website to the new webplayer, it broke Notsosirius plugin.

Just for fun, I reverted back to the native plugin, but it hasn't changed any in it's behavior... it produces the "You are not authorized" error within 2-3 seconds. I've already reported this issue to Andy about 1-2 years ago, unfortunately it doesnt look like he was able to fix the issue.

Luckily, the author of Notsosirius is one step ahead of us, he already posted on this google website just recently that his plugin is officially broken:

-----------------------------------------------
http://code.google.com/p/notsosirius-squeezecenter/
News
02/07/2011 - Well crap
It seems Sirius updated the player on the US site, so until I get a chance to fix it the plugin is officially broken. Sirius Canada is still using the old player, so there shouldn't be any problems there.
-----------------------------------------------

Hence, currently, no way to use sirius anymore for people who get the
"You are not authorized" bogus error message.


Why can't you use the official Sirius plugin rather than the unofficial "not so sirius" plugin? I'm an xm user and after the changes last weekend, moved to the official sirius plugin and all has worked perfectly once I figure out how to login (had to change my internet streaming login name from my email that I used for logging into XM).

garym
2011-02-10, 13:10
got it. I wonder what the traits are of the folks getting this message (like you) vs those of us that don't get the message. I'd never tired the official sirius plugin until last week when siriusXM changed things. Until then I'd used the 3rd part XMRadio plugin. I have regular XM (car radio) and I have the internet streaming add-on to XM. I did have to change my username on the SiriusXM webpage for the internet streaming account to work on my SB's. But other than that I didn't do anything special. And I've tested this for several days, with at least 4 hours of streaming and no messages, etc.


Hi Gary, the problem "You are not authorized..." was caused by the native plugin. I'm guessing this issue doesnt happen on newer squeezebox clients. It was suggested by a fellow user with the same issue to use the Notsosirius plugin to avoid that error; which it fixed the problem immediately. I've been very happy with the Notsosirus for several months. However, now that Sirius changed their website to the new webplayer, it broke Notsosirius plugin.

Just for fun, I reverted back to the native plugin, but it hasn't changed any in it's behavior... it produces the "You are not authorized" error within 2-3 seconds. I've already reported this issue to Andy about 1-2 years ago, unfortunately it doesnt look like he was able to fix the issue.

Luckily, the author of Notsosirius is one step ahead of us, he already posted on this google website just recently that his plugin is officially broken:

-----------------------------------------------
http://code.google.com/p/notsosirius-squeezecenter/
News
02/07/2011 - Well crap
It seems Sirius updated the player on the US site, so until I get a chance to fix it the plugin is officially broken. Sirius Canada is still using the old player, so there shouldn't be any problems there.
-----------------------------------------------

Hence, currently, no way to use sirius anymore for people who get the
"You are not authorized" bogus error message.

Guy48065
2011-02-10, 16:57
Why can't you use the official Sirius plugin rather than the unofficial "not so sirius" plugin? I'm an xm user and after the changes last weekend, moved to the official sirius plugin and all has worked perfectly once I figure out how to login (had to change my internet streaming login name from my email that I used for logging into XM).

I am using the native plugin--it's the only game in town apparently for the time being. Never had any major problems with the XM 3rd party plugin so this problem is caused by the switch to the native Sirius plugin. I look forward to the notsoSirius 3rd party plugin since apparently SXM doesn't know how to fix this issue.

Guy48065
2011-02-10, 16:59
Mike,
Please keep up the fight for the (I guess) few of us who are experiencing this issue. Really appreciated!

mkanet
2011-02-11, 06:25
I donated to flemming (a modest amount) and sent him a subsequent email asking him to please fix the issue; as there are people who depend on his plugin. I haven't heard back from him, but I'm pretty sure he got my email and respective paypal donation notice. It goes without saying that a talented guy such as him could be VERY busy; so, expecting him to fix the plugin immediately would be kind of unrealistic. For those of you who use his plugin, maybe you could consider donating any amount, even if its $20 or less. Anything would help. Hopefully that would motivate him to update his plugin. I dont think he has any idea how many people completely depend on his plugin.

-Mike

garym
2011-02-11, 10:45
It would probably help us all diagnose the problem if we could identify why some have the issue and some don't. I'd suggest posting your info. Then we can look for any commonalities among the working vs not working folks. I'll start.

I'm having no problems streaming through regular sirius app to either Squeezeplay or my SB Players (Touch, Transporter, Boom)

1. XM Subscriber
2. Have XM internet streaming subscription
3. I changed my login name for the Streaming account to something different from my login name for my overall SiriusXM account.
3. Running SbS 7.5.2 (vortexbox) and SbS 7.5.3 (Windows 7) (two different locations)
4. Also worked for me with mysqueezebox.com feeding TOUCH and BOOM.

mkanet
2011-02-11, 11:27
I think I might have mentioned this earlier, but I think it mostly affects older clients. I think it mostly happens to Classic squeezebox clients; which there are SEVERAL people who still own these. It also happens to softsqueeze; which is the software version of this hardware player. Some other clients get this message too; but apparently not too often. I'm pretty sure if it was an easy fix Andy would have fixed it over a year ago when he said he would look more closely into this problem.

-Mike


It would probably help us all diagnose the problem if we could identify why some have the issue and some don't. I'd suggest posting your info. Then we can look for any commonalities among the working vs not working folks. I'll start.

I'm having no problems streaming through regular sirius app to either Squeezeplay or my SB Players (Touch, Transporter, Boom)

1. XM Subscriber
2. Have XM internet streaming subscription
3. I changed my login name for the Streaming account to something different from my login name for my overall SiriusXM account.
3. Running SbS 7.5.2 (vortexbox) and SbS 7.5.3 (Windows 7) (two different locations)
4. Also worked for me with mysqueezebox.com feeding TOUCH and BOOM.

garym
2011-02-11, 11:30
I think I might have mentioned this earlier, but I think it mostly affects older clients. I think it mostly happens to Classic squeezebox clients; which there are SEVERAL people who still own these. It also happens to softsqueeze; which is the software version of this hardware player. Some other clients get this message too; but apparently not too often. I'm pretty sure if it was an easy fix Andy would have fixed it over a year ago when he said he would look more closely into this problem.

-Mike

this is useful info. thanks. Can't address the classic issue, but for those running "softsqueeze" I recommend running instead SqueezePlay. I moved to that a couple of years ago from softsqueeze and like it much more (plus it can control other players as well as being a player itself). Download here:

http://downloads.slimdevices.com/nightly/?ver=7.5

mkanet
2011-02-11, 12:38
I use something much nicer than squeezeplay; however, its softsqueeze based. It's integrated into my TV DVR setup, pulls up youtube videos for artists being played, Biography, News, Headlines, etc.

http://i67.photobucket.com/albums/h283/mkanet/Screenshot-1381.jpg

http://i67.photobucket.com/albums/h283/mkanet/Slimplayer-News.jpg


this is useful info. thanks. Can't address the classic issue, but for those running "softsqueeze" I recommend running instead SqueezePlay. I moved to that a couple of years ago from softsqueeze and like it much more (plus it can control other players as well as being a player itself). Download here:

http://downloads.slimdevices.com/nightly/?ver=7.5

garym
2011-02-11, 12:41
I use something much nicer than squeezeplay; however, its softsqueeze based.

Curious, what is it? And does it work with the sirius app for playback? Also, can it act as a controller for other SB players?

edit: sorry, didn't see the pics initially. but the other two questions hold still apply....

mkanet
2011-02-11, 12:46
See above, I just click on the music button on my TV remote and use it on any TV. No need to switch audio inputs, TV inputs, etc. It works for me pretty nicely, but I'm sure it's not for everyone.

Edit, oops I didnt read your questions carefully. It works with Squeezebox server just like any other client. It not a controller, its just part of what my TV setup; which includes respective speakers, etc. I can play broadcast the same channel on all TV/speakers if I wanted to, but never really needed to do that.


Curious, what is it? And does it work with the sirius app for playback? Also, can it act as a controller for other SB players?

edit: sorry, didn't see the pics initially. but the other two questions hold still apply....

bwaldron
2011-02-11, 13:11
I think I might have mentioned this earlier, but I think it mostly affects older clients. I think it mostly happens to Classic squeezebox clients; which there are SEVERAL people who still own these. It also happens to softsqueeze; which is the software version of this hardware player.

That isn't -- by itself -- the key variable. I use two Squeezebox "classic" devices (one SB2, one SB3) with no problems; nor do I experience them on any of my PCs using SqueezePlayer. (At least so far, with extensive use in the week since the forced switch to the official app from the 3rd-party XM plugin.)

The rest of my setup is the same as gary's above (save that I don't have a VortexBox, use Win7 exclusively for the server).

mkanet
2011-02-11, 13:35
Thanks bwaldron. Hmm.. I guess that's why it wasn't that easy to fix. All I know is whatever is different about the NotSoSirius plugin, is the reason why it works correctly under all circumstances (until Sirius changed their website in US).


That isn't -- by itself -- the key variable. I use two Squeezebox "classic" devices (one SB2, one SB3) with no problems; nor do I experience them on any of my PCs using SqueezePlayer. (At least so far, with extensive use in the week since the forced switch to the official app from the 3rd-party XM plugin.)

The rest of my setup is the same as gary's above (save that I don't have a VortexBox, use Win7 exclusively for the server).

bwaldron
2011-02-11, 15:52
Thanks bwaldron. Hmm.. I guess that's why it wasn't that easy to fix. All I know is whatever is different about the NotSoSirius plugin, is the reason why it works correctly under all circumstances (until Sirius changed their website in US).

I hope my luck holds out. I did notice that there was no "keep alive" option in the official app like there was in the XM plugin, and that concerned me -- but hasn't bitten me yet.

Guy48065
2011-02-11, 20:55
I think I might have mentioned this earlier, but I think it mostly affects older clients. I think it mostly happens to Classic squeezebox clients; which there are SEVERAL people who still own these.

Mike I do remember you mentioning this previously so yesterday I upgraded the SBS to 7.5.3 and since then I haven't experienced any errors. I'm running the SBS on a XP notepad dedicated as my media server in the same room as the SB. I do have a Classic (Firmware 132) and a Duet remote (usually off).

Fingers crossed the logouts don't resume.

bwaldron
2011-02-12, 11:55
There is an option for anyone who is getting kicked out of the SiriusXM streaming: XMTuner (http://www.xmtuner.net/) can be used to generate channel URLs on your LAN that can be played (and assigned to favorites) via Squeezebox Server.

Obviously not as friendly as the app, and you'll lose track info display, but it does work and will stream for as long as you like without being kicked off (in my experience).

It's a Windows app, so you'll need a Windows machine on your network to run it.

Guy48065
2011-02-12, 20:15
I use XMtuner on my PC at work & like the way it works. Simple. No problems. Maybe the developer will create a plugin for us? :)

Guy48065
2011-02-12, 20:18
Fingers crossed the logouts don't resume.

Well that was short-lived. 2 days with no logoffs but today I got the dreaded error several times.
<sigh>

mkanet
2011-02-14, 05:55
I'm using 7.5.3 already. It's possible this issue is limited to softsqueeze. If it's not too much trouble, could you install the softsqueeze client on any machine on your lan.. then try native sirius plugin?

http://sourceforge.net/projects/softsqueeze/files/softsqueeze/softsqueeze-3.8/softsqueeze_windows_3_8.exe/download

If you want to keep your PC very clean without any traces of softsqueeze after testing, you can download the zip file with all the stuff to get it started:

http://sourceforge.net/projects/softsqueeze/files/softsqueeze/softsqueeze-3.8/softsqueeze_3.8.zip/download

All you have to do is point it to the private LAN IP of your XP server. I think you have to install the java mp3 audio as well; which is harmless; and makes java mp3 playback in general sound better:
http://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/VerifyItem-Start/javamp3-1_0.exe?BundledLineItemUUID=_HWJ_hCurCcAAAEuI_NZBy Q5&OrderID=.hKJ_hCu9s0AAAEuEPNZByQ5&ProductID=9sfACUFBFJoAAAEYuxQ5AXuF&FileName=/javamp3-1_0.exe

Thanks so much for your time,
Mike


Mike I do remember you mentioning this previously so yesterday I upgraded the SBS to 7.5.3 and since then I haven't experienced any errors. I'm running the SBS on a XP notepad dedicated as my media server in the same room as the SB. I do have a Classic (Firmware 132) and a Duet remote (usually off).

Fingers crossed the logouts don't resume.

mkanet
2011-02-14, 06:28
Guy48065, could you please, PLEASE donate to Flemming. I dont think he realizes that there are people who completely depend on his plugin. I'm 100% sure my bugzilla report I placed to fix the Sirius radio plugin will be ignored or pigeonholed; as it seems to work for many people; despite it being a reproducible issue for some of us.

Anyone else who wants to help contribute by donating to Flemming, below is the official NotSoSirius plugin website with a donation link:

http://code.google.com/p/notsosirius-squeezecenter/

Thanks,
Mike


Well that was short-lived. 2 days with no logoffs but today I got the dreaded error several times.
<sigh>

virgiliomi
2011-02-14, 06:58
I don't believe the official Sirius plugin works with SoftSqueeze/Squeezeplay. I've not had any luck using it on SqueezePlay on my home PC, or on my iPad with SqueezePad. This is likely because Sirius would rather you use their web player.

I've had no problems whatsoever with the official Sirius plugin/app on my SB Boom, Receiver, or Radio, with the setups detailed in my signature.

bwaldron
2011-02-14, 07:33
I don't believe the official Sirius plugin works with SoftSqueeze/Squeezeplay.

The official Sirius app certainly works for me with SqueezeSlave and SqueezePlay (though you don't get the track info embedded in the WMA stream because it has to transcode).

Guy48065
2011-02-14, 09:28
I'm using 7.5.3 already. It's possible this issue is limited to softsqueeze. If it's not too much trouble, could you install the softsqueeze client on any machine on your lan.. then try native sirius plugin?
Mike I'm not tracking why you want me to install a player on my PC. I have no problems listening on the PC--it's when I serve to my HT that I get kicked off my SXM online stream. Are you just wanting me to test if I also get kicked off using the PC player?

jcwilcox
2011-02-19, 16:40
The "stream stopped" message when playing Sirius radio through my Duet has been a continual aggravation since I've owned the Duet and played Sirius. It's been going on for years with no apparent solution. In fact, I'm not clear whether it's a Logitech issue or a Sirius issue. Will this ever be fixed or is it just a chronic problem with no solution?

mkanet
2011-02-19, 17:33
It's definitely a Logitech SBS/SqueezeNetwork issue. It's really too bad that this issue isn't taken seriously by Logitech developers as a reproducable problem for some people.


The "stream stopped" message when playing Sirius radio through my Duet has been a continual aggravation since I've owned the Duet and played Sirius. It's been going on for years with no apparent solution. In fact, I'm not clear whether it's a Logitech issue or a Sirius issue. Will this ever be fixed or is it just a chronic problem with no solution?

jcwilcox
2011-02-20, 12:34
Mike, thanks for replying and I guess I'll just have to continue to be patient and hope it's fixed someday.

John

Guy48065
2011-02-20, 15:13
Today I had the same station playing for over 6 hours with no interruption. It just now stopped. Odd how my error-free times vary from several hours to as little as 15 minutes. Could going online on a PC that is in my wireless network but has nothing related to the SBS installed? Grabbing at straws here...

I'm wondering if the ones who never see this problem are "button pushers"? Maybe I get this a lot because I tend to play 1 station all day.

hoob
2011-02-23, 19:58
It would probably help us all diagnose the problem if we could identify why some have the issue and some don't. I'd suggest posting your info. Then we can look for any commonalities among the working vs not working folks. I'll start.

I'll officially add my voice to this thread. Another unhappy XMRadio Plugin used thrust into the pits of despair of using the official Sirius module. The "not so Sirius" plugin doesn't seem to work for my logon information, so I'm stuck trying to use the official one for now..

I too have the "you are not authorized" error within seconds or minutes, when trying to stream a Sirius to channel... BUT... Only on one of my devices!

COMMON:
1. SqueezeboxServer 7.6-beta for Debian running on my HTPC server
2. Fast/reliable connection to the internet
3. American XM Radio Online account, paying for the premium download quality, recently converted to common SiriusXM account

NOT AUTHORIZED ERROR:
1. Squeezebox Radio in the bed room
2. Wireless G connection at 85% signal and reliable
3. Device DOES support WMA natively
4. Also fails with same error when connected via ethernet LAN

WORKS FINE:
1. My old Squeezebox 2 from 2002, in the den
2. Wired LAN connection
3. Device does NOT support WMA natively...

I have a MySB account but... I'm not really sure how it's used. SBS is configured to use it, it has the Sirius app installed with my logon credentials, etc. Other than that I have no idea how or why MySB might fit into the equation. I've never used it for anything else and don't really understand what the service really is, actually.

My *suspicion* is that the NOT AUTHORIZED error is related to streaming the WMA directly to the device, perhaps with buffering/retry issues. This is purely based on the fact that where the Sirius streaming does work, there's a WMA-to-PCM conversion taking place at the server.

That being said, any SBS experts for Linux know what convert.conf settings I could make to FORCE my Squeezebox Radio connection to always reencode/stream WMA as PCM for that device, even if it supports WMA natively? Just want to test, as a hunch...

bwaldron
2011-02-24, 15:07
My *suspicion* is that the NOT AUTHORIZED error is related to streaming the WMA directly to the device, perhaps with buffering/retry issues. This is purely based on the fact that where the Sirius streaming does work, there's a WMA-to-PCM conversion taking place at the server.

I just got the error today for the first time, on a newly-purchased Squeezebox Radio. I'm a former XM plugin user; I've been using the official app since SiriusXM changed things a few weeks back; I have never gotten the error on either SqueezePlay or my SB3 (which I believe does WMA without transcoding, as does the SB2 or so I thought).

Just another data point.

UPDATE: Have listened to a couple of XM channels on the SB Radio for a few hours each; the error has yet to re-appear.

toby10
2011-02-25, 04:09
.........
I have a MySB account but... I'm not really sure how it's used. SBS is configured to use it, it has the Sirius app installed with my logon credentials, etc. Other than that I have no idea how or why MySB might fit into the equation. I've never used it for anything else and don't really understand what the service really is, actually........

You do use MySB.com, every time you access an App or use any of the Internet Radio or App menu's, whether you are using SBS server or not.
When using SBS server your players connect to SBS, then SBS uses MySB.com in the background.

hoob
2011-02-25, 16:52
You do use MySB.com, every time you access an App or use any of the Internet Radio or App menu's, whether you are using SBS server or not.
When using SBS server your players connect to SBS, then SBS uses MySB.com in the background.

Don't use Apps. Don't use Internet Radio. Don't use the menus (just favourites/presets set from SBS Web Interface.) My SB Radio gives some sort of error about being connected to the wrong account and to call Support. Still have no idea what good MySB is :)

toby10
2011-02-26, 03:54
Don't use Apps. Don't use Internet Radio. Don't use the menus (just favourites/presets set from SBS Web Interface.) My SB Radio gives some sort of error about being connected to the wrong account and to call Support. Still have no idea what good MySB is :)



......
3. American XM Radio Online account, paying for the premium download quality, recently converted to common SiriusXM account......

Umm... XM/Sirius as it applies to SB players *is* internet radio, it is streamed over the internet, what do you call it? ;)
The XM plugin no longer functions, you must use the *app* on MySB to stream XM/Sirius.
So in order to get the XM/Sirius internet radio streams you must indeed use the App, which you navigate via menu's. All of which uses MySB.com ;)

mkanet
2011-06-20, 10:34
There's a growing list of people who have found their way to Bug 17157 - Sirius Radio error: "Stream stopped, you are no longer authorized to listen." AFTER it was marked as "WONTFIX". I still cant believe Logitech developers rather sweep this issue under the rug than fix it.

I'm not sure what it will take for Logitech to realize this is a problem with SB/SqueezeNetwork servers handling streams/authentication incorrectly; triggering multiple authentications. It's NOT because users are physically trying to use more than one login.

tebrown
2011-06-21, 17:06
Please, if you experience the "You are not authorized" error while listening to Sirius, comment and vote on this bug. Maybe we can get Logitech's attention if enough people report having an issue.

http://bugs.slimdevices.com/show_bug.cgi?id=17157

john_99
2011-06-29, 13:33
Well, I have been getting the "Stream stopped: you are no longer authorized to listen" error for a couple of weeks now.

Sirius worked fine on my SBB for the past 7 months until now.

Per the Logitech Help, I did a full reset, entering my WEP, Sirius app, etc., with no success. They told me that it was a Sirius issue. Yes, it is a serious issue.

I called sirius and they were fixated on the radio ESN# (I gave up on that.)

So, I voted, but see that there are only 12 votes.

Maybe I should just replace my SBB with my desktop computer on my kitchen table!

Ron Olsen
2011-06-29, 14:26
See http://forums.slimdevices.com/showpost.php?p=637411&postcount=174 for a workaround that eliminates the "you are no longer authorized to listen" errors.

You have to replace the Sirius ProtocolHandler.pm with the version given in the above post.