Alexa Wont Play Music but Other Things Work: How to Fix It
Quick Answer
When Alexa can answer questions and control smart home devices but won’t play music, the most common cause is a broken authorization link to your music service. In plain terms: Alexa is still hearing you and getting basic answers from Amazon, but it no longer has permission to access your Spotify/Apple Music/Amazon Music account the way it did before.
The highest-impact fixes are to confirm which music service Alexa is trying to use, then disable and re-enable (re-link) that music service in the Alexa app. After relinking, set the service as the default again and test with a very specific request like, “Alexa, play music on Amazon Music” (or your chosen service) to avoid ambiguity.
Why This Happens
Alexa’s “general brain” (voice recognition, basic Q&A, timers, weather) can keep working even when music fails, because music playback depends on separate permissions and account tokens for each music provider. Those tokens can expire, be revoked, or stop matching your current account state. When that happens, Alexa may respond with messages like “I’m having trouble playing that,” “To play music, link your account,” or it may act like it’s playing but stay silent.
Here are the most common, tightly related causes:
1) The music service token expired or was revoked. This is common after a password change, security update, or logging out of the music app on your phone. Alexa can still do basic tasks because those don’t require the third-party token.
2) The default music service changed or became unavailable. If your default was set to a service that’s no longer linked (or your subscription lapsed), Alexa may keep trying that service even if another service is linked.
3) Multiple Amazon accounts or profiles are involved. If your Echo is registered to one Amazon account but your music subscription is on another (or you recently switched “Alexa Voice Profiles”), Alexa may be authenticated for voice features but not for the music entitlement you expect.
4) The music service is linked, but permissions were denied during sign-in. It’s easy to tap through an authorization screen and accidentally decline a permission request. Alexa will show the service as present, but playback fails because the provider never granted access.
5) An overlooked technical cause: the provider’s region or account type doesn’t match the device/account region. If your Amazon account region changed, you moved countries, or the music service account is registered in a different region, linking can appear successful but playback requests fail or return limited catalogs.
Real-world scenario: After a power outage, your router comes back quickly but your phone reconnects to a different saved network (or your mesh system re-optimizes). You open the Alexa app and it still controls lights, so you assume everything is fine. But your music service had a security prompt after the outage (or after the provider detected a “new login”), which invalidated Alexa’s token. Music stops, while basic Alexa features keep working.
Common user mistake: Saying “Alexa, play music” without specifying the service, then troubleshooting the wrong thing. If Alexa’s default service is broken, that generic request will always fail even though another linked service would work if you name it directly.
Step-by-Step Fix
Confirm the symptom points to authorization (not audio volume or “Do Not Disturb”).
What to do: Ask: “Alexa, what’s the volume?” then “Alexa, set volume to 5.” Next ask: “Alexa, play music on Amazon Music” (or “on Spotify,” etc.).
What the result means: If volume changes and Alexa speaks normally but music still won’t start (or errors out), the device audio hardware is fine and the issue is likely service authorization, default service selection, or account entitlement.
What to try next if it fails: If Alexa doesn’t speak clearly or volume won’t change, fix audio/Do Not Disturb first in the Alexa app, then return to the steps below.
Check which music service Alexa is trying to use (and whether it’s still linked).
What to do: Open the Alexa app > More > Settings > Music & Podcasts. Look at Default Services and the list of linked services.
What the result means: If the default service is set to a provider you don’t use anymore, or it shows as not linked, Alexa will keep failing on generic “play music” requests.
What to try next if it fails: If the app won’t load Music & Podcasts or shows errors, switch your phone to cellular data temporarily and try again. If it loads on cellular, your home network may be blocking parts of the sign-in flow (see Advanced Troubleshooting).
Disable and re-enable the music service link (refresh the authorization token).
What to do: In Music & Podcasts, select the problematic service. Choose Disable Skill or Unlink Account (wording varies), then link it again and complete the provider sign-in. Approve all requested permissions.
What the result means: This forces a new authorization token and corrects the most common “everything works except music” cases.
What to try next if it fails: If linking fails or loops back to sign-in, confirm you can log into the music service directly in its own app/browser first. If you can’t, fix the provider account (password, subscription, verification) before trying again in Alexa.
Set the default music service again (don’t assume it stayed set).
What to do: Alexa app > Settings > Music & Podcasts > Default Services. Set your preferred provider for Music and, if you use it, Artist and Genre Stations.
What the result means: If the default was pointing at a broken or unlinked provider, this fixes the “Alexa won’t play music” problem immediately for generic requests.
What to try next if it fails: If the default won’t “stick,” you may be signed into the Alexa app with a different Amazon account than the Echo device is registered to. Continue to the next step.
Verify the Echo device and the Alexa app are on the same Amazon account.
What to do: Alexa app > Devices > select your Echo > Device Settings. Check the registered account (often shown under device details). Also check Alexa app > More > Settings > Your Profile (and household profiles if used).
What the result means: If the Echo is registered to Account A but you’re linking music services in the app while signed into Account B, the link won’t apply to the device you’re talking to.
What to try next if it fails: Sign out of the Alexa app and sign back in with the Amazon account that owns the Echo. Then repeat the relink and default-service steps.
Run a quick entitlement test by naming the service and content type.
What to do: Try three commands: “Alexa, play a playlist on Spotify,” “Alexa, play a radio station on Amazon Music,” and “Alexa, play artist name on service name.”
What the result means: If one service works when named but “play music” fails, your default service is still misconfigured. If all named services fail, the issue is likely account authorization, subscription status, or a network restriction affecting sign-in/playback endpoints.
What to try next if it fails: Move on to Advanced Troubleshooting, focusing on account/cloud checks first.
Practical network sanity test: use a temporary mobile hotspot for one playback attempt.
What to do: Create a hotspot on your phone. In the Alexa app, update the Echo’s Wi-Fi to join the hotspot (Device Settings > Wi-Fi Network > Change). Then ask Alexa to play music from the same service.
What the result means: If music works on the hotspot, your home network is interfering with the authorization or streaming connection (often DNS filtering, router security features, or a mesh setting). If it still fails on the hotspot, the problem is more likely the account link/subscription/provider side.
What to try next if it fails: If hotspot works, revert the Echo back to home Wi-Fi and use the network-related items in Advanced Troubleshooting. If hotspot doesn’t help, focus on account and permissions.
Advanced Troubleshooting
Account and cloud issues (most relevant to this problem)
Provider subscription or plan limitations: Some accounts allow limited device types or require a premium plan for voice-controlled playback on speakers. If Alexa suddenly says you need an upgrade (or plays previews only), check your music provider account status directly. If the provider recently changed plan rules or you changed plans, relinking in Alexa is often required.
Security verification holds: If your music provider flagged a login as suspicious, it may require email or SMS verification. Complete that verification in the provider’s own app or website first, then unlink/relink in Alexa to refresh the token.
Amazon Household/profile confusion: In a household, Alexa may respond to different people’s profiles. If one person’s profile has the music service linked and another doesn’t, music can work sometimes and fail other times. Standardize by linking the service on the account that owns the Echo, and be cautious with voice profile switching while testing.
Network-related issues (only where they affect authorization or streaming)
DNS or content filtering: Some routers and “family safety” DNS settings block the authorization redirect or streaming domains. Symptoms include linking loops, “something went wrong” during sign-in, or music that starts then stops. As a test, set your router’s DNS back to automatic/default temporarily, or disable filtering features briefly, then relink the service.
Mesh Wi-Fi band steering edge case: Band steering usually isn’t the root cause, but it can interfere with sign-in flows if the phone and Echo bounce between nodes during setup. If relinking fails repeatedly, try standing near the main router node, temporarily pausing extra mesh nodes (if your system allows), then relink again.
Firmware and software causes
Stuck service state after an update: Occasionally, an Echo or the Alexa app gets into a state where the service appears linked but playback calls fail. Check for updates: keep the Alexa app updated, and for the Echo, you can say “Alexa, check for software updates.” After an update, wait a few minutes and retry playback.
Alexa app cache/session issues: If the Alexa app keeps showing the service as linked but relinking doesn’t change anything, force-close the Alexa app, reopen it, and try again. If the sign-in page is blank or won’t load, try a different browser on your phone for the provider login step.
Configuration conflicts
Routines and “preferred speaker” settings: If you have a routine that triggers music on a specific speaker group, or a preferred speaker set to a device that’s offline, Alexa may accept the request but fail to play where you expect. Test by explicitly naming the device: “Alexa, play jazz on Echo Kitchen.” Then check Alexa app > Devices > Groups and confirm the target speaker is online.
Explicit filter and content restrictions: If music fails only for certain songs or artists, check Alexa app > Settings > Music & Podcasts and any content filters within the music provider account. This won’t usually block all music, but it can look like “music is broken” if your common requests are filtered.
When to Reset or Replace the Device
Try a soft restart first if: the music service is correctly linked, your subscription is active, and music still won’t play after relinking and setting defaults. A restart clears temporary states that can block playback without changing your settings. Use the Alexa app to restart the device (Device Settings > Restart) or unplug it for about 30 seconds, then plug it back in and wait for it to fully reconnect before testing.
Factory reset only if: (1) you confirmed the correct Amazon account is used, (2) you successfully linked the music service, (3) music still fails on a hotspot, and (4) other Alexa features work normally. A factory reset is a last resort to clear corrupted local configuration.
What you lose with a factory reset: The Echo will be removed from your account until you set it up again. You’ll need to reconnect it to Wi-Fi, re-add it to speaker groups, reapply room/group assignments, and reconfigure device-specific settings (like preferred speaker, alarms stored on the device, and some routine targets).
Safety note: If the device is unusually hot, shuts off repeatedly, makes crackling sounds, or you notice a burning smell, stop using it and unplug it. Do not attempt to open the device or repair internal parts.
How to Prevent This in the Future
Keep account changes coordinated: If you change your music service password, enable two-factor authentication, or switch plans, expect to relink the service in Alexa afterward. Doing it immediately prevents the “everything works except music” surprise later.
Be explicit when testing: When something seems off, test with “Play music on service name” rather than “play music.” This quickly tells you whether the default service or a specific provider link is the problem.
Minimize account mismatch: Keep the Echo registered to the Amazon account that owns the household’s music subscription, or be consistent about which account is responsible for linking services. In homes with multiple adults, decide who “owns” the Echo setup to avoid split links across profiles.
Keep the Alexa app updated: Service linking relies on secure sign-in pages and redirects that can fail on older app versions. Updating reduces relink problems and blank sign-in screens.
Plan mesh Wi-Fi for stability during setup: If you use mesh Wi-Fi, do linking and device setup near the main node when possible. This reduces failed authorization attempts caused by roaming during the sign-in process.
Review routines after changes: If you rename devices, change speaker groups, or remove old Echos, update routines that start music so Alexa isn’t trying to play on a device that no longer exists or is offline.
FAQ
Why does Alexa answer questions but say it can’t play music?
Because music playback requires a separate authorization link to your music provider. Basic questions and timers use Amazon’s services and can keep working even when the music provider token has expired or been revoked. Relinking the music service usually fixes it.
If I can play music on my phone in the music app, doesn’t that prove the account is fine?
Not always. Your phone app can be logged in and working while Alexa’s link token is expired, tied to a different account, or missing permissions. Phone playback proves the provider is up and your credentials work somewhere, but it doesn’t confirm Alexa is authorized.
Do I need to reset the Echo to fix music playback?
Usually no. Unlinking and relinking the music service, then setting it as the default again, resolves most cases. Resetting is only worth trying after you’ve confirmed the correct Amazon account, verified subscription status, and tested on a hotspot.
Why does “Alexa, play music” fail but “Alexa, play music on Spotify” works?
This almost always means your default music service is set to a different provider that is unlinked, restricted, or no longer subscribed. Set your working provider as the default in Alexa’s Music & Podcasts settings.
Is this a Wi-Fi problem if other Alexa features work?
It’s less likely, but still possible in a specific way: your network can allow basic Alexa traffic while interfering with the sign-in/authorization redirect or the streaming endpoints used for music. The hotspot test is the quickest way to separate “home network interference” from “account linking/authorization” issues.
After all the noise, it’s almost funny how straightforward it feels when the pieces finally fall into place. The urgency softens into something calmer, like the room after a long day—still real, just not so tense.
What lingers isn’t the spectacle, but the everyday friction that’s been quietly removed. No grand fireworks, just a steadier rhythm that makes the whole topic feel less heavy.
