"Internal server error" on Node 2i

Answered

Comments

9 comments

  • Official comment
    Avatar
    Seppi Evans

    Oswin reboot your router, then when it’s back up power-cycle your Vault. Amazon music has been having issues recently so you may want to try another streaming service (grab a free trial)

    Comment actions Permalink
  • Avatar
    Alain DW

    Sounds a lot like the the issue I had several times. ( https://support1.bluesound.com/hc/en-us/community/posts/4404558427543-failure-to-communicate-over-wifi)

    Probably some problem with the router  and/or DHCP. (assuming you are on wifi)

    Bluesound solution is to reboot everything in the chain, assign fixed ip addresses, check wifi spectrum for overlapping channels (if on wifi, how strong is your signal? see diagnostics).

    If this isn't helping, send a support request.

    0
    Comment actions Permalink
  • Avatar
    Oswin

    Ive had the same issue. I have the vault. It has been fine since I got it end of July. Started to have issues, connectivity, internal server issues from sunday night. Ive been streaming everyday since I got the system, so it has been fine.

    I find if you log out and log back into the music service (Im using Amazon HD), it works. But develops the issue again after a few songs. Really annoying! Im at a point now thinking of returning the system as its not really fit for purpose!

    0
    Comment actions Permalink
  • Avatar
    Davywhizz

    Thanks for the replies. I'm sorry, I don't think I was clear enough with the question. The problems I've had were with Amazon Music, so maybe that's the issue. Also, my Node is hard wired to the router so it's not a wifi problem.  This morning I've rebooted the Node after disconnecting the power, and also the router. Now I'll try using the BlueOS app. It may be a coincidence, but we had a fibre broadband upgrade yesterday, when the problem started, though it's the same router and I haven't had to re-enter passwords for wifi devices and no IP addresses have changed.

    0
    Comment actions Permalink
  • Avatar
    Seppi Evans

    A reboot is always a good start, Amazon Music is having issues but I am unsure what it is.

    0
    Comment actions Permalink
  • Avatar
    Oswin

    Have tried to reboot the router and power cycle etc. Problem still persists. Ive just got off the phone with the BluOs tech support team, they are going to investigate and come back to me by today.

    I think this is a connectivity issue while communicating with the external music service (amazon HD in this case). It definitely feels like the bluos system is trying to connect and fails midway. If you force it by logging out and log back in it works immediately. Then develops the fault again.

    Lets see what the support team can do. Certainly hope they can fix it with an update. Ive grown a bit attached to this streamer and dont want to change if I can help it :(

     

    0
    Comment actions Permalink
  • Avatar
    Davywhizz

    Just to say my Node has been fine today. Maybe it was an Amazon problem and they've resolved it. Thanks again for the responses.

    0
    Comment actions Permalink
  • Avatar
    Oswin

    Good to hear Davywhizz. Mine is also working well since yesterday. I had feedback from the support team that it was something on the Amazon side. Looks like they re-booted their servers overnight ;) and fixed the issue!

    Anyway, glad my system is running well. I hate going via bluetooth or airplay, I feel Im losing quality if not streaming straight from the source.

    0
    Comment actions Permalink
  • Avatar
    SteveK

    Another Amazon HD subscriber here.
    Yesterday, I used my Node 2i for the first time in a few days
    I had the same "Error" problem. Seems to be fixed today.

    0
    Comment actions Permalink

Please sign in to leave a comment.