#YTS 1.17.0 | All clients failed - 0 sig function possibilities

1 messages · Page 1 of 1 (latest)

low cove
#

I'm using version 1.17.0 of dev.lavalink.youtube.v2 with lavaplayer, and latest version of yt-cipher (tested using locally and remote). Started happening sometime this afternoon.


Client [MWEB] failed: Remote cipher service request to resolve URL failed with status code: 500. Response: {"error":"found 0 sig function possibilities"}Remote cipher service request to resolve URL failed with status code: 500. Response: {"error":"found 0 sig function possibilities"}
    at dev.lavalink.youtube.cipher.RemoteCipherManager.validateAndGetResponseBody(RemoteCipherManager.java:178)
    at dev.lavalink.youtube.cipher.RemoteCipherManager.resolveUrl(RemoteCipherManager.java:157)
    at dev.lavalink.youtube.cipher.RemoteCipherManager.resolveFormatUrl(RemoteCipherManager.java:66)
    at dev.lavalink.youtube.track.YoutubeAudioTrack.loadBestFormatWithUrl(YoutubeAudioTrack.java:208)
    at dev.lavalink.youtube.track.YoutubeAudioTrack.processWithClient(YoutubeAudioTrack.java:134)

*REPEATS FOR EVERY CLIENT*
merry falcon
twin matrix
#

make sure you are using the latest version of yt-cipher, or try the public one https://cipher.kikkia.dev that one always runs the latest one.

winged heath
twin matrix
#

Switching the public url, and restarting (to make sure its using the public url) doesnt work? I don't see any 500s coming from the public api, are you sure you are hitting it and getting a 500 back?

winged heath
twin matrix
#

no worries, no you need to tackle how to use yt with flagged ips, theres lots of other help threads about it

winged heath
#

ipv6?

inland kettle
#

same question i also want to know how to tackle this yt flagged ips

#

as in hetzner after creating new server also iam getting same errors

#

while using yt urls

winged heath
#

I also have a hetzner server with IPv6 enabled and working. I use YouTube Source with refreshToken and RemoteCipher

inland kettle
winged heath
#

Nope

inland kettle
#

thats my question

#

normal searching mine also works

#

with ipv4

winged heath
#

Before it didn’t work anymore

inland kettle
#

mine never gave any issues with ipv4 only issue is that yt urls not working with either ipv4 or ipv6