starred/spotify-tui

Fork 0

mirror of https://github.com/Rigellute/spotify-tui.git synced 2026-04-26 16:15:55 +03:00

[GH-ISSUE #669] Cannot install: `Error: Address already in use (os error 48)` #273

New issue

Closed

opened 2026-02-28 14:48:10 +03:00 by kerem · 5 comments

kerem commented

2026-02-28 14:48:10 +03:00

Owner

Originally created by @CaspianA1 on GitHub (Nov 30, 2020).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/669

I get this error when trying to configure it via spt:

$ spt
Error: Address already in use (os error 48)
Starting webserver failed. Continuing with manual authentication

From there it tries to open a very large Spotify link: Opened https://accounts.spotify.com/authorize ...

This page hangs and does nothing. For each time I uninstall spotify-tui this link works once (by asking me to confirm a lot of permissions regarding what spt can do). After I click accept then that page hangs as well.

This is so frustrating - Does anyone know what I am doing wrong?

Originally created by @CaspianA1 on GitHub (Nov 30, 2020). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/669 I get this error when trying to configure it via `spt`: ``` $ spt Error: Address already in use (os error 48) Starting webserver failed. Continuing with manual authentication ``` From there it tries to open a very large Spotify link: `Opened https://accounts.spotify.com/authorize` ... This page hangs and does nothing. For each time I uninstall `spotify-tui` this link works once (by asking me to confirm a lot of permissions regarding what `spt` can do). After I click `accept` then that page hangs as well. This is so frustrating - Does anyone know what I am doing wrong?

kerem closed this issue

2026-02-28 14:48:10 +03:00

kerem commented

2026-02-28 14:48:11 +03:00

Author

Owner

@Seltonu commented on GitHub (Dec 24, 2020):

The exact same thing happens to me, except the error says "os error 98" instead of 48. But huge link, page hang, all of it.

I've put in my client ID, client secret, and edited the spotify dashboard app to use "http://localhost:8888/callback" as a redirect URI.

@Seltonu commented on GitHub (Dec 24, 2020): The exact same thing happens to me, except the error says "os error 98" instead of 48. But huge link, page hang, all of it. I've put in my client ID, client secret, and edited the spotify dashboard app to use "http://localhost:8888/callback" as a redirect URI.

kerem commented

2026-02-28 14:48:11 +03:00

Author

Owner

@OrangeFran commented on GitHub (Dec 29, 2020):

You can try to change your port, I don't know if it helps though. Normally these address already in use messages appear if a process is already using the port, in this case 8888. To investigate, maybe have a look at netstat -l to see all listening processes or even lsof -i :8888 to look at the port and see which processes are using it. I hope this helps. These commands definetely work on macOS and probably on linux too.

If you want to try changing the port, change the callback url to something like: http://localhost:5555/callback and enter 5555 when spt is asking you for the port.

@OrangeFran commented on GitHub (Dec 29, 2020): You can try to change your port, I don't know if it helps though. Normally these `address already in use` messages appear if a process is already using the port, in this case `8888`. To investigate, maybe have a look at `netstat -l` to see all listening processes or even `lsof -i :8888` to look at the port and see which processes are using it. I hope this helps. These commands definetely work on macOS and probably on linux too. If you want to try changing the port, change the callback url to something like: `http://localhost:5555/callback` and enter `5555` when spt is asking you for the port.

kerem commented

2026-02-28 14:48:11 +03:00

Author

Owner

@CaspianA1 commented on GitHub (Dec 29, 2020):

I'll try that out.

@CaspianA1 commented on GitHub (Dec 29, 2020): I'll try that out.

kerem commented

2026-02-28 14:48:11 +03:00

Author

Owner

@CaspianA1 commented on GitHub (Dec 29, 2020):

Thank you, changing the port resolved my problem.

@CaspianA1 commented on GitHub (Dec 29, 2020): Thank you, changing the port resolved my problem.

kerem commented

2026-02-28 14:48:11 +03:00

Author

Owner

@Seltonu commented on GitHub (Dec 29, 2020):

Just commenting to also add it works for me too now, I was going to test a different port as you mentioned but before doing that I tried "lsof -i :8888" and saw nothing was using the port so I went with the default 8888 and it worked. Must've been as you say, some program was using the port and restarting my PC must've cleared it at some point. Thank you!

@Seltonu commented on GitHub (Dec 29, 2020): Just commenting to also add it works for me too now, I was going to test a different port as you mentioned but before doing that I tried "lsof -i :8888" and saw nothing was using the port so I went with the default 8888 and it worked. Must've been as you say, some program was using the port and restarting my PC must've cleared it at some point. Thank you!

kerem referenced this issue

2026-02-28 14:53:08 +03:00

[PR #273] [MERGED] docs: add blackwolf12333 as a contributor #725