You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi and kudos on the plugin!
While running it from the local jitsi server the plugin works as it should, but when calling it from the monitoring server (or any other server as a script) I get the following error:
./check_jitsi.py -H domainname.local -p 5347 -m health
UNKNOWN - Could not connect to JVB API: Failed to resolve hostname or service is not listenings
I have checked the port to be open from any by modifying the prosody.conf.lua file and adding 0.0.0.0 for this port. is there any other port or configuration to be made to allow it to connect?
Also when trying _telnet domainname.local 5347 I get connected.
The text was updated successfully, but these errors were encountered:
org.jitsi.videobridge.rest.private.jetty.host=::in /etc/jitsi/videobridge/sip-communicator.properties is needed to not just bind to 127.0.0.1 issue solved
Hi and kudos on the plugin!
While running it from the local jitsi server the plugin works as it should, but when calling it from the monitoring server (or any other server as a script) I get the following error:
./check_jitsi.py -H domainname.local -p 5347 -m health
UNKNOWN - Could not connect to JVB API: Failed to resolve hostname or service is not listenings
I have checked the port to be open from any by modifying the prosody.conf.lua file and adding 0.0.0.0 for this port. is there any other port or configuration to be made to allow it to connect?
Also when trying _telnet domainname.local 5347 I get connected.
The text was updated successfully, but these errors were encountered: