@Alice (Alice Wang) posted a new topic, subject ""unfortunately something went wrong " and reconnecting". It read:

   i am having a problem on ->unfortunately something went wrong, we are trying to fix this, - i am a newbie
    
    os ubuntu 18.04

So @damencho (Damian Minkov) replied

    Hi and welcome.
    
    First open your js console in the browser and check what it the error you see when this happen.

Then @Urbanovits said

    Hi,
    
    I found this is a thipical symhtome lack of NAT or firewall settings. No transport channel opening between client and server on port UDP 10000 OR JVB did not find themself
    
    3 steps to check
    
    1., On public IP  
    Enable UDP port 10000
    
    2., On NAT  
    Edit/check your videobridge SIP config file /etc/jitsi/videobridge/sip-communicator.properties file  
    Add this lines at he end:  
    org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=xxx.xxx.xxx.xxx  
    org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=xxx.xxx.xxx.xxx  
    where xxx.xxx.xxx.xxx your internal and external P address
    
    orig source: https://github.com/jitsi/jitsi-meet/blob/maste/doc/quick-install.md#advanced-configuration
    
    3., Edit/check your videobridge config file /etc/jitsi/videobridge/config  
    modify your “JVB_HOST=” line  
    to  
    JVB_HOST=localhost  
    JVB_HOST=228-456-0398
    
    don't forget to restart your videobridge using /etc/init.d/jitsi-videobridge restart
    
    If you have same issue after applying settings above, ping “localhost” name and see the result. If you find IPv6 name resoultion reply, then go to /etc/hosts and comment out all of your IPv6 setting, so even kill all of your IPv6 services on JVB server.
    
    hope it is help

Then @Alice (Alice Wang) said

    thank you let me read through

@Alice (Alice Wang) replied

    Urbanovits:
    
    > Enable UDP port 10000
    
    i have done this - it didnt worked

@damencho (Damian Minkov) replied

    Did you check the console as I suggested above?

After which, @Alice (Alice Wang) added

    yes i shared a link for better understanding - i failed to decode what you want on the console. can you help me by visiting that link

@damencho (Damian Minkov) replied

    You always need to look at the first error you see, not the last. You error is `CONFERENCE FAILED: conference.focusDisconnected focus.live.sasai.xyz 1`. Jicofo is not running or not connected, check its logs.

Then @DanielWahl (Daniel Wahl) said

    Hey guys,
    
    I've installed Jitsi today on my Ubuntu 18 Server and I'm facing the same issue.  
    I also get the “Conference failed: converende.focusDisconneted …” error in my console.
    
    Furthermore, my jicofo troughs the following error every second:
    
    > Jicofo 2020-04-07 17:52:18.203 SEVERE: [33] org.jitsi.meet.ComponentMain.log() not-authorized, host:xmpp.meet.jitsi, port:5347  
    >  org.xmpp.component.ComponentException: not-authorized  
    >  at org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:243)  
    >  at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:242)  
    >  at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:222)  
    >  at org.jitsi.meet.ComponentMain.lambda$getConnectCallable$0(ComponentMain.java:285)  
    >  at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)  
    >  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)  
    >  at java.util.concurrent.FutureTask.run(FutureTask.java:266)  
    >  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)  
    >  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)  
    >  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)  
    >  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)  
    >  at java.lang.Thread.run(Thread.java:748)
    
    My UDP 1000 port is open.
    
    Has someone found a fix for this problem?
    
    Thanks in advance

After which, @papakojo (Papakojo) added

    restart these items:  
    sudo systemctl restart prosody  
    sudo systemctl restart jicofo  
    sudo systemctl restart jitsi-videobridge2
    
    Worked for me

To which @NLDer (Andrew Salm) replied

    A quick note…
    
    If you are using cloudflare, or another proxy capable DNS service, make sure that your cname for jitsi is NOT being proxied. Leave, or set it, to DNS only, and point it to your A record, or your DNS updated, like duckdns or the like.
    
    Proxying this conference through a place such as cloudflare will cause this problem to occur.

After which, @carlo_merola (carlo merola) added

    me it happend too, but if you try to reset your internet connection this is will fix. If I follow this procedure at least it works for me

After which, @Vignesh_Chinnaiyan (Vignesh Chinnaiyan) added

    This Worked for me. Thanks.

