[GH-ISSUE #499] GetBrowseCategories - status code 502 bad gateway #1221

New issue

Closed

opened 2026-03-14 14:00:00 +03:00 by kerem · 2 comments

kerem commented

2026-03-14 14:00:00 +03:00

Owner

Originally created by @japopich on GitHub (Jul 8, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/499

Describe the bug
When pressing g b to get to the browse page I get an http error: status code 502 Bad Gateway in the log and a subsequent blank page in the application.

To Reproduce
Press g b

Expected behaviour
Open the spotify browse page

Log and backtrace
2024-07-08T17:14:22.636700Z ERROR client_request{request=GetBrowseCategories}: spotify_player::client::handlers: Failed to handle client request: http error: status code 502 Bad Gateway

Environment

OS: Arch Linux
Application version: 0.19.1
Application features: cargo build --release --no-default-features --features pulseaudio-backend,streaming,lyric-finder,media-control,notify,sixel,fzf

Additional context
This was working in the last version 0.18.2

Originally created by @japopich on GitHub (Jul 8, 2024). Original GitHub issue: https://github.com/aome510/spotify-player/issues/499 **Describe the bug** When pressing `g b` to get to the browse page I get an http error: status code 502 Bad Gateway in the log and a subsequent blank page in the application. **To Reproduce** Press `g b` **Expected behaviour** Open the spotify browse page **Log and backtrace** `2024-07-08T17:14:22.636700Z ERROR client_request{request=GetBrowseCategories}: spotify_player::client::handlers: Failed to handle client request: http error: status code 502 Bad Gateway` **Environment** - OS: Arch Linux - Application version: 0.19.1 - Application features: cargo build --release --no-default-features --features pulseaudio-backend,streaming,lyric-finder,media-control,notify,sixel,fzf **Additional context** This was working in the last version 0.18.2

kerem

2026-03-14 14:00:00 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-14 14:00:17 +03:00

Author

Owner

@aome510 commented on GitHub (Jul 8, 2024):

Still works for me in the latest version.

This 50x error is mainly because of internal errors with Spotify server, which should be resolved after a day or so

@aome510 commented on GitHub (Jul 8, 2024): Still works for me in the latest version. This `50x` error is mainly because of internal errors with Spotify server, which should be resolved after a day or so

kerem commented

2026-03-14 14:00:22 +03:00

Author

Owner

@japopich commented on GitHub (Jul 8, 2024):

I will mark this as resolved, cheers!

@japopich commented on GitHub (Jul 8, 2024): I will mark this as resolved, cheers!