User Tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
services:spotizerr [2025/05/30 07:14] – willyservices:spotizerr [2025/10/15 06:53] (current) – [Reverse Proxy] willy
Line 1: Line 1:
 ====== Spotizerr ====== ====== Spotizerr ======
  
-[[https://github.com/Xoconoch/spotizerr|Spotizerr]] is an amazing self-hosted web service that let's you download and search for music from Deezer and Spotify.+ 
 +**UPDATE:** //As of October 2025, due to being abandoned, a few critical bugs in latest release 4 caused it to malfunction. You need to downgrade to 3.3.0 which works fine, but it's a bit less polished.// 
 + 
 +**UPDATE:** //As of August 2025, Spotizerr GitHub account has been taken down by a DMCA request from Spotify. While this sucks, the goodness of Open Source means that Spotizerr lives along and has been moved to a new repository. I have updated all the links in this page to reflect that. If you are migrating from an existing install from GitHub, be aware that a few changes are required. Review your docker compose according to the one in this page.// 
 + 
 +[[https://lavaforge.org/spotizerr/spotizerr]] is an amazing self-hosted web service that let's you download and search for music from Deezer and Spotify.
  
 While i **do not recomend** to use it, as it's against those services ToS, it seems to be working pretty well at least if you have a premium account. While i **do not recomend** to use it, as it's against those services ToS, it seems to be working pretty well at least if you have a premium account.
Line 18: Line 23:
 chown spotizerr:media /var/log/spotizerr chown spotizerr:media /var/log/spotizerr
 su - spotizerr su - spotizerr
-wget https://raw.githubusercontent.com/Xoconoch/spotizerr/refs/heads/main/docker-compose.yml+wget https://lavaforge.org/spotizerr/spotizerr/raw/branch/main/docker-compose.yaml
 </code> </code>
  
Line 33: Line 38:
     ports:     ports:
       - 7171:7171       - 7171:7171
-    image: cooldockerizer93/spotizerr+    # image: lavaforge.org/spotizerr/spotizerr:latest # For version 4.0.0, which is broken 
 +    image: cooldockerizer93/spotizerr # previous version 3.3.0, that works fine
     container_name: spotizerr-app     container_name: spotizerr-app
     environment:     environment:
Line 74: Line 80:
 </code> </code>
  
 +If you get an error starting up Spotizerr that says //Missing 'version' in data/config/main.json. Please update your configuration to 3.3.0.//, you need to edit your **/data/daemons/spotizerr/config/main.json** to add the following line:
 +<code>
 +    "version": "3.3.1",
 +</code>
 +
 +You can add it anywhere, and if the file itself is missing, just create it, but remeber it's a json file, so you will need to wrap that line between {}.
  
 ===== Reverse Proxy ===== ===== Reverse Proxy =====
Line 83: Line 95:
         server_name spotizerr.mydomain.com;         server_name spotizerr.mydomain.com;
         listen 443 ssl;         listen 443 ssl;
-        listen 8443 ssl;+        http2 on; 
 + 
 +        access_log /var/log/nginx/spotizerr.mydomain.com_access_log main; 
 +        error_log /var/log/nginx/spotizerr.mydomain.com_error_log info; 
 + 
 +        location / { 
 +                proxy_pass http://127.0.0.1:7171/; 
 +                proxy_set_header Connection $http_connection; 
 +                proxy_set_header Upgrade $http_upgrade; 
 +        } 
 + 
 +        include com.mydomain/certbot.conf; 
 +} 
 + 
 +server { 
 +        server_name spotizerr.mydomain.com; 
 +        listen 443 ssl;
         http2 on;         http2 on;
  
Line 99: Line 127:
         }         }
  
-        include org.gardiol/certbot.conf;+        include com.mydomain/certbot.conf;
 } }
- 
-Please note that Spotizerr does not provide **any** authentication or protection: you **must** put your SSO (see [[selfhost:sso|here]]) and HTTPS on top of it using the reverse proxy as in the above config example. 
 </file> </file>
 +
 +Please note that Spotizerr does not provide **any** authentication or protection: you **must** put your SSO (see [[selfhost:sso|here]]) and HTTPS on top of it using the reverse proxy as in the above config example. As usual, i have put SSO on external facing access and no SSO on internal one.