saghul
commented
4 months ago Please share the logs of every component. Including the browser console logs.
Closed therock42 closed 3 months ago
saghul
commented
4 months ago Please share the logs of every component. Including the browser console logs.
therock42
commented
4 months ago Please share the logs of every component. Including the browser console logs.
do you mean jvb.log & jicofo.log
therock42
commented
4 months ago Please share the logs of every component. Including the browser console logs. jvb.log
JVB 2024-06-02 18:50:46.901 INFO: [1] JitsiConfig.
ji
therock42
commented
4 months ago Jicofo 2024-06-02 18:58:08.373 INFO: [1] Main.main#47: Starting Jicofo.
Jicofo 2024-06-02 18:58:10.716 INFO: [1] JitsiConfig.
therock42
commented
4 months ago Please share the logs of every component. Including the browser console logs. from start new conference to crashed ... < There are no operational bridges> how to fix it
Jicofo 2024-06-03 07:54:14.463 INFO: [22] ConferenceIqHandler.handleConferenceIq#86: Conference request for room test3@conference.jitsi.su.sd, from --xhanm6zyemrs7-4ft40uje@guest.jitsi.su.sd/r7IaTmnkwVo6
Jicofo 2024-06-03 07:54:15.440 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@3f8dfe74{/,null,AVAILABLE}
Jicofo 2024-06-03 07:54:15.477 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@3a5c2626{HTTP/1.1, (http/1.1)}{0.0.0.0:8888}
Jicofo 2024-06-03 07:54:15.506 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started Server@25e49cb2{STARTING}[11.0.20,sto=0] @11497ms
Jicofo 2024-06-03 07:54:15.506 INFO: [1] JicofoServices.
saghul
commented
4 months ago No valid IP addresses available for harvesting.
Did you configure the public mapping with the LAN address? It doesn't seem like you did.
therock42
commented
4 months ago No valid IP addresses available for harvesting.
Did you configure the public mapping with the LAN address? It doesn't seem like you did.
I did
org.jitsi.videobridge.NAT_HARVESTER_PUBLIC_ADDRESS=172.16.16.28
org.jitsi.videobridge.NAT_HARVESTER_LOCAL_ADDRESS=172.16.16.28
saghul
commented
4 months ago I don't think that is the correct syntax. It had ice4j in the name. The JVB has not applied that config, it logs a line about it.
therock42
commented
4 months ago I don't think that is the correct syntax. It had
ice4jin the name. The JVB has not applied that config, it logs a line about it.
like this?
org.ice4j.jitsi.videobridge.NAT_HARVESTER_PUBLIC_ADDRESS=172.16.16.28 org.ice4j.jitsi.videobridge.NAT_HARVESTER_LOCAL_ADDRESS=172.16.16.28
aaronkvanmeerten
commented
4 months ago While this is correct for the older syntax, I'd highly encourage you to switch to the latest jvb.conf hocon syntax rather than the older deprecated .properties style syntax. Certain properties are simply no longer able to be configured in this old format.
therock42
commented
4 months ago While this is correct for the older syntax, I'd highly encourage you to switch to the latest jvb.conf hocon syntax rather than the older deprecated .properties style syntax. Certain properties are simply no longer able to be configured in this old format.
plz help me to switch to latest jvb.conf, give me example to reconfigure /etc/jitsi/videobridge/sip-communicator.properties
path is: sudo nano /etc/jitsi/videobridge/jvb.conf right? below my jvb.conf file
videobridge { http-servers { public { port = 9090 } } websockets { enabled = true domain = "jitsi.su.sd:443" tls = true } }
aaronkvanmeerten
commented
4 months ago Given that this is the docker forum, I presume you are somehow overriding the entire JVB configuration with a new file. Can you confirm you're using the docker method? If so, you can simply start with a clean JVB and your .jitsi-meet-cfg/ directory will contain the newly generated jvb.conf file based on environment variables.
If you aren't in docker, a clean install of the debian package will result in the same thing in /etc/jitsi/videobridge/jvb.conf
Then you'll want to take the customizations you've made and re-apply them to the generated stock configuration. If you're in docker, I suggest migrating these to the relevant environment variables:
https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker#advanced-jvb-options
If you aren't running in docker, then you'll want to edit the file directly. Reference configuration is here: https://github.com/jitsi/jitsi-videobridge/blob/master/jvb/src/main/resources/reference.conf
I do not believe we have an automated translation tool but I'll ask the team today and see if anybody has any other suggestions.
therock42
commented
4 months ago While this is correct for the older syntax, I'd highly encourage you to switch to the latest jvb.conf hocon syntax rather than the older deprecated .properties style syntax. Certain properties are simply no longer able to be configured in this old format.
plz help me to switch to latest jvb.conf, give me example to reconfigure /etc/jitsi/videobridge/sip-communicator.properties
path is: sudo nano /etc/jitsi/videobridge/jvb.conf right? below my jvb.conf file
videobridge { http-servers { public { port = 9090 } } websockets { enabled = true domain = "jitsi.su.sd:443" tls = true } }
what is right configuration to add it?
aaronkvanmeerten
commented
4 months ago what is right configuration to add it?
So specifically for disabling harvesting and hard-coding a static mapping:
ice4j {
harvest {
mapping.stun.enabled = false
static-mappings = [
{
local-address = "<docker address>"
local-port = <docker port>
public-address = "<public address>"
public-port = "<public port>"
name = "<something unique>"
}
]
}
}
}Given that this is the docker forum, I presume you are somehow overriding the entire JVB configuration with a new file. Can you confirm you're using the docker method? If so, you can simply start with a clean JVB and your .jitsi-meet-cfg/ directory will contain the newly generated jvb.conf file based on environment variables.
If you aren't in docker, a clean install of the debian package will result in the same thing in /etc/jitsi/videobridge/jvb.conf
Then you'll want to take the customizations you've made and re-apply them to the generated stock configuration. If you're in docker, I suggest migrating these to the relevant environment variables:
i have using jitsi locally without public IP .
therock42
commented
4 months ago /etc/jitsi/videobridge/jvb.conf
add it in the end of file /etc/jitsi/videobridge/jvb.conf?
aaronkvanmeerten
commented
4 months ago i have using jitsi locally without public IP .
However you do have an IP/port that is accessible to other instances on your network? That's the IP/port you want to advertise in your mapping.
aaronkvanmeerten
commented
4 months ago add it in the end of file /etc/jitsi/videobridge/jvb.conf?
Correct, the hocon syntax can be added to the bottom of that existing file. If you prefer another file you can also use the include syntax.
include "custom.conf"
therock42
commented
4 months ago i have using jitsi locally without public IP .
However you do have an IP/port that is accessible to other instances on your network? That's the IP/port you want to advertise in your mapping.
sorry pro my English lang not good and am beginner in jitsi
therock42
commented
4 months ago what is right configuration to add it?
So specifically for disabling harvesting and hard-coding a static mapping:
ice4j { harvest { mapping.stun.enabled = false static-mappings = [ { local-address = "<docker address>" local-port = <docker port> public-address = "<public address>" public-port = "<public port>" name = "<something unique>" } ] } } }
docker address you mean my local ip addr
therock42
commented
4 months ago videobridge { http-servers { public { port = 9090 } } websockets { enabled = true domain = "jitsi.su.sd:443" tls = true } }
ice4j { harvest { mapping.stun.enabled = false static-mappings = [ { local-address = "172.16.16.28" local-port =1000 public-address = "172.16.16.28" public-port = "<1000>" name = "jitsi" } ] } } }
right?
aaronkvanmeerten
commented
4 months ago sorry pro my English lang not good and am beginner in jitsi
No worries, happy to keep attempting to explain. Let me know if this means you'd like me to re-state the suggestion in other words?
Basically, I presume you are running the JVB in a docker as you are posting to the docker project. Since that's the case, we'd assume your docker IP address is the local IP, and the host IP that you wish other instances to access is your "public" IP. So, the JVB needs to know what to advertise (public side of the mapping) and where to expect the incoming packets to be received (local side of the mapping). In the case of a JVB in docker on a local network you'd use the 192.168.x.x or 10.x.x.x address for the "public" side, and the 172.1x.x.x docker address for the local one.
Let me know if this clarifies anything, or if you have other questions.
aaronkvanmeerten
commented
4 months ago right?
Not exactly, but very close. The public side needs to be something that's accessible outside your docker network (unless you are only running clients inside your docker on a single machine). So that's usually an address like 192.168.x.x or 10.x.x.x depending on your network.
therock42
commented
4 months ago pro i don't know if my jitsi docker or not i'm install it from https://www.digitalocean.com/community/tutorials/how-to-install-jitsi-meet-on-ubuntu-22-04
plz help me i wanna to start it locally without internet access after install it
aaronkvanmeerten
commented
4 months ago I have transferred your issue out of the docker-jitsi-meet project in order to better associate it with correct type of project and stop any confusion about docker.
aaronkvanmeerten
commented
4 months ago As far as configuration goes, you shouldn't reference any thing docker-specific, which means you shouldn't use the 172.1x.x.x network either.
This is far outside my expertise as I have never run this for a local network. You'll probably need to look up what internal IP address your instance has, and configure that for both sides of static mapping. I'll also ask some of the team today to see if anyone else has any tips.
therock42
commented
4 months ago As far as configuration goes, you shouldn't reference any thing docker-specific, which means you shouldn't use the 172.1x.x.x network either.
This is far outside my expertise as I have never run this for a local network. You'll probably need to look up what internal IP address your instance has, and configure that for both sides of static mapping. I'll also ask some of the team today to see if anyone else has any tips.
if there are to side jitsi on 172.16.x.x and other side is 192.168.x.x what's configuration i could edit
saghul
commented
4 months ago Then out the loca IP to the 172 one and the public part to 192.
therock42
commented
4 months ago Then out the loca IP to the 172 one and the public part to 192.
my local ip is single (jitsi ip addr) but the public will be network like 192.168.x.x/24
aaronkvanmeerten
commented
4 months ago if there are to side jitsi on 172.16.x.x and other side is 192.168.x.x what's configuration i could edit
If you aren't running jitsi in docker, please do not configure any docker networking. The 172.16.x.x network is going to be docker-specific which means ONLY accessible on the one machine running docker containers. Unless your jitsi is running inside this docker container (if you followed the instructions you linked, it won't be), then you can disregard anything docker-specific (like the 172.16.x.x network).
So, you have a VM with a 192.168.x.x address. Then traditionally it's using STUN to detect its public address (while you are connected to the internet). We have suggested configurations that disable this STUN automated mapping, which requires a static mapping. The static mapping would simply reference the same 192.168.x.x address and port in both public and private side.
therock42
commented
4 months ago org.ice4j.ice.harvest.DISABLE_AWS_HARVESTER=true org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES=meet-jit-si-turnrelay.ji> org.jitsi.videobridge.ENABLE_STATISTICS=true org.jitsi.videobridge.STATISTICS_TRANSPORT=muc org.jitsi.videobridge.xmpp.user.shard.HOSTNAME=localhost org.jitsi.videobridge.xmpp.user.shard.DOMAIN=auth.jitsi.su.sd org.jitsi.videobridge.xmpp.user.shard.USERNAME=jvb org.jitsi.videobridge.xmpp.user.shard.PASSWORD=BioAAIza org.jitsi.videobridge.xmpp.user.shard.MUC_JIDS=JvbBrewery@internal.auth.jitsi.s> org.jitsi.videobridge.xmpp.user.shard.MUC_NICKNAME=3c601c28-440c-4d42-9ac9-84ce>
What needs to be modified?
aaronkvanmeerten
commented
4 months ago Hi, I suggest you stop using the sip-communicator.properties file for any of this, as they are deprecated and should simply not be used.
Please use the jvb.conf syntax as suggested in this thread instead.
aaronkvanmeerten
commented
4 months ago What needs to be modified?
The syntax I pasted above with the ice4j {} is what you'll need. Simply fill in your 192.168.x.x address in both places for local and public.
damencho
commented
4 months ago pro i don't know if my jitsi docker or not i'm install it from https://www.digitalocean.com/community/tutorials/how-to-install-jitsi-meet-on-ubuntu-22-04
plz help me i wanna to start it locally without internet access after install it
That ^ guide is outdated. https://jitsi.org/qi is the one we support and keep updated.
therock42
commented
4 months ago what is right configuration to add it?
So specifically for disabling harvesting and hard-coding a static mapping:
ice4j { harvest { mapping.stun.enabled = false static-mappings = [ { local-address = "<docker address>" local-port = <docker port> public-address = "<public address>" public-port = "<public port>" name = "<something unique>" } ] } } }
what about docher port? is local port is: 1000? public port is :1000?
aaronkvanmeerten
commented
4 months ago is local port is: 1000? public port is :1000?
Yes, in this case it's not docker port, but rather local port and remote port. Since you aren't doing any host->docker translations of port, the 10000 is correct in both cases. Make sure you make it 10000, not 1000 as you have posted here.
therock42
commented
4 months ago is local port is: 1000? public port is :1000?
Yes, in this case it's not docker port, but rather local port and remote port. Since you aren't doing any host->docker translations of port, the 10000 is correct in both cases. Make sure you make it 10000, not 1000 as you have posted here.
videobridge { http-servers { public { port = 9090 } } websockets { enabled = true domain = "jitsi.su.sd:443" tls = true } }
ice4j { harvest { mapping.stun.enabled = false static-mappings = [ { local-address = "192.168.1.38" local-port = 10000 public-address = "192.168.1.38" public-port = "10000" name = "therock" } ] } } }
still not work
therock42
commented
4 months ago Jicofo 2024-06-03 13:26:51.680 INFO: [47] ConferenceIqHandler.handleConferenceIq#86: Conference request for room test4@conference.jitsi.su.sd, from 1p8r-ckvfmacprtna5arywl6@guest.jitsi.su.sd/uYtf23WukJ9c
Jicofo 2024-06-03 13:26:51.681 INFO: [47] AbstractAuthAuthority.authenticateJidWithSession#431: Authenticated jid: 1p8r-ckvfmacprtna5arywl6@guest.jitsi.su.sd/uYtf23WukJ9c with session: AuthSession[ID=usr@jitsi.su.sd, JID=1p8r-ckvfmacprtna5arywl6@guest.jitsi.su.sd/uYtf23WukJ9c, SID=3620e045-e7ee-4d04-967f-8c3449ef1eb5, MUID=9a98efb3eddda97a9c6200d0ed023e4d, LIFE_TM_SEC=297, R=test3@conference.jitsi.su.sd]@297203553
Jicofo 2024-06-03 13:26:51.682 INFO: [47] AbstractAuthAuthority.notifyUserAuthenticated#339: Jid 1p8r-ckvfmacprtna5arywl6@guest.jitsi.su.sd/uYtf23WukJ9c authenticated as: usr@jitsi.su.sd
Jicofo 2024-06-03 13:26:51.684 INFO: [47] [room=test4@conference.jitsi.su.sd] JitsiMeetConferenceImpl.
same issue
therock42
commented
4 months ago i need to disabe stun ?
how to disable it on /etc/jitsi/videobridge/jvb.conf ?
aaronkvanmeerten
commented
4 months ago mapping.stun.enabled = false
You already have it disabled via the above.
aaronkvanmeerten
commented
4 months ago Jicofo 2024-06-03 13:27:04.568 WARNING: [51] BridgeSelector.selectBridge#182: There are no operational bridges.
Jicofo 2024-06-03 13:27:04.569 SEVERE: [51] [room=[test4@conference.jitsi.su.sd](mailto:test4@conference.jitsi.su.sd) meeting_id=b8f74b96-b226-4af6-99e2-3b91acc04b70 participant=6b67eccf] ParticipantInviteRunnable.doRun#218: Can not invite participant, no bridge available.This indicates that your bridge is not successfully configured to connect to your prosody, so your jicofo isn't finding it. How do you have the prosody configuration set up today in jvb.conf?
therock42
commented
4 months ago Jicofo 2024-06-03 13:27:04.568 WARNING: [51] BridgeSelector.selectBridge#182: There are no operational bridges. Jicofo 2024-06-03 13:27:04.569 SEVERE: [51] [room=[test4@conference.jitsi.su.sd](mailto:test4@conference.jitsi.su.sd) meeting_id=b8f74b96-b226-4af6-99e2-3b91acc04b70 participant=6b67eccf] ParticipantInviteRunnable.doRun#218: Can not invite participant, no bridge available.This indicates that your bridge is not successfully configured to connect to your prosody, so your jicofo isn't finding it. How do you have the prosody configuration set up today in jvb.conf?
i sent sudo nano /etc/jitsi/videobridge/jvb.conf above
aaronkvanmeerten
commented
4 months ago I believe you are missing the xmpp configuration. This should all have been configured by default via the debian installer during setup if you followed this one: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart/
so I'm not sure why you'd be missing it now. Can you send again the current contents of you sip-communicator.properties
therock42
commented
4 months ago I believe you are missing the xmpp configuration. This should all have been configured by default via the debian installer during setup if you followed this one: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart/
so I'm not sure why you'd be missing it now. Can you send again the current contents of you sip-communicator.properties
org.ice4j.ice.harvest.DISABLE_AWS_HARVESTER=true org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES= org.jitsi.videobridge.ENABLE_STATISTICS=true org.jitsi.videobridge.STATISTICS_TRANSPORT=muc org.jitsi.videobridge.xmpp.user.shard.HOSTNAME=localhost org.jitsi.videobridge.xmpp.user.shard.DOMAIN=auth.jitsi.su.sd org.jitsi.videobridge.xmpp.user.shard.USERNAME=jvb org.jitsi.videobridge.xmpp.user.shard.PASSWORD=dJvj4cCy org.jitsi.videobridge.xmpp.user.shard.MUC_JIDS=JvbBrewery@internal.auth.jitsi.s> org.jitsi.videobridge.xmpp.user.shard.MUC_NICKNAME=ae91069c-37e2-4b93-affd-c3c4> org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=192.168.1.38 org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=192.168.1.38
aaronkvanmeerten
commented
4 months ago this all looks correct to me then, can you restart your videobridge service with a sudo service jitsi-videobridge restart and see if that helps?
therock42
commented
4 months ago this all looks correct to me then, can you restart your videobridge service with a
sudo service jitsi-videobridge restartand see if that helps? i do it not solve i'm trying docker
therock42
commented
4 months ago
saghul
commented
4 months ago We don't recommend to use root for running your containers. At any rate, is it working?
therock42
commented
4 months ago We don't recommend to use root for running your containers. At any rate, is it working?
it isn't working
therock42
commented
4 months ago
For the Installation i have Internet Access. After that the Server is used offline in a LAN & I have local Domain. when end of installation I test it it's working fine but when test it offline it's not work when second person join to conference. when back it to access internet it's working .