JItsi instance built and running but unexpected behaviour on runtime

Talleyrand-34 commented 1 week ago

Describe the bug

With the config on the tutorial plus revising jitsi module. The videocalls drop when a second user enters it.

The service is built correctly
The instance works perfectly on init
At runtime it cannot connect two users to the same call

Steps To Reproduce

Steps to reproduce the behavior:

run module conf

flake.nix
inputs = {
#both fail
nixpkgs.url = "github:nixos/nixpkgs?ref=nixos-unstable";
#nixpkgs.url = "github:nixos/nixpkgs?ref=nixos-24.05";
};

{
services.jitsi-meet = {
enable = true;
hostName = "meet.domain.com"; # change this to your domain
#prosody.enable = false;
};

services.jitsi-videobridge.openFirewall = true;
services.jitsi-videobridge.enable = true;
services.jitsi-meet.videobridge.enable = true;

security.acme = {
acceptTerms = true; # ensure that you have read the subscriber agreement (https://letsencrypt.org/repository/)
defaults.email = "user@mail.com"; # change this to your email address
};

networking.firewall.allowedTCPPorts = [ 80 443];
networking.firewall.allowedUDPPorts = [ 10000];
}

nixos-rebuild test --flake /path#flakename
Expected behavior

Videocalls working

Additional context

Add any other context about the problem here.

Notify maintainers

@cleeyv @ryantm @lassulus @yayayayaka @asymmetric

Metadata

[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.74, NixOS, 24.11 (Vicuna), 24.11.20240624.2893f56`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.3`
 - channels(root): `"nixos-23.11pre-git"`
 - nixpkgs: `/nix/store/bi5zxc0v5g6ylygdwyqzh280sccg3ykb-source`

Resources

https://summer.nixos.org/blog/deploying-simple-jitsi-meet-server/ https://nixos.org/manual/nixos/stable/#module-services-jitsi-meet

Lassulus commented 1 week ago

additionally I have port 4443 tcp and 10000 tcp open, can you check with those again?

Lassulus commented 1 week ago

ah, videobridge.openFirewall should probably take care of that, have you trid restarting the videobridge? is there anything interesting in the journal logs?

Talleyrand-34 commented 6 days ago

ah, videobridge.openFirewall should probably take care of that, have you trid restarting the videobridge? is there anything interesting in the journal logs?

@Lassulus I forgot to add this that is the warning which full videobrdge log MucClient.setPresenceExtensions#467: Cannot set presence extension: not connected. There is no error

Lassulus commented 3 days ago

hmm not sure, maybe restarting prosody helps? it does for me sometimes

NixOS / nixpkgs