[Bug] Some issues

[LennBoedd]

First off, this is a really cool tool :)
But I’ve found a few things that probably aren’t intended to work this way.

1. When a music bot is deleted, it doesn’t seem to take effect until the manager is restarted.

2. Streaming a YouTube video via a bot doesn’t seem to work. I always get an HTTP 500 error, even though I’ve uploaded the cookies.

3. The “Animated Channel Name” BotFlow causes a socket crash for me. Also, the parameter for the time interval between updates doesn’t seem to work properly here. Anything under 2 seconds apparently just defaults to 2 seconds.

And a little wish: If I understand correctly, streaming via the bots is currently only possible through the Manager.
It would be awesome if you could also start a stream using, for example, !stream <URL/Path>.

[TheMaxik]

Anything under 2 seconds apparently just defaults to 2 seconds.

I thought this was a bug on my end. -> +1

Not sure but looks like your Bot is being blocked by flood protection. Did you add the ip of the bot to the query_ip_allowlist.txt ?
This should bypass flood protection

[GingerFury6]

5. The “Animated Channel Name” BotFlow causes a socket crash for me. Also, the parameter for the time interval between updates doesn’t seem to work properly here. Anything under 2 seconds apparently just defaults to 2 seconds.

The socket doesnt crash you got a ban for flooding as you see in the first error "Flow 2 channel update error: client is flooding"

This is because you dont set the ip of the manager backend in the query_ip_allowlist in your teamspeak server (putting in the IP there disables the flood mechanism for the backend and you can execute as many commands as you wish)

2. Streaming a YouTube video via a bot doesn’t seem to work. I always get an HTTP 500 error, even though I’ve uploaded the cookies.

you have to look in the backend logs or the sidecar logs but "Error 500" ist most likely due to yt-dlp issues.

[TheMaxik]

@LennBoedd are you hosting the bot in a datacenter (Hetzner?) ytdl usually gets 500 when youtube block you because you're literally a Bot or due to the video being age restriced. Both should be avoidable by insterting your youtube cookie under Settings->Youtube

[GingerFury6]

@LennBoedd are you hosting the bot in a datacenter (Hetzner?) ytdl usually gets 500 when youtube block you because you're literally a Bot or due to the video being age restriced. Both should be avoidable by insterting your youtube cookie under Settings->Youtube

NOTE: the cookies need to be logged in cookies (when using a Hetzner server), so exportet from an actual logged in account - also very important the account you exportet the cookies from cant be used as a "normal account" anymore so in the moment you exportet the cookies from the logged in account you cant watch any videos with it in your browser anymore - only in the manager. As for mostly any video request in the browser some keys in the cookie gets rerolled (if using the manager only this is not a problem cause yt-dlp updates the cookie file itself on any request) so everytime you watch a video again with the specific account outside of the manager the cookies inside the manager get invalid.

[TheMaxik]

Is is possible to change the ytdl arguments? Sometimes --extractor-args "youtube:player_client=ios" (faking the client to be a phone) bypasses the datacenter block

[LennBoedd]

@LennBoedd are you hosting the bot in a datacenter (Hetzner?) ytdl usually gets 500 when youtube block you because you're literally a Bot or due to the video being age restriced. Both should be avoidable by insterting your youtube cookie under Settings->Youtube

Jop, I'm using a server VM in a datacenter, but not Hetzner. Should be the same tho.

NOTE: the cookies need to be logged in cookies (when using a Hetzner server), so exportet from an actual logged in account - also very important the account you exportet the cookies from cant be used as a "normal account" anymore so in the moment you exportet the cookies from the logged in account you cant watch any videos with it in your browser anymore - only in the manager. As for mostly any video request in the browser some keys in the cookie gets rerolled (if using the manager only this is not a problem cause yt-dlp updates the cookie file itself on any request) so everytime you watch a video again with the specific account outside of the manager the cookies inside the manager get invalid.

This might be the issue. I'm using a logged in account but will test later. Thanks :)

[D3nnis3n]

@LennBoedd are you hosting the bot in a datacenter (Hetzner?) ytdl usually gets 500 when youtube block you because you're literally a Bot or due to the video being age restriced. Both should be avoidable by insterting your youtube cookie under Settings->Youtube

NOTE: the cookies need to be logged in cookies (when using a Hetzner server), so exportet from an actual logged in account - also very important the account you exportet the cookies from cant be used as a "normal account" anymore so in the moment you exportet the cookies from the logged in account you cant watch any videos with it in your browser anymore - only in the manager. As for mostly any video request in the browser some keys in the cookie gets rerolled (if using the manager only this is not a problem cause yt-dlp updates the cookie file itself on any request) so everytime you watch a video again with the specific account outside of the manager the cookies inside the manager get invalid.

Actually, that seems to not be correct as I figured out. I exported cookies from my personal, logged in account - but from a Google Chrome Incognito tab that I never did anything else with than open Youtube, watch until I get the cookies, export and close the window so the same session never gets opened again. That cookie still works since setup on the bot, despite I have used Youtube tons of times with the same account on different browsers.

I think it's nontheless not advisable to do this, especially if you plan to use the bot frequently and on a public server, given it might be some ToS violation that could get the account blocked.

[GingerFury6]

Can you Check the backend Logs, when getting the error 500? I wonder what error yt-dlp is throwing exactly