Then @Ponraj_Perumal (Ponraj Perumal) said

    I am also facing the same issue. how to solve this issue ?

Then @vishwanath_nijampurk (vishwanath nijampurkar) said

    even i have the same issue but sometimes not regular after showing this error ill just re-start the server prosody videobridge ect then it will work fine but why its coming sometimes also can anyone know how to solve it?

To which @sor2000 (Sor) replied

    I just had this issue and @Urbanovits 3rd step helped but I did it differently.  
    I did not want to touch the default install videobridge file “/etc/jitsi/videobridge/config” so instead I edited the “/etc/hosts” and added this line “228-456-0398 example.domain.com” this way if any other application is set to look for default localhost it will point to itself.
    
    I compared these settings with my live server.

@VishalKale (Vishal) replied

    Hi All,
    
    I uninstalled the JITSI and tried the fresh install using the article: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart
    
    I have also set a domain and advance configuration but getting this “unfortunately, something went wrong” issue when the second user joins the call.
    
    I tried the solution posted here: https://github.com/jitsi/jitsi-meet/issues/5696  
    But it didn't help.
    
    I also tried the solution posted by @kitsis here: Room crashes when anyone trys to join  
    But still, it's not working, getting the below error when second users join the call.
    
    Screenshot navarrosamantha@example.net PM1438×780 272 KB
    
    How to fix this?

@rpositronic (Positronic) replied

    Worked for me. Thanks!

@Manjunath_P (Manjunath P) replied

    This solution didnt work for me

Then @cessariuss said

    thank you!!  
    These settings solved my problem.

Then @Krati (Krati) said

    @VishalKale has your issue resolved?  
    I an also getting the same issue

So @Krati (Krati) replied

    Hi @damencho,  
    I have installed latest jitsi version on my server “” and whenever I am joining the conference after 20-30 seconds I'm getting error “Unfortunately something went wrong. We are trying to fix this. Reconnecting in 17 seconds”
    
    Earlier when I was working with previous versions I never faced this issue but since I have updated the version I'm getting such error.
    
    Please guide for the same.  
    Since I'm getting such issue, I have tried fresh installation in different servers aswell but still facing the same issue.

To which @corby (🇺🇸) replied

    @Krati
    
    Is port 10000 accessible? See Tip: how to check UDP/10000 connectivity for a quick test
    
    Do you see errors in the jifoco log? Or the JVB log?
    
    Since you are seeing this on different servers and with fresh installs it's likely not related to the code but the configuration of either the servers or your client.

After which, @Krati (Krati) added

    Hi @corby  
    Thanks for your reply
    
    I am attaching jicofo an jvb log files:  
    jvb.log (2.2 MB) jicofo.log (277.0 KB)
    
    in jvb log file there is one line
    
    2020-08-05 06:31:12.354 INFO: [7275] [confId=9aa921d00bf19cc8 gid=162057 stats_id=Wilfredo-2Cn conf_name=qwerty ufrag=ce68h1eeul21t0 epId=6c8f521c local_ufrag=ce68h1eeul21t0] ConnectivityCheckClient$PaceMaker.run#922: Pair failed: 228-456-0398:10000/udp/host -> 228-456-0398:59966/udp/host (stream-6c8f521c.RTP)
    
    is this some what error? As in previous lines pair is added and after that pair failed issue is present

Then @gpatel-fr said

    Krati:
    
    > Pair failed: 228-456-0398:10000/udp/host -> 228-456-0398:59966/udp/host (stream-6c8f521c.RTP)
    > 
    > is this some what error? As in previous lines pair is added and after that pair failed issue is present
    
    By itself having ‘pair failed' in the log is not an error, when it is followed by a message about ‘pair succeeded'. If it's not, there is probably a problem; as 10.1.0.x is a private IP address, look for
    [code] 
        org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=...your private IP address ...
        org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=... your public IP address ...
        
    [/code]
    
    in the /etc/jitsi/videobridge/sip-communicator.properties file. When there is a pair succeeded message, it will be with your public IP address.

