Error: forbidden. Tidal: 132773053
Beantwortet
Lately I started to get this error sometimes when I return to Tidal in bluos, I often see it when I have a song paused for some time and then when I return later to resume playback I get an error saying: Forbidden. Tidal: 132773053
Then I click OK in the dialog box and then I can reload the song I was playing.
Any idea what this error is about?
-
Offizieller Kommentar
Hi Tom
Your connection to the TIDAL Server has timed out on the active stream. Clearing the error and restarting the song re-establishes an updated link to the server. This usually happens when pausing in the middle of a track when you are leaving the house or the phone rings.
I have passed this along to our QA Team for review and help make a better experience to have a better, softer landing from this error state.
Thanks for mentioning. It's how we make a better experience for all.
-
Thx, recently it started even when the song had not been paused for more than an hour or under. In the past I never saw this error and could have a song paused for hours or days without problems. It all started recently so it seems like something has changed. Thx for looking into this.
0 -
Hi,
I do have the same issue as reported here, and I'm also quite positive it is new.
Paul
0 -
Hi Paul
If the problem persists, please select Music Services, TIDAL and log out. Select Help, DIagnostics, Reboot. Once the Player returns to ready mode (a BLUE LED), select Music Services, TIDAL and log back in.
If it continues after that, please select Help, Send Support Request in the App for our Support Crew to take a closer look at your log file.
0 -
Like Paul says it's def. a new issue. I will try the steps suggested above.
0 -
I tried the steps above but here days after I still get this error often after playback has been paused for a while. Hopefully we will see a fix some day :)
0 -
I also tried the indicated steps, which did not work. Will try a support request.
0 -
Any updates regarding this ? I know I can just restart the song, just a bit annoying having to do that every time a song has been paused for a while. Hope you find a fix for this.
0 -
I have no news from my support request which I opened a week ago, maybe it's being looked into.
0 -
Hi Paul
We responded on Monday - please check your G-Mail Junk Folder0 -
Hi Tony,
That got lost yes, my bad.
They indicated to try the steps you provided here, to which we already replied it does not work. Will reply now.
0 -
Antknee Williamson I noticed something when I used the bluos desktop app on my windows 10 computer, and then started the music and later paused it for some hours, then when I started it again through the app on my computer it didnt give the error like it always does when I do it on my ipad. Will keep an eye on itt and see if the error also appears when using the app on computer.
0 -
Update: I wrote in my last post that it didnt happen when I use the bluos app on my computer but seems I was wrong, im getting the error here also. Just an update to let you know.
0 -
I finally got a positive answer from support as they successfully replicated our issue.
They will be "looking into this further, with the intention to provide a fix for this issue in a future firmware update."
The problem is constantly there for me, and although it is not critical, it's a bit annoying.
0 -
Thanks for letting me know Covered and yes though not critical it's very annoying, happens often even when only beeing paused for a couple of hours. Let's hope they find a fix for this :)
0 -
Im still getting this error daily, wonder if they are still working on a fix ?
0 -
I have no idea.
All I know is I'm still getting it, and the more they update the more new bugs I get.
On top of that now, I'm sometimes getting non-responsive apps (inputs do not control the node anymore), or wrong info showing (wrong track for example), or yet inability to change the played track. For all those to go I have to restart the app.
0 -
Shame that there is so many bugs after each update, I really hope they fix it but so far it doesnt like it.
0 -
This error is an error that your account cannot connect to TIDAL and not a software bug.
If you have logged out of TIDAL and restarted your player and logged back in, please contact TIDAL to ensure your account is in good standing.
0 -
My account is in good standing, I have no issue at all with the Tidal app for example.
Again, the signature of the error is: pause a track, idle for a while, hit resume, the error pops, hit "OK" and resume again, and the track starts from the beginning.
Clearly the SW can relog since it does it fine on the second try, while on the first try it pops the error. Why couldn't the process performed on the second try be performed on the first without losing the paused position information?
0 -
Plus what happened to support saying they successfully replicated the issue, while now you're saying it's a Tidal account problem? (my post from 2 months ago)
0 -
Yeah it's def. not a problem with Tidal and our accounts being in bad standing, and in the past I didnt have this error. And seeing that others have the same error it must be relatated to bluos somehow. I asked a friend of mine who also use Tidal with bluos and he gets these errors also. Plus support told (Covered) that they were able to replicate the error so .... :)
0 -
The issue was resolved by TIDAL resolving an outage on their server end as nothing changed in the software. Please reach out to TIDAL Support.
0 -
Okay thx Tony W. I will try contact Tidal support. Thx again.
0 -
I also did, and got the problem fixed finally!
HowTo:
1. Log out from your Tidal account on BluOS
2. Reset your Tidal password
3. Relog on BluOS by updating your info
Thanks for the help :)1 -
So changing password and re-login is fxing the issue? Was it Tidal who told you to try this or? Seems strange that a password change would fix this but im gonna try and let you know if it worked thx :)
0 -
Okay so I tried this but it didnt work, still getting the error forbidden. I will try contact Tidal support chat on monday.
0 -
Hey all, it seems now that it has finally been fixed, or so I think, I havent gotten any errors the last few days, so I think it might have been fixed with one of the recent updates to the player. Just an update to let you know :)
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
28 Kommentare