Muse does not function

[slaapkopamy]

What's happening?
I recently setup a clean installation of muse using docker compose file pulling the latest version (2.11.1), I inserted the api keys for youtube and spotify in the bot with ofcourse my bot token. started the bot up and invited the bot in my server. now i wanted to test the functionality of the bot by adding a spotify url in the play command to findout it's getting errored with ope: song not found, tried with a different url.. same thing. tried with just searching... guess what... same thing...
if i try with a youtube url i get 403 forbidden (probably something on google side since i cant access the api key on my pc either)

Logs
For some reason, there are no logs being produced in the docker container. if i run docker compose logs -f the only last thing i see is the discord invite url for the bot.

Screenshots
discord: https://slaapkopamy.com/sc/images/lJoRssyXbJ8FXjBr8SY4z.png
docker: https://slaapkopamy.com/sc/images/Y3NrZ4SoFvrCgdysphmkC.png

Additional context
Add any other context about the problem here.

Runtime
I'm running Muse:

• Directly from the cloned repository
• [x ] Inside a Docker container
• Something else (please elaborate)

Versions

• Muse: 2.11.1
• Docker (if applicable): 28.0.4 build v8034c0
• OS: ubuntu 20.4.6 lts
• Node.js: (if running outside the Docker container)
• ffmpeg: (if running outside the Docker container, 4.1 or later is required)

[melzyy]

try #1255

[slaapkopamy]

try #1255

Sadly tried and same issue, also the docker container does not produce any logs

[a-sitarz]

Got the same issue.
Looks like YT changed something, again...

[slaapkopamy]

Got the same issue. Looks like YT changed something, again...

maybe but i also have an issue with spotify which is not liked with google if i'm not wrong

[nealhead]

Are we done for? Do any self hosted music bots still work?

[JordiBrisbois]

Dirty fix while waiting for this pull request to be merged.

If you're using Docker, mount /usr/ as a volume:

services:
  muse:
    image: 'ghcr.io/museofficial/muse:pr-1256'
    restart: always
    volumes:
      - 'bot-data-muse:/data'
      - 'bot-datanode-muse:/usr/'
    environment:
      - DISCORD_TOKEN=xxx
      - YOUTUBE_API_KEY=xxx
      - SPOTIFY_CLIENT_ID=xxx
      - SPOTIFY_CLIENT_SECRET=xxx
volumes:
  bot-data-muse: null
  bot-datanode-muse: null

Next, edit /app/node_modules/@distube/ytdl-core/lib/sig.js inside the container and replace its contents with the code from:

https://raw.githubusercontent.com/distubejs/ytdl-core/ba7516dd4f5ad125f9ee8a41ebea486442533f82/lib/sig.js

Save the file, restart your container, and it should work.

[rexyness]

ghcr.io/museofficial/muse:pr-1256 can be used without the dirty fixed as of now ^_^

[ChrisTecha]

ghcr.io/museofficial/muse:pr-1256 can be used without the dirty fixed as of now ^_^

working for me

[Maikel1990]

ghcr.io/museofficial/muse:pr-1256 can be used without the dirty fixed as of now ^_^

Working for me for Youtube search results/links. Spotify playlist links gives me a no songs found error.
Single Spotify links works.

[DejaVuMan]

@Maikel1990 , that seems like a separate issue - I just loaded a custom spotify playlist with no issues using branch pr-1256.

[Mubelotix]

@slaapkopamy Since the fix has been merged, you should close this issue unless you can still reproduce the issue in latest version

[slaapkopamy]

@slaapkopamy Since the fix has been merged, you should close this issue unless you can still reproduce the issue in latest version

I still have the same issue,

pulled the pr1261 image. rechecked the api keys and secrets if they are still valid (they are).
loaded up the bot via docker compose up -d, checked after that the logs to see if there are any errors (none).
did /play in the discord with a random query, got the same error as explained earlier. tried with a spotify url, same issue and tried with youtube url, same issue.

If my server ip is blocked I should receive a different error right? then only ope 403 on youtube and ope on spotify?

[Mubelotix]

Maybe you could try running it with yarn outside of docker after cloning the repository. Either it would work, or that would give us logs with more information