Jitsi meet can't talk, can't change nickname, keeps disconnecting

Hi,
I’m trying to install jitsi (with qc instructions) on custom port on ip address (I’ve tried on domain but I couldn’t make it work)
Once everything was installed I configured NAT then routing (100 -> 100 TCP and 10000 -> 10000 UDP).
After instalation I can see


Everything seems to be fine but I can’t unmute (permission is granted) I can’t change my nickname, after some time I got disconnected

I didn’t change anything after installation (only NAT was changed)

I can’t send attachments so here’s pastebin links

sip-communicator.properties https://pastebin.com/z3JspPag
jicofo.log https://pastebin.com/1pYGHnsG

jvb.log https://pastebin.com/MVtWDW5K
Chrome logs https://pastebin.com/pQJg8Vjd

I have the same problem. Can not un-mute, and in a little while get disconnected. I did this on two separate ubuntu systems with the same result. My guess is that the installation instructions are making some un-stated assumptions about the environment.

Jicofo 2020-03-16 06:48:12.832 SEVERE: [16] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.doConnect().309 Failed to connect/login: host-unknown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
<stream:error><host-unknown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text>This server does not serve auth.xx.xxx.xxx.xx</text></stream:error>
org.jivesoftware.smack.XMPPException$StreamErrorException: host-unknown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
<stream:error><host-unknown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text>This server does not serve auth.xx.xxx.xxx.xx</text></stream:error>
    at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1059)
    at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
    at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
    at java.lang.Thread.run(Thread.java:748)

You have a problem with your prosody config that jicofo is trying to use.
Apparently you fixed that at some point and then you just get errors for the jvb:

 Jicofo 2020-03-16 06:51:09.976 SEVERE: [29] org.jitsi.jicofo.discovery.DiscoveryUtil.discoverVersion().200 Failed to discover version, req: <iq to='jitsi-videobridge.xx.xxx.xxx.xx' id='apjAJ-44' type='get'><query xmlns='jabber:iq:version'></query></iq>, response: <iq to='focus@auth.xx.xxx.xxx.xx/focus4573682691' from='jitsi-videobridge.xx.xxx.xxx.xx' id='apjAJ-44' type='error'><error type='cancel'><service-unavailable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>

Check jvb logs.

I am starting to suspect that the name that is given during installation must already be set up in DNS before starting installation. This is not mentioned in the documentation. The installation procedure also starts the jitsi service running, and that will fail if the name can not be resolved.

Also, very annoying, is that ‘apt purge’ does not clean everything up. In particular, enough config information is left behind that if you try to re-install, it thinks you have already answered the ‘name’ question and does not give you a chance to put in a different one. I have not been able to find where it hides this information.

We hat a similar problem, but it now seems to work after we restarted the Docker container.

For uninstall follow the uninstall section in https://jitsi.org/qi

That was UDP forwarding (10000 to 20000) problem and 443 port forwarding. I had routing external port 444 and internal 443. Client didn’t have connection to jitsi videobridge

Looking at my browser developer log after one of these ‘disconnected’ incidents, I can see that the browser is trying to connect to the name that was given during the Jitsi installation procedure. What this means is that the name you put in that box during installation must be the permanent domain name of your server. This is very important, as that name gets sprinkled all through the various configuration files and there is no way to change it later.

So it has to be either a static IP address or a domain name that you control. It could be a name you registered at one of the Dynamic DNS service, or it could be a name chosen for this purpose and registered at Namecheap or one of the other DNS registration services. Or both: make the registered name have a CNAME record pointing to your Dynamic DNS name, as this will allow you to point it somewhere else in the future without changing the name your clients know.

I currently have a jitsi meet installation running on AWS but it gets this disconnect error because the domain name I configured it for, and registered, has not yet propagated to all the world’s DNS servers, a process that can take 48 hours. AND you can not do the final installation step of replacing the self-signed certificate with a letsencrypt one until that domain name is working.

I verified that this is the case by faking out my local desktop machine by putting an entry in /etc/hosts that points directly to my AWS instance.