[GH-ISSUE #89] [Bug Report] OAuth Server Over SSH #78

New issue

Closed

opened 2026-02-27 04:57:24 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 04:57:24 +03:00

Owner

Originally created by @mauricehoutman on GitHub (Sep 28, 2025).
Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/89

Originally assigned to: @Googolplexed0 on GitHub.

Zotify Version
v0.9.21

Bug Description
Seems like I'm not able to login. Login in with credentials redericts back to a blank page. Changing the IP to my debian machine doesn't work. Not sure if it's caused since I'm trying to run this on a different machine over SSH. Worked perfectly a few weeks ago.

Originally created by @mauricehoutman on GitHub (Sep 28, 2025). Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/89 Originally assigned to: @Googolplexed0 on GitHub. **Zotify Version** v0.9.21 **Bug Description** Seems like I'm not able to login. Login in with credentials redericts back to a blank page. Changing the IP to my debian machine doesn't work. Not sure if it's caused since I'm trying to run this on a different machine over SSH. Worked perfectly a few weeks ago. <a href="https://ibb.co/pv6p54Jn"><img src="https://i.ibb.co/GvfjNCcF/Foto-28-09-2025-om-10-32.png" alt="Foto-28-09-2025-om-10-32" border="0" /></a>

kerem

2026-02-27 04:57:24 +03:00

closed this issue
added the
bug

question
labels

kerem commented

2026-02-27 04:57:25 +03:00

Author

Owner

@Googolplexed0 commented on GitHub (Oct 1, 2025):

Changing the IP to my debian machine doesn't work.

You need to have the SSH machine's address (192.168.2.13) set for the REDIRECT_ADDRESS config. This will make sure the OAuth server is listening for the response of SSH and will automatically set the URL correctly.

If you try this and it still doesn't work, try changing the binding address in librespot's OAuth implementation (librespot/oauth.py, line 106) to

("" , url.port)

If that still doesn't fix it, then I will need to do more digging.

@Googolplexed0 commented on GitHub (Oct 1, 2025): > Changing the IP to my debian machine doesn't work. You need to have the SSH machine's address (`192.168.2.13`) set for the `REDIRECT_ADDRESS` config. This will make sure the OAuth server is listening for the response of SSH and will automatically set the URL correctly. If you try this and it still doesn't work, try changing the binding address in librespot's OAuth implementation (`librespot/oauth.py`, line 106) to ``` ("" , url.port) ``` If _that_ still doesn't fix it, then I will need to do more digging.

kerem commented

2026-02-27 04:57:25 +03:00

Author

Owner

@mauricehoutman commented on GitHub (Oct 3, 2025):

I'm able to login, altough it looks like Librespot is having issues. Unable to find the oauth.py on my machine.

CRITICAL:Librespot:AudioKeyManager:Audio key error, code: 1
CRITICAL:Librespot:AudioKeyManager:Audio key error, code: 1

ERROR: FAILED TO FETCH AUDIO KEY

MAY BE CAUSED BY RATE LIMITS - CONSIDER INCREASING BULK_WAIT_TIME

GID: c3445bade50d4323b89d812a807ae854 - File_ID: 7638c190ab7c7ea0d581cd9ab495c2d8392234ef

ERROR: SKIPPING SONG - FAILED TO GET CONTENT STREAM

Track_ID: 5WsK63Cre8ixhuZWEUnWYs

@mauricehoutman commented on GitHub (Oct 3, 2025): I'm able to login, altough it looks like Librespot is having issues. Unable to find the oauth.py on my machine. > CRITICAL:Librespot:AudioKeyManager:Audio key error, code: 1 > CRITICAL:Librespot:AudioKeyManager:Audio key error, code: 1 > ### ERROR: FAILED TO FETCH AUDIO KEY ### > ### MAY BE CAUSED BY RATE LIMITS - CONSIDER INCREASING `BULK_WAIT_TIME` ### > ### GID: c3445bade50d4323b89d812a807ae854 - File_ID: 7638c190ab7c7ea0d581cd9ab495c2d8392234ef ### > > ### ERROR: SKIPPING SONG - FAILED TO GET CONTENT STREAM ### > ### Track_ID: 5WsK63Cre8ixhuZWEUnWYs ###

kerem commented

2026-02-27 04:57:25 +03:00

Author

Owner

@Googolplexed0 commented on GitHub (Oct 9, 2025):

This second error is a duplicate of #86.

@Googolplexed0 commented on GitHub (Oct 9, 2025): This second error is a duplicate of #86.

kerem commented

2026-02-27 04:57:25 +03:00

Author

Owner

@cdlenfert commented on GitHub (Oct 28, 2025):

Sorry to open this back up but I'm also unable to log in on a new instance on a headless server. When I add REDIRECT_ADDRESS and my server LAN IP to my confg.json file, I get INVALID_CLIENT: Invalid redirect URI when I paste the address from terminal to my browser. When I use the default the redirect is to 127.0.0.1 after authenticating and if I manually change that to my server's lan IP 10.1.10.188, and reload the address in my browser, it doesn't authenticate.

@cdlenfert commented on GitHub (Oct 28, 2025): Sorry to open this back up but I'm also unable to log in on a new instance on a headless server. When I add REDIRECT_ADDRESS and my server LAN IP to my confg.json file, I get `INVALID_CLIENT: Invalid redirect URI` when I paste the address from terminal to my browser. When I use the default the redirect is to 127.0.0.1 after authenticating and if I manually change that to my server's lan IP 10.1.10.188, and reload the address in my browser, it doesn't authenticate.