After which, @Krati (Krati) added

    @gpatel-fr that means “Pair failed” is not an error as earlier there was “pair succeeded” message present.
    
    So as per you i need to check my private and public ip address in /etc/jitsi/videobridge/sip-communicator.properties file right?
    
    So below is my .properties file:
    
    org.ice4j.ice.harvest.DISABLE_AWS_HARVESTER=true  
    org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES=meet-jit-si-turnrelay.jitsi.net:443  
    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.webrtc.centralindia.cloudapp.azure.com  
    org.jitsi.videobridge.xmpp.user.shard.USERNAME=jvb  
    org.jitsi.videobridge.xmpp.user.shard.PASSWORD=JW9YrSde  
    navarrosamantha@example.net  
    org.jitsi.videobridge.xmpp.user.shard.MUC_NICKNAME=9fbb28eb-e363-4845-9539-b2fd1389e1f5

Then @gpatel-fr said

    Krati:
    
    > that means “Pair failed” is not an error as earlier there was “pair succeeded” message present.
    
    That's not exactly what I said. If things work, you can have any number of pair failed messages, **followed** by a pair succeeded and a pair validated message. If after a pair failed message you have other error messages instead, it's not good and in this case you may have better success in including the lines in your sip-communicator.properties.

After which, @Krati (Krati) added

    @gpatel-fr I have added the public and private ip address in .properties file but found nothing in log files by which I can come to conclusion that why I am facing “something went wrong” issue

So @gpatel-fr replied

    is the parameter taken in account ? that is, is running  
    sudo grep LOCAL_ADDRESS /var/log/jitsi/jvb.log  
    returning something along the lines of:
    [code] 
        2020-08-04 09:11:40.686 INFO: [1] AbstractReadOnlyConfigurationService.logConfigurationProperties#85: org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS =...the private address ...
        
    [/code]
    
    and similar for PUBLIC_ADDRESS
    
    and is the log with pair failed exactly the same or are there changes ?

To which @Krati (Krati) replied

    gpatel-fr:
    
    > sudo grep LOCAL_ADDRESS /var/log/jitsi/jvb.log
    
    I tried executing the command :  
    grep LOCAL_ADDRESS /var/log/jitsi/jvb.log  
    grep PUBLIC_ADDRESS /var/log/jitsi/jvb.log
    
    but didn't get any response.
    
    NOTE: in the place the LOCAL_ADDRESS I have used my private ip address

@corby (🇺🇸) replied

    Can you show us the output of `sudo netstat -anlp | grep 10000`

To which @Krati (Krati) replied

    corby:
    
    > udo netstat -anlp | grep 10000
    
    below is the output:
    
    udp6 0 0 228-456-0398:10000 8b7c:f320:99b9:690f:4595:cd17:293a:c069:* 7930/java

