#This video requires login
1 messages · Page 1 of 1 (latest)
/48
tunnelbroker?
yes
LoadBalance, but my other lavalink which is running on legacy is not getting bonked for this
Missing TVHTML5EMBEDDED client ?
and it's running on the same server
try RotatingNanoSwitch
using that
what?
using the same ip block but only one node getting this issue?
post application ymls den
port: 2343
address: 0.0.0.0
lavalink:
server:
password: "xxx"
sources:
youtube: false
bandcamp: true
soundcloud: true
twitch: true
vimeo: true
mixer: true
http: true
local: false
bufferDurationMs: 400
youtubePlaylistLoadLimit: 60 # Number of pages at 100 each
youtubeSearchEnabled: true
soundcloudSearchEnabled: true
gc-warnings: true
plugins:
# replace VERSION with the current version as shown by the Releases tab.
- dependency: "com.github.lavalink-devs.lavaplayer-youtube-source:plugin:1.0.7"
repository: "https://jitpack.io"
- dependency: "com.github.topi314.lavasrc:lavasrc-plugin:4.1.1"
repository: "https://maven.lavalink.dev/releases" # this is optional for lavalink v4.0.0-beta.5 or greater
snapshot: false # set to true if you want to use snapshot builds (see below)
plugins:
youtube:
enabled: true
clients: ["TVHTML5EMBEDDED", "ANDROID", "MUSIC"]
TVHTML5EMBEDDED:
playlistLoading: true # Disables loading of playlists and mixes for this client.
videoLoading: true # Disables loading of videos for this client (playback is still allowed).
searching: true # Disables the ability to search for videos for this client.
lavasrc:
sources:
spotify: true # Enable Spotify source
applemusic: false # Enable Apple Music source
deezer: false # Enable Deezer source
yandexmusic: false # Enable Yandex Music source
flowerytts: false # Enable Flowery TTS source
youtube: false # Enable YouTube search source (https://github.com/topi314/LavaSearch)
spotify:
clientId: "xx"
clientSecret: "xx"
# spDc: "your sp dc cookie" # the sp dc cookie used for accessing the spotify lyrics api
countryCode: "US" # the country code you want to use for filtering the artists top tracks. See https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2
playlistLoadLimit: 6 # The number of pages at 100 tracks each
albumLoadLimit: 6 # The number of pages at 50 tracks each
ratelimit:
ipBlocks: ["2001:xxx::/48"] # list of ip blocks
#excludedIps: ["...", "..."] # ips which should be explicit excluded from usage by lavalink
strategy: "RotatingNanoSwitch" # RotateOnBan | LoadBalance | NanoSwitch | RotatingNanoSwitch
searchTriggersFail: true # Whether a search 429 should trigger marking the ip as failing
#retryLimit: -1 # -1 = use default lavaplayer value | 0 = infinity | >0 = retry will happen this numbers times
spring:
mvc:
async:
request-timeout: -1
metrics:
prometheus:
enabled: false
endpoint: /metrics
logging:
file:
max-history: 30
max-size: 1GB
path: ./logs/
level:
root: INFO
lavalink: INFO ```
what?
I am running lavalink 4.0.5 with lavaplayer 2.1.2. Interestingly enough, I am also running lavalink legacy on the server, and they are using the same ip blocks, but that one does not get this error?
u have 2 lavalink servers
running correct?
Oh i see
yes
port: 2333
address: 0.0.0.0
lavalink:
server:
password: "xxx"
sources:
youtube: true
bandcamp: true
soundcloud: true
twitch: true
vimeo: true
mixer: true
http: true
local: false
bufferDurationMs: 400
youtubePlaylistLoadLimit: 60 # Number of pages at 100 each
youtubeSearchEnabled: true
soundcloudSearchEnabled: true
gc-warnings: true
ratelimit:
ipBlocks: ["2001:xxx::/48"] # list of ip blocks
#excludedIps: ["...", "..."] # ips which should be explicit excluded from usage by lavalink
strategy: "LoadBalance" # RotateOnBan | LoadBalance | NanoSwitch | RotatingNanoSwitch
searchTriggersFail: true # Whether a search 429 should trigger marking the ip as failing
#retryLimit: -1 # -1 = use default lavaplayer value | 0 = infinity | >0 = retry will happen this numbers times
spring:
mvc:
async:
request-timeout: -1
metrics:
prometheus:
enabled: false
endpoint: /metrics
logging:
file:
max-history: 30
max-size: 1GB
path: ./logs/
level:
root: INFO
lavalink: DEBUG
this is the legacy one
alright
- dependency: "com.github.lavalink-devs.lavaplayer-youtube-source:plugin:1.0.7"
so use 1.3.0 here?
ye
We don't use jitpack anymore
Prob client based
Ur not using the web client in the application YML
Use the web client
Web client actually doesn't work either
so weird
But this must be something unrelated to ip-banning, because I am running lavalink legacy using the same /48 block and it is working
what for a server u use and what is the name of the provider?
nono but what hosting provider u use?
Please show me the LavaLink log.
It is not true that IP rotation has anything to do with this necessarily, or it might be a combination of IP/client. If you read what I have wrote, I am running two lavalink nodes, one on legacy v3 and one on v4. Both LL nodes access via the same ipv6 block, except one of them gets blocked and the other doesn't
well tf are you doing in this thread then? get your own thread
Getting this error too unfortunately
Seems to be only happening on the server I have it hosted on, going through he suggestions in this thread to see if one of them helps
occured to me as well
even with a 48 block
and all ips with my ASN
as well
https://github.com/TeamNewPipe/NewPipe/issues/11139, https://github.com/iv-org/invidious/issues/4734
hopefully this doesnt blow up
Whats the different between Rotateon Ban LoadBalance etc..?
They're the strategies used and determine when a new IP is selected
most commonly used (and generally most effective) is RotatingNanoSwitch, which updates the IP on every nanosecond update
is there a noob tutorial there? xD
But then I don't influence anything on the server that isn't lavalink, right?
or the whole server network internet traffic will go over tunnelbroker?
only youtube traffic will go over tunnelbroker
you'd have to specifically make requests with the ipv6 block tunnelbroker give you for traffic to route through it
so if you're doing general networking things (i.e. sending requests to discord) it will go over your normal network
ok thx for this info
Can I use for RotatingNanoSwitch /48 or do I need to use /64?
RotatingNanoSwitch is really good for a /48
I don't think anything less is advised with nanoswitch tbf, /48 is ideal, /64 might not be effective enough
the larger the block, the better the results generally speaking
Update: I solved this by changing my vps provider
ye cause they seem to be blocking asns lol