This issue has been reported multiple times by various people.  This happens on all Windows OS versions and Java versions.  I've even contacted "Andy" from the forums via AIM Internet chat about this; sending him logs, etc.  IIRC, he said that this isn't easy to fix; and, has to do with the backend Sirius servers.  That was around 2 years ago.

Currently, people having this issue are forced to use the 3rd party NotSoSirius plugin; which doesnt depend on backend servers to stream Sirius Radio.

Can someone please fix this?

There's nothing we can do to fix this one, we have to honor the return value from Sirius when they tell us to stop playing.

Andy, the return value is caused by Squeeze Network backend servers not handling the stream correctly (producing simultaneous login/playback requests).  In these circumstances, only ONE SBS client is playing ONE Sirius Radio station using a valid Sirius Radio Premium Account.  This problem was reported by multiple people under various circumstances; none of which were due to multiple clients trying to use the same account.  This issue never happens when using a premium account and 3rd party Sirius SBS plugins.

This bug was introduced about 2 years ago when there was some major changes on the Sirius backend servers (I think around the time Logitech came into play).  These changes also broke Artist - Song title information being passed to the SBS CLI.  It used to work great under earlier versions of Squeeze Center and respective SN backend servers.  

This has been reported on multiple clients and OS's under the same circumstances.  For some people, the error is returned within 3-10 seconds; and for others, it takes up to a minute or so (with no other clients turned on).

