[GH-ISSUE #280] [BUG] Error 404 on certain songs when used in conjunction with zotify #50

New issue

Open

opened 2026-02-27 08:11:37 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 08:11:37 +03:00

Owner

Originally created by @FISSI0N on GitHub (Sep 14, 2024).
Original GitHub issue: https://github.com/kokarare1212/librespot-python/issues/280

I hope this is the right place to mention this bug, as I found it using zotify (and reported it there too: https://github.com/zotify-dev/zotify/issues/195 ). Please delete if it's the wrong place to report too, even though it seems to be connected to librespot's init.py file:

Track_ID: 1wPhVZMt6eIkGxcGBX6L2S


404

        [∙●∙] Preparing download... Traceback (most recent call last):
  File "C:\Python 3\Lib\site-packages\zotify\track.py", line 225, in download_track
    stream = Zotify.get_content_stream(track, Zotify.DOWNLOAD_QUALITY)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python 3\Lib\site-packages\zotify\zotify.py", line 53, in get_content_stream
    return cls.SESSION.content_feeder().load(content_id, VorbisOnlyAudioQuality(quality), False, None)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 723, in load
    return self.load_track(playable_id, audio_quality_picker, preload,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 784, in load_track
    return self.load_stream(file, track, None, preload, halt_listener)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 738, in load_stream
    return CdnFeedHelper.load_track(self.__session, track, file,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 340, in load_track
    streamer = session.cdn().stream_file(file, key, url, halt_listener)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 439, in stream_file
    return CdnManager.Streamer(
           ^^^^^^^^^^^^^^^^^^^^
  File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 562, in __init__
    response = self.request(range_start=0,
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 623, in request
    raise IOError(response.status_code)
OSError: 404

im using the latest snapshot version of librespot (which is still displayed as 0.0.9 though).

Originally created by @FISSI0N on GitHub (Sep 14, 2024). Original GitHub issue: https://github.com/kokarare1212/librespot-python/issues/280 I hope this is the right place to mention this bug, as I found it using zotify (and reported it there too: https://github.com/zotify-dev/zotify/issues/195 ). Please delete if it's the wrong place to report too, even though it seems to be connected to librespot's __init__.py file: ``` Track_ID: 1wPhVZMt6eIkGxcGBX6L2S 404 [∙●∙] Preparing download... Traceback (most recent call last): File "C:\Python 3\Lib\site-packages\zotify\track.py", line 225, in download_track stream = Zotify.get_content_stream(track, Zotify.DOWNLOAD_QUALITY) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Python 3\Lib\site-packages\zotify\zotify.py", line 53, in get_content_stream return cls.SESSION.content_feeder().load(content_id, VorbisOnlyAudioQuality(quality), False, None) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 723, in load return self.load_track(playable_id, audio_quality_picker, preload, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 784, in load_track return self.load_stream(file, track, None, preload, halt_listener) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 738, in load_stream return CdnFeedHelper.load_track(self.__session, track, file, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 340, in load_track streamer = session.cdn().stream_file(file, key, url, halt_listener) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 439, in stream_file return CdnManager.Streamer( ^^^^^^^^^^^^^^^^^^^^ File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 562, in __init__ response = self.request(range_start=0, ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Python 3\Lib\site-packages\librespot\audio\__init__.py", line 623, in request raise IOError(response.status_code) OSError: 404 ``` im using the latest snapshot version of librespot (which is still displayed as 0.0.9 though).

kerem added the

bug

label

2026-02-27 08:11:37 +03:00

kerem commented

2026-02-27 08:11:38 +03:00

Author

Owner

@Masterolic commented on GitHub (Sep 17, 2024):

404 stands for not found seems like the track is not available at your region or unavailable

@Masterolic commented on GitHub (Sep 17, 2024): 404 stands for not found seems like the track is not available at your region or unavailable

kerem commented

2026-02-27 08:11:38 +03:00

Author

Owner

@FISSI0N commented on GitHub (Sep 21, 2024):

I just tryied via VPN and am still getting the same error.
I believe its got nothing to do with a region lock

@FISSI0N commented on GitHub (Sep 21, 2024): I just tryied via VPN and am still getting the same error. I believe its got nothing to do with a region lock

kerem commented

2026-02-27 08:11:38 +03:00

Author

Owner

@Masterolic commented on GitHub (Sep 21, 2024):

I just tryied via VPN and am still getting the same error. I believe its got nothing to do with a region lock

That what make us confuse robust blocking had being done by Spotify just using a vpn does not resolve it else we would use that but that made harder for us. When we use vpn Spotify detect it as different region from which region your account had being created so they still stuck us on the current region. In case if we had to shift Country use vpn and login to web and there to your profile settings you can see a option had enabled named region which you can select your current ip address region and the default region (the region when you created).

Unfortunately the game had not ended it takes several minutes to get updated through the whole service

@Masterolic commented on GitHub (Sep 21, 2024): > I just tryied via VPN and am still getting the same error. I believe its got nothing to do with a region lock That what make us confuse robust blocking had being done by Spotify just using a vpn does not resolve it else we would use that but that made harder for us. When we use vpn Spotify detect it as different region from which region your account had being created so they still stuck us on the current region. In case if we had to shift Country use vpn and login to web and there to your profile settings you can see a option had enabled named region which you can select your current ip address region and the default region (the region when you created). Unfortunately the game had not ended it takes several minutes to get updated through the whole service

kerem commented

2026-02-27 08:11:38 +03:00

Author

Owner

@Erriez commented on GitHub (Oct 20, 2024):

Discussed in librespot-org project issue Connection reset by peer (os error 104) #1340.

Looks like this MR should be backported to this project in order to fix the connection problems.

@Erriez commented on GitHub (Oct 20, 2024): Discussed in [librespot-org project issue Connection reset by peer (os error 104) #1340](https://github.com/librespot-org/librespot/issues/1340). Looks like [this MR](https://github.com/librespot-org/librespot/pull/1359) should be backported to this project in order to fix the connection problems.

kerem referenced this issue

2026-02-27 08:11:57 +03:00

[PR #50] [MERGED] Format code with yapf #109