I recently found out that the exporter I had been using somehow broke. I’m not sure whether this is because of a change in the jitsi docker image or something else. The last time I can confidently say it worked was in version 6173.
I previously used the jitsiexporter by xsteadfastx and also now tried the one by systemli, both of which get a Connection refused
error when attempting to connect to the /colibri/stats
path or any other monitoring API. I can use curl localhost:8888/colibri/stats
and receive a result just fine. The exporters should have been in the correct docker network as well.
Here is my config:
exporter:
version: '3.7'
services:
jitsiexporter:
image: quay.io/xsteadfastx/jitsiexporter
restart: unless-stopped
ports:
- 9700:9700
command: -url http://localhost:8888/colibri/stats
#image: systemli/prometheus-jitsi-meet-exporter:latest
#ports:
# - 9700:9888
#command: -videobridge-url http://localhost:8888/colibri/stats
networks:
exporter.jitsi:
networks:
exporter.jitsi:
name: exporter.jitsi
jitsi:
[...]
# Video bridge
jvb:
image: jitsi/jvb:${VERSION}
restart: ${RESTART_POLICY}
ports:
- '${JVB_PORT}:${JVB_PORT}/udp'
- '${JVB_TCP_PORT}:${JVB_TCP_PORT}'
- '${JVB_TCP_MAPPED_API_PORT}:${JVB_TCP_API_PORT}'
volumes:
- ${CONFIG}/jvb:/config:Z
environment:
- DOCKER_HOST_ADDRESS
- ENABLE_COLIBRI_WEBSOCKET
- ENABLE_OCTO
- JVB_AUTH_USER
- JVB_AUTH_PASSWORD
- JVB_BREWERY_MUC
- JVB_PORT
- JVB_MUC_NICKNAME
- JVB_TCP_HARVESTER_DISABLED
- JVB_TCP_PORT
- JVB_TCP_MAPPED_PORT
- JVB_STUN_SERVERS
- JVB_WS_DOMAIN
- JVB_WS_SERVER_ID
- PUBLIC_URL
- COLIBRI_REST_ENABLED
- SHUTDOWN_REST_ENABLED
- TZ
- XMPP_AUTH_DOMAIN
- XMPP_INTERNAL_MUC_DOMAIN
- XMPP_SERVER
depends_on:
- prosody
networks:
meet.jitsi:
exporter.jitsi:
# Custom network so all services can communicate using a FQDN
networks:
meet.jitsi:
name: meet.jitsi
exporter.jitsi:
external: true
.env
variables:
JVB_TCP_API_PORT=8080
JVB_TCP_MAPPED_API_PORT=8888
# Optional properties for shutdown api
COLIBRI_REST_ENABLED=true
SHUTDOWN_REST_ENABLED=true
Perhaps this turns out to be a stupid config error on my side.
Any help is appreciated.