After which, @corby (🇺🇸) added

    That seems like a problem to me. The `10.0..` network is a private address. UDP port 10000 is not listening on any public IP address (if that's all you see from netstat)

Then @Krati (Krati) said

    At my end UDP port 10000 is open as you can see the status below:  
    sudo ufw status verbose
    
    Status: active  
    Logging: on (low)  
    Default: deny (incoming), allow (outgoing), disabled (routed)  
    New profiles: skip
    
    To Action From
    
    * * *
    
    80/tcp ALLOW IN Anywhere  
    443/tcp ALLOW IN Anywhere  
    4443/tcp ALLOW IN Anywhere  
    10000/udp ALLOW IN Anywhere  
    22/tcp ALLOW IN Anywhere  
    80/tcp (v6) ALLOW IN Anywhere (v6)  
    443/tcp (v6) ALLOW IN Anywhere (v6)  
    4443/tcp (v6) ALLOW IN Anywhere (v6)  
    10000/udp (v6) ALLOW IN Anywhere (v6)  
    22/tcp (v6) ALLOW IN Anywhere (v6)

To which @corby (🇺🇸) replied

    I see. When some people run `nc -l 10000` (as sometimes suggested) they are actually listening on port 10000 (on all addresses). This could lead to a false positive. It does verify the firewall, but not the jvb. I believe using ngrep is a better solution
    
    Just because it's open (which is good, you need that) it doesn't mean is working.
    
    > Your JVB is not actually _listening_ on port 10000 in a reachable way.
    
    Unless there is some other routing/forwarding/masquerading going on in` iptables` that I am not aware of on your system (and there may be) I don't believe this will work.
    
    You need to have your JVB bind to UDP 10000 on an IP address that is reachable – either directly by the meeting participants or indirectly through a relay /TURN. Others can correct me where I am wrong.

So @gpatel-fr replied

    Krati:
    
    > in the place the LOCAL_ADDRESS I have used my private ip address
    
    no  it was really LOCAL_ADDRESS

So @Krati (Krati) replied

    Krati:
    
    > grep LOCAL_ADDRESS /var/log/jitsi/jvb.log
    
    Thanks you so much for your quick response and guidance.  
    It really helped me to look deep into this issue.
    
    I was verifying the enabled ports from ubuntu and now I enabled 10000 port for network firewall from cloud console and now its working

@corby (🇺🇸) replied

    Excellent! Glad we could help you!

To which @Girdhar (Girdhar Soni) replied

    Hii @VishalKale once follow these steps
    
      1. check your 10000 UDP and 4443 TCP port , these should be opened.
      2. Open this file **/etc/jitsi/videobridge/sip-communicator.properties** and uncomment this line  
    **org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES=meet-jit-si-turnrelay.jitsi.net:443**
      3. And add this  
    org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS= put here your local ip address  
    org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=put here your public ip address.
    
    
    
    Then restart **prosody, jicofo, jitsi-videobridge2.**
    
    Happy coding

After which, @corby (🇺🇸) added

    For others that find their way here, check our this “how to” that addresses this common scenario:
    
    [How to] Why do I see "Unfortunately something went wrong"? Why does my room 'crash'? Install & Config
    
    > “Unfortunately something went wrong”  This is one of the most common issues users face when installing a new self-hosted Jitsi Meet server UDP Port 10000 This is usually related to UDP port 10000 not being accessable by the participant's device. Access to this port is critical because it is used for all video/audio communications. The first thing to try is Tip: how to check UDP/10000 connectivity. More on Port 10000The JVB port is set to 10000 by default, but may be…

To which @innovation (Conference expert) replied

    Hello
    
    My all classes students got reloaded with “unfortulately something went wrong” . What could be the issue. What we should look into.
    
    thanks

So @damencho (Damian Minkov) replied

    Get the js console logs when this happens before the page reloads.

After which, @innovation (Conference expert) added

    How to get this now… as it has happened and reconnected… any change to navarrosamantha@example.net. We dont want this to happen again… Its on premise deployment.

To which @damencho (Damian Minkov) replied

    This is in developer tools in the browser - Console, right clicking in the logs area there is an option to save the file.  
    Attach the log with the problem.

Then @innovation (Conference expert) said

    E2E ping failed error. What could be the issue as other class at the same time is working

@Mohan_Bhombe (mohanRB) replied

    papakojo:
    
    > sudo systemctl restart jicofo
    
    I am getting the same issue  
    my jicoff log  
    
    
    image1920×960 105 KB
    
      
    
    
    image1907×755 86.6 KB

Then @Freddie said

    Looks like you have a wrong password/secret.

So @saqibomer (Saqib) replied

    papakojo:
    
    > sudo systemctl restart jitsi-videobridge2
    
    This worked for me


{'source': 'discourse', 'url': 'https://community.jitsi.org/t/unfortunately-something-went-wrong-and-reconnecting/17835', 'title': '"unfortunately something went wrong " and reconnecting', 'views': 16624, 'has_accepted_answer': False, 'word_count': 2498, 'like_count': 3, 'reply_count': 41, 'participant_count': 23, 'posts': 48, 'tags': 'meet', 'author': '@Alice (Alice Wang)', 'participants': '@Alice (Alice Wang), @damencho (Damian Minkov), @Urbanovits, @DanielWahl (Daniel Wahl), @papakojo (Papakojo), @NLDer (Andrew Salm), @carlo_merola (carlo merola), @Vignesh_Chinnaiyan (Vignesh Chinnaiyan), @Ponraj_Perumal (Ponraj Perumal), @vishwanath_nijampurk (vishwanath nijampurkar), @sor2000 (Sor), @VishalKale (Vishal), @rpositronic (Positronic), @Manjunath_P (Manjunath P), @cessariuss, @Krati (Krati), @corby (🇺🇸), @gpatel-fr, @Girdhar (Girdhar Soni), @innovation (Conference expert), @Mohan_Bhombe (mohanRB), @Freddie, @saqibomer (Saqib)', 'image_url': [None], 'created_at': '2019-05-01T06:34:04.783Z', 'last_posted_at': '2022-01-06T13:19:01.005Z'}