Issues with Spotify Authorization Flow

[fl3usner]

Hi,

I'm not sure if this is the right place to ask, so please let me know if it isn't.

I'm having trouble with the Spotify authorization flow. I can approve the access request, but I get stuck at the Music Assistant OAuth redirect. Clicking "Complete Authentication" results in a 401 error.

Has anyone experienced this issue before and found a solution?

Thanks in advance!

[OzGav]

Are you trying to connect with a firewall or across a VLAN or anything like that?

[fl3usner]

I’m only using the default firewall provided by my router, which hasn’t caused any issues in the past. I integrated my SoundCloud account without any problems about an hour ago.

The only thing that came to mind a few minutes ago is that my Pi-hole might be the issue. However, even after temporarily disabling it, I still couldn’t complete the auth flow.

[OzGav]

I just tried it on my test instance and it worked fine. Are you using HAOS? Can you look carefully at the URL on the 401 page for clues. Is there anything in the MA logs?

[fl3usner]

Yes, I'm running an HAOS on my proxmox homeserver.

There is nothing within the MA logs.
For the auth flow I receive a 200 OK response, followed by an 301 Moved Permanently
And as soon as I click on the "Complete Auth" - link I receive the 401.

I've attached some screenshots in case it helps.

Oh an btw, thank you very much for your time & efforts on this case! :-)

[OzGav]

Please confirm 192.168.178.57 is the IP of your MA server?

[fl3usner]

It is!

[bjorne]

Having the same issue. Getting a 401 on http://192.168.10.22:8123/api/hassio_ingress/... which is the correct internal address. (HA 2025.5.3)

[Hannnes1]

Had the same issue on the latest beta version. It works on stable for me though.

[OzGav]

Can everyone try exposing the web server on port 8095 and then try again when accessing MA through that

[fl3usner]

That worked just fine, thanks! I was able to add Spotify as a music provider within the exposed web server.

[OzGav]

Ok we will have a look at what is going on with ingress

[richheitech]

Same issue for me - 401 error. Tried both from HA and direct with port 8095. I'm also using Beta version 2.6.0b8

[OzGav]

I have created an issue from this discussion. It will be looked at soon.

[NicusorFlorinBaluta]

I have the same issue, and the 8095 port is exposed but it still doesn't work

any workaround available while the issue is being fixed?

[mhoogenbosch]

Exposing the webserver doens't help for me either. I removed the Beta and installed the stable, that works immediately.

[Concepcionsmall]

i had this problem before, it was because of my spotify app, i tried uninstalling and redownloading it from https://seruapk.com/spotify, it worked fine.

[Dzsonzii]

Chiming in, stable works perfectly fine, but beta doesn't. Port is exposed, and after connecting spotify from the stable version, I deleted the app from spotify, so there aren't any remains.

[Ay1tsMe]

I have mine set in configurations.yml:

# Access URL's
homeassistant:
  external_url: "https://redacted:8123"
  internal_url: "http://10.1.1.176:8123"

[OzGav]

The HA URL is not used in this case. Please try a different browser or incognito mode to rule out caching issues.

[Ay1tsMe]

Definitely not caching. I tried logging in on 3 different devices and they all showed the same behaviour

[OzGav]

OK we are having trouble working out why the redirect is returning there if you started with the IP. Please think carefully about whether you have something on your network that would be redirecting the traffic

[maxi1134]

OK we are having trouble working out why the redirect is returning there if you started with the IP. Please think carefully about whether you have something on your network that would be redirecting the traffic

I get this issue as well! It started sometimes in the last week

[xentara2]

After enabling the web port, make sure to restart the Music Assistant add-on. Before the restart, you’ll be able to access Music Assistant through the new port, but authentication won’t work yet. Once you restart the add-on, accessing it via the enabled port will allow authentication to function correctly.

[Ay1tsMe]

This. Restarting the add-on seemed to fix it. Was able to authenticate with the local IP. Can't believe a simple restart was the fix. Sorry for the lengthy discussion.

[mhoogenbosch]

Spot on... for me the exact same. After restarting the addon it immediately authenticated.

Such a rookie mistake, my bad!