It looks like a handful of Amazon Alexa users have been having trouble getting their Alexa-equipped Echo speakers to play tracks from Pandora. The issue appears after a single track from any given station has finished playing, which then leads to a number of seconds of silence, and then finally Alexa saying “Sorry I’m having trouble playing the music”.
This is an issue that has been plaguing many users for an unknown number of months now. It appears that there has been no success on Amazon’s side to develop a solid answer just yet, so this has left many users taking to the web to find a solution, and little have had such luck. Until now, at least.
One Proven Solution
Thankfully, there is at least one answer that could solve this problem for a number of users who happen to be using “free” ad-supported Pandora accounts behind strong firewalls or network-wide ad-blocking solutions like Pi-Hole. This appears to be a common issue that is leading to this error and the solution is as simple as white-listing a single domain.
Although Amazon hasn’t come forth with any hard solutions, we were able to discuss this problem with one of Pandora’s team members who has been working diligently to resolves issues just like these, which helped bring us to this one solution.
If you are running a network-wide ad-blocking solution like Pi-Hole, then it is doing its job quite well, and it is also blocking ads from Pandora that try to pop up in between tracks. Despite this sounding like a “Sweet! No ads!” moment, those free Pandora accounts do require those ads in order for the service to work on the Echo speakers (and it helps cover the cost of those accounts and the profit to the artists you are listening to).
So you are going to want to whitelist the domain “delivery-cdn-cf.adswizz.com” on your ad-blocking solution. The same applies if you are using router hardware that features strong firewalls that may behave in a similar manner.
Although powerful ad-blocking solutions like this can be quite a tool for privacy, it can also hurt certain services that rely on this income to offer the services they do. So you have to weigh out what you really want in life. Free Pandora music, or make the sacrifice for a paid subscription (or find another solution). If you prefer the former, then you’ll have to put up with at least a few ads here and there. At least everything else on your network will still be blocked.
Of the issues users have run into, this is the only one we have been able to replicate ourselves, and white-listing the domain has resolved it in every observed case.
For Everyone Else
For those not being affected by ad-blocking or firewall solutions that could be prohibiting these ads from coming though, there could be something else to blame for your experience.
The trouble is likely on Amazon’s side and how the Echo speakers are communicating with Pandora. Especially since Pandora seems to work fine just about everywhere else (mobile apps, Google Assistant, and so on).
You can rest assured that Pandora seems to be working hard to resolve any potential problems that could involve anything on their end. As for Amazon, you are at their mercy if it falls on theirs.
You can find many conversations between Alexa users and Amazon as they try to troubleshoot the experience people are having. Most of which have led to some of the same troubleshooting techniques listed as followed:
- Cycle Power (router too) – Pull the power to your Echo speaker and plug it back in, forcing it into a fresh reboot. You may want to try rebooting your router too if it normally gives you connectivity issues over time.
- Ask Alexa to “check for updates”. Once it comes back online, ask Alexa to check for updates, just in case there are any new updates available. Alexa does this automatically on the backend, so you should almost always find that no new updates are currently available (but it’s worth a shot nonetheless).
- Drop the pandora account from your Alexa account via the app and re-add it. Pull up the Alexa app via your chosen mobile device, head over to Pandora, and sign the account out of Alexa. Once finished, add the account back to Alexa.
Some users have claimed these steps have helped them, while a majority of users claim the issue remains unchanged.
Others have thought that this might have something to do with the multi-room features within the speakers and have tried various techniques of adding speakers to groups and other related ideas to troubleshoot the issue with. However, this appears to be an older issue that was patched by Amazon. If there are any new problems arising that surround the multi-room features, then you will once again be at Amazon’s mercy for a fix.
Amazon has theorized that the issue could arise due to fluctuations in bandwidth. However, Judging by some of the responses around the web, we would say this is not the most common issue as most internet connections can handle music streaming at this point (not to say that there aren’t some users out there with weak internet connections that can affect music streaming).
Hopefully, if you run into this problem, you fall into the first group within this article and it can be resolved quickly. If not, then it will be a waiting process in hopes that Amazon will find a solution on their end.
Feel free to use the comments below to share your own experiences and possibly any steps you yourself have taken to find a solution (that may or may have not worked). Through community, you find many answers.




2 Comments
I have this problem pretty often on my original (1st-gen) Echo, but have no problems with newer devices.
It is quite an oddly random experience between users. For example, we have confirmed having this problem with gen 2 and 3 Echo devices.