Jibri management scripts don't respect the custom internal-api-port
Closed this issue · 0 comments
emrahcom commented
Description
Jibri management scripts don't respect the custom internal-api-port which is set in jibri.conf.
reload.sh
shutdown.sh
graceful_shutdown.sh
reference.conf
Current behavior
These scripts call always through TCP/3333 which is hardcoded in scripts
Expected Behavior
They should call through the right port if it's changed in /etc/jitsi/jibri/jibri.conf
Possible Solution
The scripts can check jibri.conf for a possible customization and use the new value if it's changed. The ruby-hocon package must be in the jibri dependency list to apply this solution or needed a simple query using grep etc.
I can send a PR if this solution is OK for you too
Steps to reproduce
Change internal-api-port in jibri.conf and run /opt/jitsi/jibri/shutdown.sh
/opt/jitsi/jibri/shutdown.sh
curl: (7) Failed to connect to 127.0.0.1 port 3333: Connection refused