"Cannot access audio file: Forbidden" on new ISP

[rye]

So just today, I was switched from Comcast (if you care) to MetroNet.

Logging in to Pandora through pianobar works great, but once it autoselects the station and gets the new playlist, and then commences to try to play each track, it complains:

/!\ Cannot access audio file: Forbidden.

Now, I'm not sure what the issue is, here. One important thing to note is that it does not work to use a browser (which, after working in the background displays:)

We've encountered an error. Sorry, it's our fault.

I'm not sure as to what the issue is, here, nor if my new ISP has anything to do with it. Ideas?

[rye]

This issue is still an issue today.

[PromyLOPh]

If the website does not work for you either only Pandora’s support can help you/fix the problem.

[rye]

As of now, pianobar now functions properly without displaying this error.

[advaitkunte]

@PromyLOPh I am from India, using proxy in the config, running it on xubuntu 12.04 I am having the same issue, have the latest version (as of 2-Oct-2013) "/!\ Cannot access audio file: Forbidden." it plays for some time and after few hours of playing I get this issue. And the website says "We've encountered an error. Sorry, it's our fault." Also if I use a VPN (I tried vpnreactor) the same thing works (weird!) but through the proxy it doesnt If I login from another account it works fine on the website.

[rye]

I think it could possibly be something on the server-side, where they block unfamiliar IP addresses (or those out of their ranges). My IP address from my service provider changed, and it now works.

[philippwiddra]

I have the same problem from time to time, here in Germany. I use pianobar over a proxy, but when i get the "We've encountered an error. Sorry, it's our fault." error on desktop, i also get the same Forbidden one in pianobar. I'm pretty sure thats a serverside fault, but haven't found a fix or workaround (neither via google, nor via pandoras support).

[rye]

I'm pretty sure it's definitely a thing with IP addresses associated with accounts. I've used the same account multiple times this day from different networks, and I've just now, after returning to my home with the new ISP, started getting errors again.

[rye]

@philippwiddra I'm pretty sure it's a serverside fault as well; poking around indicates that the server is 403'ing, both in web and pianobar.

Unfortunately, that's not a pianobar fault, it's a Pandora fault.

[advaitkunte]

as I said earlier, if I use a VPN (vpnreactor) the same account at the same time works! But if I try the same over a proxy it doesnt and gives me this error

[PromyLOPh]

I believe my comment on #348 might be relevant: https://github.com/PromyLOPh/pianobar/issues/348#issuecomment-13609295

[philippwiddra]

I definitely will try using not only a control proxy next time i get this error. Thanks for the link.

[rye]

In my case, I'm not using a VPN or a proxy (at least, I'm not making a conscious effort to). I'll try making an alternate account for that to see if that works, and then try to figure out how I can get my other account back to normal (perhaps just letting it sit for a while will help (?)).

[advaitkunte]

@PromyLOPh https://github.com/PromyLOPh/pianobar/issues/348#issuecomment-13653473 this is exact problem that I am facing. I am using the proxy variable in my config file, will continue to for some more time and report back

[theDiverDK]

The error is back.

At least i am getting it 95% of the time i try to use Pianobar :-(

[PromyLOPh]

@theDiverDK: Is the web player working correctly?

[theDiverDK]

I can't use the pandora webplayer, due to IP restrictions, I am using a DNS proxy from Pianobar.

The version I am using is: 2013.05.19-win32

[PromyLOPh]

The version I am using is: 2013.05.19-win32 The windows version’s issue tracker is here: https://github.com/thedmd/pianobar-windows

[advaitkunte]

Got a Raspberry Pi recently and wanted to try this out and back to having the same problem :( http://pastebin.com/gVTynGVx I am not from US so using DNS redirection. It worked initially for an hour or so and then stated to get this error. And before this incident, have been using this account on my Android phone for more than a year without any issues EDIT 1: When I start to get this errors, I can't use Pandora on the web player or the Android app, I have to wait for a day or two for the error to go away and then I am able to use it on the web player or the android app. But as soon as I use pianobar, in an hour or so I start to get these errors and they continue for a day or two Let me know if in any way I can help you solve this issue

[PromyLOPh]

This is probably caused by the same access restrictions resulting in ads replacing tracks (see #415). I suppose you can’t use the web player/Android app, correct? You can ping Pandora’s support about this then, as they are usually able to unblock you.

[advaitkunte]

Yes I cant use the web player or the android app, it keeps changing the track infinitely. This issue only occurs roughly 1 hour of using of pianobar. This has never happened to me when using the web player or the android app. I can contact Pandora support but, this happens to me every time I use pianobar. I even created 3 new accounts just to check if even they have the same issue, and they do. If I may, I request you to use a VPN from a country where pandora isnt available and try running pianobar through this VPN and see if you are having the same issue. Funny thing is if I use VPN service from a country where Pandora is supported, it works, and as soon as I disconnect and back to using proxy, I get the forbidden error.

[josefson]

Just for your knowledge about this error. I was used to get this error to. 1- At first i tried to create new accounts to keep listening, but they detected it. -> did not work 2- Started searching for new proxies - here is a tricky observation: Even if my pandora account was somehow "blocked" with google chrome and media hint plugin, once i found a nice proxy i could listen to pandora again. So once i realized that i automatized the way i look for proxies and substitute them in pianobar config.

[TermeHansen]

I suffer from this behavior of pianobar/Pandora blocking me out after 1-2 hours of listening. I don't follow what you suggest to do Josefson. If my account is first blocked I get forbidden from any proxy for a couple of days until my account is "unflagged" again. Then I can listen to 1-2 hours again :( This is not usable...

[Ph1r3ph0x]

Why has this been closed? This is clearly a pianobar issue. I can use pandora with the proxmate addon for chromium without having any trouble at all. I don't even have to listen to ads (adblock). I have set the proxy + control_proxy to the server I extracted from my proxmate plugin. Login and listening works, but I get banned after some time (I guess the first time pandora tries to play an ad?) Any advice?

[PromyLOPh]

Why has this been closed? As you can see above the original reporter closed this issue, because it disappeared.

[advaitkunte]

I have been have this issue. No idea why it got closed On 04-Jun-2014 5:34 pm, "PromyLOPh" notifications@github.com wrote:

Why has this been closed? As you can see above the original reporter closed this issue, because it disappeared.

Reply to this email directly or view it on GitHub https://github.com/PromyLOPh/pianobar/issues/400#issuecomment-45082062.

[ubuntuslave]

This is not even solved by using a system-wise proxy (unless your local IP address is maintained constant, which is a rare case if you're switching hotspots). Maybe a VPN could help, but I haven't tested that yet. Logging under a different user account worked. I guess my other account got flagged or something (as mentioned before).

[josefson]

guys, in my experience i get a lot of those errors to, but it is until i find the right proxy(the ones pandora didn't detect and block yet.) In order to do that i use an automated script to crawl some site as hidemyass for new proxies and try to use one by one until i don't have this error message. So yes this is annoying, but it is not a pianobar issue.

[Ph1r3ph0x]

@josefson I don't think so since I use the exact same proxy, which works pretty well in chromium. Only had this problem with pianobar :(

[PromyLOPh]

@Ph1r3ph0x: The website uses a different API.