I have clients that get an error 404 sometimes.
After some reloads, it seems to dissapear and all works fine.
I had 2 changes before:
It was an debian10 systen with auth and a local turnserver and all worked fine with the stable version.
I made all upgrades with apt upgrade.
the server has ip4 and ip6, but i just configured ip4 in dns an the services.
Lastly i cloned the server, changed ip, hostname and videobrige id and made the changes to bind the 2nd servers videobridge to server 1. then i disabled all services but videobridge2.
Then i made the major upgrade to 2.0.5390-1.
All seemed to work fine. The conferences where balanced between the 2 servers and both have a similar count of streams.
On the vbs there are just 3 ports:
tcp6 0 0 127.0.0.1:8080 :::* LISTEN 893/java
tcp6 0 0 :::9090 :::* LISTEN 893/java
and the outgoing connect to the main server:
tcp6 0 0 184.108.40.206:46238 220.127.116.11:5222 ESTABLISHED 893/java
But now i get a lot of compliants about periodic error 404 if clients wants to connect.
It seems to disappear after a few reloads.
It should be no workload problem, because there are just about 250 streams on each server.
The single server had between 300 and 600 streams without major problems.
Where should i look?