(In reply to comment #2)
> There's nothing we can do to fix this one, we have to honor the return value
> from Sirius when they tell us to stop playing.

I agree that you have to honor the return value, but I think there must be something that is causing this to occur on the backend since it occurs within the hour every time I use the builtin Sirius plugin even though I can say with 100% confidence that nobody else is using my account (because I changed my credentials).

I can also say with 100% confidence that nobody else is using my account as well; since this happens on any new usename/password I create.

It's interesting that people like us have the same exact issue; but have entirely different clients and OS's.  The only thing that's we share that's the same is the Sirius backend servers on SB Network.  Hopefully this issue wont be pigeon holed/chalked up as "wont-fix" just because its not easy to fix; as it's been reported over and over again by various people on different configurations (on the forum and here).  I have a feeling whatever was changed on the backend Sirius server might be related to the SiriusXM Artist/song title not getting passed to the SBS CLI since both issues happened right around the same time.  The only difference is the SiriusXM Artist/Song title not getting passed to the CLI is preproducable on all setups last time I checked.

(In reply to comment #4)
> (In reply to comment #2)
> > There's nothing we can do to fix this one, we have to honor the return value
> > from Sirius when they tell us to stop playing.
> 
> I agree that you have to honor the return value, but I think there must be
> something that is causing this to occur on the backend since it occurs within
> the hour every time I use the builtin Sirius plugin even though I can say with
> 100% confidence that nobody else is using my account (because I changed my
> credentials).

*** This bug has been confirmed by popular vote. ***

Interesting how this bug has a status as "RESOLVED WONTFIX"; yet at the same time it's recognized as:

 "*** This bug has been confirmed by popular vote. ***

I'm pretty sure I had a bug report on this same issue a couple of years ago; but didnt get too far either.

RESOLVED WONTFIX???  This has been a problem for a while now.  Please logitech fix your server issues!

(In reply to comment #8)
> RESOLVED WONTFIX???  This has been a problem for a while now.  Please logitech
> fix your server issues!
Totally agree.  An organization that is dedicated to solving end-user problems does not pass the buck saying "it's not our problem -- it's a problem on the Sirius end".  The correct approach is to accept ownership of the problem and work with Sirius to resolve it.

Maybe the Logitech devel team doesn't have the resources to work with Sirius to fix this, but that's what should happen, if customer satisfaction means anything to Logitech.

So what recourse do we have if Logitech won't fix this? The Not So Sirius plugin no longer works and I don't believe it's Sirius' problem so canceling my subscription (while a likely outcome as the result of this) is not an associative response. 

If Logitech needs someone to reproduce this, please have someone contact me and I will provide my source IP, username and I'll even get on the phone with an engineer to let them know when it happens.

I'm will to do the same as Travis if you guys need another machine to test against as well.  This bug has gone unfixed/ignored for way too long.

Ok.. so I had been listening to Sirius for about an hour and I got the "Stream Stopped" message. I hit play to restart, and 1 minute later it stopped again.  I didn't do ANYTHING else to any of my other players during this time.  Someone *please* look at this on the Squeezebox server side of things.

Please fix as this has been a ongoing problem that needs to be taken care of.

As someone who is also regularly experiencing this, I find the RESOLVED WONTFIX ridiculous.

Also getting this, since Logitech advertises the capability, then it should work.

I've looked at the Slim code that causes the server to stop playback, and I agree with the Slim devs' assertion that the problem is on Sirius' side. 

Andy/Slim: until you get this fixed-fixed, would your agreement with Sirius permit you to be less aggressive about *immediately* stopping playback in ProtocolHandler.pm (line 271) when the stream is not open? Given that Sirius is clearly the flake here, maybe you could allow a grace period and fail playback after some number of failed attempts...

I am also a former XM, now SiriusXM customer who is paying for Internet access. I am running Squeezebox server and am using a Squeezebox Touch as the user interface. I'm also getting the "not authorized" message after playing several stations through my touch. Please reopen the case to fix this bug.

I don't see how Logitech Squeezebox can promote the fact that Sirius Radio works on the Squeezebox when the stream constantly stops and you get the error "Stream stopped, you are no longer authorized to listen."  I checked to see if any of my other squeezeboxes are on (they weren't) or if I'm streaming from Sirius on my phone or computer (I wasn't), so I don't understand why I get this message.  


"*** This bug has been confirmed by popular vote. ***

(In reply to comment #18)
> I don't see how Logitech Squeezebox can promote the fact that Sirius Radio
> works on the Squeezebox when the stream constantly stops and you get the error
> "Stream stopped, you are no longer authorized to listen."  I checked to see if
> any of my other squeezeboxes are on (they weren't) or if I'm streaming from
> Sirius on my phone or computer (I wasn't), so I don't understand why I get this
> message.  
> 
> 
> "*** This bug has been confirmed by popular vote. ***

This is from http://www.mysqueezebox.com/appgallery:

With SiriusXM and Squeezebox you can
o Listen to over 100 channels including 100% commercial-free music, news, talk, comedy and live sports coverage
o Enjoy Howard Stern, 24/7 SIRIUS NFL Radio, Martha Stewart, NPR and more
o Discover special artist’s channels including E Street Radio, Grateful Dead Channel and more
Effortless entertainment all at your fingertips

Since this is a WONTFIX, please add the following bullet point:
o Enjoy interrupted listening and press play every few minutes when you get erroneous "you are no longer authorized" messages.

You have to ask why these stop signals are coming from Sirius, and whether it has to do with the SBS implementation to begin with. If it does not, then it's a MAJOR freaking bug on Sirius' side and it should be Logitech's responsibility to see that Sirius fixes it. It's not going to be fixed otherwise.

Created attachment 7320 [details]
Revised version of the Sirius ProtocolHandler.pm that fixes the "you are no longer authorized to listen" error.

(In reply to comment #21)
> Created an attachment (id=7320) [details]
> Revised version of the Sirius ProtocolHandler.pm that fixes the "you are no
> longer authorized to listen" error.

The source for this fix: http://forums.slimdevices.com/showpost.php?p=637411&postcount=174

That's not a fix.  It's a temporary workaround.  The problem still needs to be fixed.

(In reply to comment #23)
> That's not a fix.  It's a temporary workaround.  The problem still needs to be
> fixed.

Call it a temporary workaround if you like.  The fact is this: using this version of ProtocolHandler.pm stops the erroneous "you are no longer authorized to listen" messages.  

It's a way for users to eliminate the problem on their own. I will be using it until Logitech and Sirius provide a proper fix. I doubt this will ever happen, given the WONTFIX status of this bug.

I am a paid internet radio subscriber to Sirius, however, I consistently get a stopped stream and the message like: "stream stopped....you are no longer authorized to use the service" I called Sirius and the gentleman reset everything and apologized. I was hopeful until about 10 minutes into playing a station...the same thing occurred. I do not know exactly where to turn at this time , so I am posting this in hopes that others may have an answer. Anyone else having this problem??? Thank you.
__________________

Let me take another look at this.

This really is a feature of Squeezebox that they should have notified us about.  I bought this so I could have uninterrupted music....I didn't know 15 minutes was the longest it played.  Please fix this.

(In reply to comment #26)
> Let me take another look at this.

Please do. I have a similar problem with SBRs (I have three) fed by server running on Mac OS X Lion. Frequency of "No longer authorized" messages has increased unacceptably recently (often after 5 minutes or so ... and I can keep 're-authorizing' all night, at five minute intervals).

Seems to me (I'm a computer scientist) that somehow Sirius knows they are streaming to Squeezebox?

Why is this not a problem for PC-based software players like Pulsar and Radium? They don't seem to have any difficulty coding around the "no longer authorized" messages or they are not receiving them.

Also, I note that I do not have to "re-authorize" when using the XM/Sirius hardware in my automobile.

Seems as if they are particularly hostile towards Squeezebox users?

As others have mentioned, I am definitely a long-time paid user. I can understand Sirius trying to limit "pirated access" but here they are clearly penalizing and alienating their loyal, paid customer base. I am not far from canceling my Sirius account and tossing my SBRs into the trash because of this.

Another workaround I have considered is simply running Radium on my iMac server and just streaming the audio output to (possibly multiple) SBRs -- essentially treating the SBRs as dumb speakers. How ridiculous it is that I would have to even consider such a thing ...

phillip

Andy,
Please take another look at this.  I have a squeezebox touch and noticed the problem became much worse about 3 weeks ago.  I'm at Squeezeplay 7.6.0 r9458 and get the error after 15 minutes, consistently.  I've tried to implement the workaround by placing an updated ProtocolHandler.pm in /usr/squeezecenter/Slim/Plugin/Sirius on the squeezebox's filesystem, but it does not work.  The player seemed to ignore ProtocolHandler.pm.  As a test, I deleted ProtocolHandler.pm from the directory and the player ran fine without the file and I get the error after 15 minutes.  This is very frustrating since I had few problems during the 30 day trial and for several weeks after I bought a subscription.  Please help.

This has become *increasingly* obnoxious... stream stops several times an hour.  Also occurring with mysqueezebox.com.  Logitech/Sirius needs to fix this ASAP... please bump the priority.

As with others, willing to help any way I can...

(In reply to comment #30)
> This has become *increasingly* obnoxious... stream stops several times an hour.
>  Also occurring with mysqueezebox.com.  Logitech/Sirius needs to fix this
> ASAP... please bump the priority.
> 
> As with others, willing to help any way I can...

I agree that this is obnoxious. The workaround could be used if you are running a server locally, but I would like to continue to take advantage of connecting to mysqueezebox.com.  I mainly use my squeezeboxes to listen to Sirius and I loved the idea of not having to run a server 24x7. It's a shame that the feature is there, but cannot be used.  It really depreciates the value of these devices.

ProtocolHandler doesn't seem to be the problem... the 'call'

 my $statusURL = Slim::Networking::SqueezeNetwork->url(
                "/api/sirius/v1/playback/streamStatus?content=" . uri_escape(
$status->{content} )
        );

is returning 'unauthorized' (ERRONEOUSLY).  Please find out WHY.  

(the plumbing behind this call is undoubtably what is also causing the failure with mysqueezebox.com)

The "hacked" ProtocolHandler.pm file stopped working with squeezeboxserver-7.6.1-0.1.33011.noarch.rpm  - stream stops about every ten minutes.

http://forums.logitech.com/t5/Squeezebox-Players/Sirius-App-stops-quot-no-longer-authorized/td-p/657348

Here is a comment from a customer about what a Senior Tech at Sirius told them in comment 9.

(In reply to comment #34)
> http://forums.logitech.com/t5/Squeezebox-Players/Sirius-App-stops-quot-no-longer-authorized/td-p/657348
> 
> Here is a comment from a customer about what a Senior Tech at Sirius told them
> in comment 9.

It is com. 9 in the thread I posted...not on here...sorry

(In reply to comment #33)
> The "hacked" ProtocolHandler.pm file stopped working with
> squeezeboxserver-7.6.1-0.1.33011.noarch.rpm  - stream stops about every ten
> minutes.

Reverted back to squeezeboxserver-7.6.1-0.1.32942.noarch.rpm and replaced the
stock ProtocolHandler.pm file under
/usr/lib/perl5/vendor_perl/Slim/Plugin/Sirius with the hacked one mentioned in
this thread, NO SIRIUS STREAM STOPPAGE IN TWO DAYS! FYI!!

(In reply to comment #36)
> (In reply to comment #33)
> > The "hacked" ProtocolHandler.pm file stopped working with
> > squeezeboxserver-7.6.1-0.1.33011.noarch.rpm  - stream stops about every ten
> > minutes.
> 
> Reverted back to squeezeboxserver-7.6.1-0.1.32942.noarch.rpm and replaced the
> stock ProtocolHandler.pm file under
> /usr/lib/perl5/vendor_perl/Slim/Plugin/Sirius with the hacked one mentioned in
> this thread, NO SIRIUS STREAM STOPPAGE IN TWO DAYS! FYI!!

PS- if it matters, I'm running a sync-group with a SBB, SBR and a SBT.

OK, I can easily reproduce this by simply playing 1 Sirius stream on 1 player, then starting a second stream on another player. I'm checking with my contact at Sirius to see if this is our bug or if they intentionally block this. This would also explain why synced players using only MySB run into this bug, since each player gets its own stream in that case. (SBS sync users would not be affected, unless you started a 3rd player.)

(In reply to comment #35)
> (In reply to comment #34)
> > http://forums.logitech.com/t5/Squeezebox-Players/Sirius-App-stops-quot-no-longer-authorized/td-p/657348
> > 
> > Here is a comment from a customer about what a Senior Tech at Sirius told them
> > in comment 9.
> 
> It is com. 9 in the thread I posted...not on here...sorry
Here is the comment:
"I finally had a chance to call Sirius tech support and finally got to speak to a "senior tech." He claims that the original policy was to allow 90 minutes of Internet listening, at which point you would get a message to click to continue. This was done to preserve bandwidth to prevent leaving it on without listening. Now, according to the tech, the time has been changed to 15 minutes because too much bandwidth is being used- "no longer authorized" really means "your allotted time is up.". Bad enough for a free service, ridiculous for a paid one.  He said that this would be posted on their website soon. If this is correct, I plan on canceling my Internet accounts. I have already sent a letter to the NY State Department of Consumer Affairs, the Better Business bureau and the State Attorney General. I find this to be outrageous if true; more outrageous if not true."

This is DEMONSTRABLY untrue.  Their own web player does no such thing.  (And I bet the Android, etc. players don't either... I'll check).

Do the Sirius streams on SBs even come directly from Sirius, or is it SB restreaming Sirius streams?   In either event, we're PAYING for that bandwidth.

So that's normal and the way it's always worked (I must have forgot).

The word from Sirius: "You certainly can't listen to different channels in 2 places with one account."

So my question is: does anyone have this problem who only uses a single player and never plays Sirius anywhere else but on that player? If so, I can't reproduce this case, so I need some help figuring out what you might be doing differently. Do you change channels right before it kicks you off for example?

If you use synced players on MySB, there is no way to avoid this bug but to use SBS. You probably want to do this anyway because synced radio on MySB cannot sync perfectly like it can on SBS.

The 90-minute thing is true for PC/browser access only. Our timeout is 8 hours of inactivity.

I have the issue (as stated above in comment 8) in where I have 4 sb players in a sync group listening a single channel.  After 20 minutes or so I get the error message.  I am only playing sirius on that player and no where else.  I am not changing channels or anything, just listening.

Thanks!
Dustin Sterkenburg

(In reply to comment #40)
> So that's normal and the way it's always worked (I must have forgot).
> 
> The word from Sirius: "You certainly can't listen to different channels in 2
> places with one account."
> 
> So my question is: does anyone have this problem who only uses a single player
> and never plays Sirius anywhere else but on that player? If so, I can't
> reproduce this case, so I need some help figuring out what you might be doing
> differently. Do you change channels right before it kicks you off for example?
> 
> If you use synced players on MySB, there is no way to avoid this bug but to use
> SBS. You probably want to do this anyway because synced radio on MySB cannot
> sync perfectly like it can on SBS.

(In reply to comment #40)
> So that's normal and the way it's always worked (I must have forgot).
> 
> The word from Sirius: "You certainly can't listen to different channels in 2
> places with one account."
> 
> So my question is: does anyone have this problem who only uses a single player
> and never plays Sirius anywhere else but on that player? If so, I can't
> reproduce this case, so I need some help figuring out what you might be doing
> differently. Do you change channels right before it kicks you off for example?
> 
> If you use synced players on MySB, there is no way to avoid this bug but to use
> SBS. You probably want to do this anyway because synced radio on MySB cannot
> sync perfectly like it can on SBS.


Andy,

 I have definitely had this problem using SBS 7.5.x, running Ubuntu 11.04 and a squeezebox touch.  Sometimes, it would play for hours, and other times it would only go for minutes.  I was never able to reproduce this problem when I ran a SBS on MacOS, but I think that was really more of a coincidence than anything. I bet if you let it run long enough, you'll eventually get this error.

(In reply to comment #40)
> So my question is: does anyone have this problem who only uses a single player
> and never plays Sirius anywhere else but on that player? If so, I can't
> reproduce this case, so I need some help figuring out what you might be doing
> differently. Do you change channels right before it kicks you off for example?

I can verify that the problem does indeed occur on a Sirius ID not used anywhere else.  As part of PD, I changed my Sirius ID and Password (and also changed my MySB ID and Password, and reconfigured Sirius there).  At that time, no other device could POSSIBLY log on to my Sirius account, yet the 'Stream stopped...' still occurred (REPEATEDLY).  Failed on both MySB and SBS.  And no, nothing special... just pressed Play on the SB.

I use my Sirius ID on a single SB, and now have it again configured on Android, but use that very infrequently (and never around the time of the SB failures).  I did verify tonight that Android Sirius did not time out after 15 or 30 minutes.

(In reply to comment #40)
> So my question is: does anyone have this problem who only uses a single player
> and never plays Sirius anywhere else but on that player? If so, I can't
> reproduce this case, so I need some help figuring out what you might be doing
> differently. Do you change channels right before it kicks you off for example?

I can also confirm I only use a single player and never use the Sirius login for anything else. I get the problem with MySB and SBS. Timeouts usually occur after <10 mins listening. 

I can test anything you need testing with this basic setup

Running latest version of SbS nightly:
Version: 7.6.1 - r33044 @ Thu Aug 11 02:05:41 PDT 2011
running on Win7 (64) machine.

Seem to be almost consistently getting the "Stream stopped..." message just before I hit 15 minutes.

Changing this to MySB as any fix here can be done entirely on our side.

(In reply to comment #38)
> OK, I can easily reproduce this by simply playing 1 Sirius stream on 1 player,
> then starting a second stream on another player. I'm checking with my contact
> at Sirius to see if this is our bug or if they intentionally block this. This
> would also explain why synced players using only MySB run into this bug, since
> each player gets its own stream in that case. (SBS sync users would not be
> affected, unless you started a 3rd player.)

Yes, Sirius certainly doesn't want two streams playing with one ID.  But the end result of starting another Sirius player somewhere and the BUG we're discussing is identical... 'unauthorized' is somehow getting returned.

The thing to do (IMHO) is to 'borrow' someone's ID that regularly fails, and monitor the point where SB contacts Sirius.  Either something is getting corrupted on the SB side (and Sirius appropriately returning 'unauthorized') or Sirius is erroneously returning 'unauthorized' with 'authorized' credentials.

I am hoping that this serious Sirius stoppage issue is fixed before my renewal is lapsed. I would recommend that it be totally fixed for mysb.com as well as SBS. I am predominantly a SBS user because of the sync capability. Sirius is mainly a music servic(although I know there are news/talk stations). For me, music from Sirius is synced multiple rooms.

I was having this problem under 7.5 running on a Mac; I was able to fix it by using the replacement "protocol handler.pm" file. However, the upgrade to 7.6 seems to have broken that fix.

I have two players, but they are not synched and I only use one at a time. I get the "you are no longer authorized" message after about 15 minutes.

Been having this issue for about 5 weeks now.  I stream Sirius to my Squeezebox radio ( from MySqueezebox.com ).  I've tried contacting both Sirius and Logitech and noone will even admit to knowing about the issue.  I've tried deleting the acct and app from mysqueezebox and reloading ... doesn't work.  I've had Sirius send a "refresh" signal .... didn't work.
My brother has the same problem as me with his unit / acct.  The stream plays for about 15 minutes and then the "no longer authorized" message appears.

I pay way too much for Sirius to get this kind of service.   I don't get this issue when playing the stream through the Sirius iphone app or on the Pulsar program for my Mac.  It's got me thinking that the problem is on the Logitech end ....

Wonder if Grace Digital Audio ( Recieva Radio service ) has this issue?  I'll buy one of their units if it works better than this,

(In reply to comment #51)
> Been having this issue for about 5 weeks now.  I stream Sirius to my Squeezebox
> radio ( from MySqueezebox.com ). 

I too have been having this annoying problem every 10-15 minutes or so when I am streaming sirius favorites to my duet using squeezebox.com.  I had the same problem when connecting via squeezebox server on my PC as well.  Then, when I copied the new ProtocolHandler.pm (above) into the appropriate place on my PC, then exited and restarted squeezebox server - all was wonderfully fine.  No more stream stoppage with the "You are no longer authorized ....".  Now, if only squeezebox.com can be fixed!  Please!

Was forced to update serve to continue to get rhapsody.  Update destroyed my ability to listen to Sirius.  Get this error constantly -- never got it on the old server.  To add insult to injury, all of the presets on the radio that refer to Sirius stations are removed after this error.  It's ridiculous that this has gone on so long.  Please revert to the plugin until this is fixed.

Add one more to the list.  Bought the Squeezebox just so I could easily listen to Sirius.  Some days it will play for hours without incidence but most days every 10 or 15 minutes I'll run into the authorization issue and it will stop playing.  After restarting it two or three times I'll just give up and turn on Pandora instead which will play all day.  As others have stated apps like the Sirius one on my iPod Touch don't have this problem.  That one times out after 90 minutes as Sirius says it will but never like the Squeezebox who's app is obviously buggy and needs attention!

I wonder why just now there's so much attention to this problem.  I first brought this to Andy's attention almost 3 years ago via AIM chat and also via forum PM.  He said he would look into it.  Anyway, I'm just glad this time there are enough people who are forcing this issue to be resolved.  I sure as heck couldn't do it on my own.

I have also been trying equally as hard (and just as long) to get the "Broken Sirius artist and title metadata in the CLI" bug fixed.  Unfortunately that one also gets ignored repeatedly.  I have been reporting that one on bugzilla for years too.

Same issue for me.  I agree it has been getting worse.  I've ignored it for months at a time, but am now telecommuting and in the car much less often.  Without a fix, I'm seriously considering either cancelling Sirius or swapping my Squeezeboxes for an alternative.

I can also confirm this is happening all the time, at least for the past few months. I even purchased a new Squeezebox Radio yesterday direct from Logitech and that unit also has the same issue. So that proves earlier and late model Squeezeboxes have the same issue.

(In reply to comment #40)

> So my question is: does anyone have this problem who only uses a single player
> and never plays Sirius anywhere else but on that player? If so, I can't
> reproduce this case, so I need some help figuring out what you might be doing
> differently. Do you change channels right before it kicks you off for example?
> 


Andy, I'm only using the one player ... I don't access the stream from multiple units at the same time.

I have had customers report that they do one only one device with this issue and we have rolled back to 7.5.4 and the issue still occurs.



Can someone verify whether this may have to do with the report a customer gave about Sirius changing their refresh time from 90 minutes to 15 minutes and if the services we access has this updated to it?

XM typically quits on me after 10 seconds or less, on a single device.  I really hope there are plans to fix this soon.

I've been dealing with this problem on and off for some time now and have multiple tickets which were opened with Logitech.  It was suggested that I put my experiences here. 

I Sirius account was originally on the XM side of the deal, initially the Sirius interface on the squeezebox did not support the XM accounts.  Eventually that problem was resolved but used the Sirius channel lineup vs XM.  I didn't have any problems for about a month or so and then the service stopped for no apparent reason.  The XM account continued to work on the my laptop and ipad so I wasn't sure what was going on.  After contacting both logitech and Sirius I did find out that Sirius had converted systems and merged accounts and there was a problem with my account setup on the Sirius side.  They made a change to the account but I found the problem on the Squeezebox did not go away.  I had to ultimately delete my sirius account information on the squeezebox, delete and reinstall the sirius interface and then re-enter by sirius account info.  Once this was accomplished everything (early Feb 2011) everything worked fine for about a month and a half.

Now getting to my experiences relating to this thread, after working for a while I started to experience intermittent disconnect/timeout issues after being connected to Sirius for about 15-20 minutes.  At first I was told by Logitech that this was a Sirius issue, but again I did not experience the problems on my other devides (laptop or ipad).  

After having multiple conversations (Question Reference #110127-003157) with Logitech they ultimately resolved the problem in end of March with version 7.5.4.  This resolved the timeout issue and I have been using this version with no problems since then. 

About two weeks ago (mid-July) I was prompted for a new update (7.6.0) on the squeezebox which was downloaded and installed. Immediately I started to experience the timeouts when listening to Sirius.  The timeouts would typically occur around 15 minutes but sometimes could be as low as 5 mins.  

I opened a new ticket (110812-003729(with logitech and the first response I was told was to revert back to version 7.5.4 which appeared to work.  However I pointed out tha this was not a resolution since it would lock me into that version and I would be able to get future features or bugs fixed.  I was then told it was the Sirius issue, however I pointed out that I do not have that issue on other devices using Sirius via internet, and more importantly that the problem was previously resolved in version 7.5.4.   

Yesterday (8/18/2011) I had made no changes to my squeezebox and was listening to sirius, I experience no issues and more importantly the 15 minute timeout was gone.  I abled to listen to Sirius for more than 90 minutes. However today, it's back to the timeout issue.  

Not sure if something was changed yeterday, but today it's almost worst with the timeout being every 5-10 minutes.  Posted updated on Logitech. 

Again the timeout only appears to be on the squeebox.         

Gerry

 == Auto-comment from SVN commit #10834 to the network repo by agrundman ==
 == http://svn.slimdevices.com/network?view=revision&revision=10834 ==

Fixed bug 17157, rewrote the way we store persistent Sirius device info

(In reply to comment #62)
> == Auto-comment from SVN commit #10834 to the network repo by agrundman ==
>  == http://svn.slimdevices.com/network?view=revision&revision=10834 ==
> 
> Fixed bug 17157, rewrote the way we store persistent Sirius device info

Not fixed .... still have the problem, 15 minutes of music = "You are no longer authorized to listen to this stream"

(In reply to comment #63)
> (In reply to comment #62)
> > == Auto-comment from SVN commit #10834 to the network repo by agrundman ==
> >  == http://svn.slimdevices.com/network?view=revision&revision=10834 ==
> > 
> > Fixed bug 17157, rewrote the way we store persistent Sirius device info
> 
> Not fixed .... still have the problem, 15 minutes of music = "You are no longer
> authorized to listen to this stream"

Nevermind, had to reset my unit but afterwards seems to work good.

Thanks for the fix!

Comment 62 says the problem was fixed, but the link provided (http://svn.slimdevices.com/network?view=revision&revision=10834) gives "The webpage cannot be found".  Can someone post information on how to get and install this fix?

(In reply to comment #65)
> Comment 62 says the problem was fixed, but the link provided
> (http://svn.slimdevices.com/network?view=revision&revision=10834) gives "The
> webpage cannot be found".  Can someone post information on how to get and
> install this fix?

The fix is internal, upstream at SB, whether you are using SBS or MySB.com.  I tested it a bit this morning, and it seemed to work, including appropriately showing 'you are no longer authorized' after I logged on to Sirius from Android.

Thanks, Andy!

Many thanks Andy!  It's such a pleasure to be able to listen to XM without the constant interruptions.  I have to give a lot of credit to Logitech for listening to its customers and allocating the resources to fix this problem.

Thank you so much!

It seems that it may be back.

over this past weekend I have noticed the "you are no longer  authorized to listen" error has returned.  anyone else notice this? fix coming? hopefully!!

I've noticed it twice in the last few days.

Issue isn't resolved.  Still getting You are no longer authorized to listen.

I got this error this morning after 1 minute of listening.

I had it happen to me this morning, within the first few minutes of playback.

is Andy working on a fix?  any update. my 3 squeezebox devices are all experiencing this issue again. def has returned.

Yes, it's definitely back -- worse than the before.  Approximately every 2 minutes I get the error.  I hit play again, get the error after 2 minutes - I repeated this about 5 times then gave up.  I also hit the reset button after the first couple of errors.

Yes, the problem has returned. :(

Well, unfortunately the stoppages continue and in spite of a Sirius Internet Radio paid subscription, the dreaded message "stream stopped; You are no longer authorized to listen"! I feel like I ran a red light or something. After continuously paying my subscription fee I do not think this is fair. The service is endorsed by Logotech and Sirius endorses Logitech.

I try to listen to Sirius Services on SBS and until just yesterday I thought the bug (#17157) was fixed. 
 The Sirius stations were very stable with beta 7.6.2 r33340. I tried to go back from the latest nightly(r33449) to r33340 but it would not download.

AndyG worked on this bug and it was supposedly fixed, but it is back. It is dissapointing and very frustrating. I'm sure AndyG must be also. 
Could anyone please help. Thank you.

As a voter for this bug resolution I have been following the most recent comments about it's return. Contrary to those posting renewed problems, I have not experience a reoccurrence of this issue. I did indeed experience this problem before the fix went in last month - it has not returned for me. I am running Squeezebox Server Version: 7.6.1 - r33110. Perhaps the current problems have a different cause. - Rob

I too updated a few weeks ago (7.6.1 - r33110) after this fix and it seemed 100% resolved, however, about a week or so ago I began experiencing a sort of in-between aspect of this bug.  I now again get the "you are no longer authorized" after about 10 minutes, but pressing the play button plows through it and so far the message doesn't come back again.

Maybe I jumped to conclusions.  Seems to be better now. Thanks. (I just get so disappointed when I see that unkind message) Sorry about the knee-jerk reaction.

Though I got the error regularly earlier in the week, I enjoyed interruption-free listening this weekend.  

Squeezebox Touch running 7.6.1 r9486