jetty is disabled by default now.
you can enable statistics by passing the “–api=rest,” value for JVB_OPTS option in /etc/jitsi/videobridge/config file.
Hi! Just wanted to say thanks for the point regarding jetty. I’d been troubleshooting a Colibri statistics problem – no obvious REST API, and jvb.log had some confusing messages – for quite a while, looking at Woodworker_Life’s tutorials, etc., when I came across some jetty settings for the videobridge2 config. I was about to start adding those to my config when I read this thread.
Instead I went back into jvb.log and eventually realised that the socket for the Cockpit Project service I’m running was clashing with it, on 9090/tcp; I stopped the service and I can now get stats via the REST API on 8080/tcp, as you say, with no additional settings. (Well, the previously-mentioned tutorial does suggest --apis=rest,xmpp and this doesn’t seem to break things.)
I also had to add these lines to /etc/jitsi/videobridge/sip-communicator.properties:
org.jitsi.videobridge.rest.private.jetty.port=8080
org.jitsi.videobridge.rest.private.jetty.host=0.0.0.0
Without these, I could not access the status endpoint from anywhere but localhost.
well, that’s a different issue that the original one. Accessing statistics from anywhere should be done preferably through some tunnel or VPN since there is no authentication or encryption so it’s better not to set the options like you did IMO.
You are right, this access should probably only be allowed for those behind your firewall. If you don’t set these settings you will not even be able to access the stats from anywhere but localhost even if you are behind the firewall. If you want to build a system to get Jitsi stats and display them to administrators, these settings are needed. In my case, my Jitsi server is behind a firewall and a NAT and port 8080 is not accessible from the outside.
I added this info here because it is a related issue and I’m hoping this will save some time for those trying to set up a jitsi monitor.