I checked, such error occurs on any virtual server.Hello,
can you check if the port 9987 is already is use?
Regards
it happens too.Yes I have the same problem when I delete a server, and re create it with the same port, I am forced to completely restart teaspeak
Is there any way to fix the port conflict? Or while to abandon the music bot?Im still a little bit confused, why FFMPEG uses UDP ports?!
Specially the ports which TeaSpeak use as well.
My first thought that this is just a displaying error and the process isnt ffmpeg instead its TeaSpeak
I think it's because it using the "port" to connect to the server (maybe?)Im still a little bit confused, why FFMPEG uses UDP ports?!
Specially the ports which TeaSpeak use as well.
My first thought that this is just a displaying error and the process isnt ffmpeg instead its TeaSpeak
Never fixed it there, I'm still searching for a way to reproduce it and to determine how ffmpeg listen on ports, because for me locally it doesn't do thatAfter upgrading to 1.2.18-beta, the bug still persists.
To play this you need to:Never fixed it there, I'm still searching for a way to reproduce it and to determine how ffmpeg listen on ports, because for me locally it doesn't do that
I can provide you with my test VDS on which there is this problemNever fixed it there, I'm still searching for a way to reproduce it and to determine how ffmpeg listen on ports, because for me locally it doesn't do that