Closed LucasB25 closed 4 months ago
Add more clients for more resilience.
Also you have a client config for TVHTML5 but it isn't even registered...
I've also just seen that you have playback disabled for the WEB
client, so requests are being routed through the ANDROID
client which is broken with no known fix.
Do not blindly copy the client config if you do not know what it does. I would advise removing it.
If something and disabled it is not usable so it should not create a problem on the operation
but so I did not understand what I should keep for a classic use
this area is for default use if I understood correctly?
No I'm referring to the client-specific configs where you can adjust what each client will handle. You appear to have blindly copied the demo config from the README without understanding what it does.
No I'm referring to the client-specific configs where you can adjust what each client will handle. You appear to have blindly copied the demo config from the README without understanding what it does.
Honestly yes because initially at the beginning of the plugin it worked and there was no mention that some area was there for advanced uses
this area is for default use if I understood correctly?
Only this area and therefore useful for conventional use without going into more advanced use then?
No I'm referring to the client-specific configs where you can adjust what each client will handle. You appear to have blindly copied the demo config from the README without understanding what it does.
Honestly yes because initially at the beginning of the plugin it worked and there was no mention that some area was there for advanced uses
When I wrote it I anticipated users reading the attached comments and reading to see what the configs do. They're only there for illustration purposes, to demonstrate what can be done should someone want more granular control over what each client does/handles.
At the beginning of the plugin, ANDROID
worked. It no longer does. Also, the plugin didn't support client-specific configs which meant that disabling playback for individual clients wasn't possible, hence why everything seemingly worked.
The best advice I can give when it comes to software and the configuration of, is to not touch/use anything you aren't familiar with to avoid such mishaps. I have improved the comments surrounding the configuration feature to hopefully avoid situations like these going forward
I made the changes you tell me, despite that I still have the same error feedback "Not success status code: 403"
Add more clients for more resilience.
You did not do this.
spring.log
I randomly get a null return sometimes and when I restart LavaLink, it seems to pick up the music that previously returned an error.