Your instruction is fine and clear. However:
I have installed jitsi on my own server (ubuntu 18.04, nginx). https://meet.2ls4u.eu/ Opening page shows up fine, but other visitors can not be seen. Then I restarted (via SSH) during the meeting:
- systemctl restart prosody.service
- systemctl restart jicofo.service
- systemctl restart jitsi-videobridge2.service And the system works fine.
But: when after logging out I start a new meeting the participants
- can see themselves
- but appear muted and without video on the other screens (though they opened their camera and microphone).
When trying the same restart trick I get the message: “Job for jicofo.service failed because the control process exited with error code. See “systemctl status jicofo.service” and “journalctl -xe” for details.” I imagine this has to do with jicofo, but the indications as suggested (systemctl status jicofo.service, journalctl -xe) do not clarify very much. The first one makes clear that something goes wrong with the exit code, but I have no idea how to repair this.
Do you have any suggestion how to solve this?
Thanks in advance for your attention. Fokko Dijkstra (chain foundation) - foundation@chain.eu
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hello,
This issue could be due to several reasons like incorrect firewall settings, network configuration issues, or even issues with the software dependencies or configuration. Here are few steps to debug and hopefully solve the issue:
-
Check jicofo logs: Run the command
journalctl -u jicofo.serviceorcat /var/log/jitsi/jicofo.logto see the logs of the jicofo service. These logs should give you more details about why the service is not starting correctly. -
Check Firewall Settings: Ensure that your firewall is not blocking any necessary ports. For a Jitsi server, you should have at least these ports open:
- TCP/443 (or TCP/4443 and TCP/80 if you are not using a SSL certificate)
- UDP/10000 (for the video bridge)
-
Check NAT Configuration: If your server is behind NAT (i.e. it has a private IP address), you need to set the
org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESSandorg.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESSproperties in the/etc/jitsi/videobridge/sip-communicator.propertiesfile to your private and public IP addresses respectively. -
Ensure services are running: Make sure that prosody, jicofo, and jitsi-videobridge services are all running correctly. You can use the command
systemctl status <service_name>to check the status of each service. -
Reconfigure Jitsi: You can try reconfiguring your Jitsi instance using the command
dpkg-reconfigure jitsi-videobridge2anddpkg-reconfigure jicofo. During reconfiguration, make sure to input correct domain and other settings. -
Update and Upgrade System: Ensure that your system and Jitsi Meet are up to date. Run
apt-get updateandapt-get upgradeto update your system packages. To update Jitsi, you can runapt-get install jitsi-meet.
Remember to restart the services after each change to apply them. If none of the above helps, please share the errors that you get in the logs for a more accurate diagnosis.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.