"Content couldn't be loaded Internal Server Error" or "Remote Service Error - Internal Server Error".

Answered
Tom LaCorte

I've owned the NODE for about a week. Amazon music although not perfect was working fine, could access all content for the most part. As of last night when I try to load a requested album or artist or song I get,  "Content couldn't be loaded Internal Server Error" or "Remote Service  Error - Internal Server Error". Playlists  and all other content available is fine, just when I request artist or albums is the issue. I've rebooted the Node and router, signed out and back in on Amazon, still same issue. I am connected by ethernet cable. I was really liking this, hate to have to return and find a different option.

2

Comments

8 comments

Date Votes
  • Official comment
    Tony W.
    Product Support Manager

    Hi Tom

    The Remote Service Error you are receiving indicates an issue with the source music service. Please reach out to Amazon to ensure all is well on their end. Thanks for understanding.

  • Alan Wright
    • Edited

    Having the exact same problem, whenever I try and search for something. Anything in "My Music", I can access and play ok. I think there was a similar issue a few months back, which, iirc, was down to some compatibility issue with a new Bluos update, and Amazon's servers. Was fixed in about a week or so, I think. I'd say to hold tight, before returning. Based on the previous instance, it should be sorted sooner, rather than later.

    0
  • Tom LaCorte

    Ah, words of encouragement. I'm racking my brains out thinking what changed from one day to another that brought this issue on. 

    Thanks

    Tom

    1
  • Kris Whitman

    Exact same issue here. Playlists work fine just cannot search!

    1
  • Steve welch

    I am having the same issue, cannot search for tracks from Amazon music. Saying content cannot be loaded internal server error.

    1
  • Ta-Chen Wang

    Yes, I also have exactly the same issue. Like Alan said, it happened some time last year and the issue was fixed in a few days. What’s interesting this time is that the search works for certain, albeit small number of, artists. Hope it gets resolved soon.

    1
  • Joerg Sauer
    • Edited

    This is ridiculous - Bluesound asking their customers to reach out to Amazon when Amazon Music itself is working perfectly, as anyone here can confirm by simply using the Amazon Music app. The only thing not working here is Bluesound's Amazon Music integration, because the only situation in which Amazon Music exhibits a problem is when we are trying to access it via Bluesound's software.

    Is it possible that Amazon changed something on their side? Sure. But most likely not something that is in violation of their API spec or SLA.

    0
  • Tony W.
    Product Support Manager

    Hi Joerg

    Thanks for your patience and understanding, unfortunately, the issue is in fact happening at Amazon's end when you search for content rather than browse it, as confirmed by our contacts at Amazon. No changes were made to BluOS when the issue started to appear.

    Please follow this thread for updates on the situation; https://support1.bluesound.com/hc/en-us/community/posts/13013006304279 

    0

Post is closed for comments.

Didn't find what you were looking for?

New post