Jami Not Receiving Messages When Using Some Networks


In summary, many new Jami users are facing this same challenge. This is actually one of the most frequent challenge. In summary, when using some networks, Jami successfully send & receive messages. But when using some other networks, Jami failed to receive messages. All the above using both the same devices & same Jami configuration.

Below are the steps to reproduce this challenge, the likely cause of this challenge, and two suggested resolutions.

Steps to reproduce

  1. Install Jami Desktop version Maloya 202106****** on two devices

  2. Using your network, let’s call it Network 1, sending & receiving messages back & forth is successful between those two devices.

  3. Using the same two devices, use a different network. Let’s call it Network 2. For example, use:

    • Friends’ network
    • Office network
    • Free wireless network in a store

    Do not make any change to the configuration of Jami on your two devices. But double check that you use a different network.

  4. When using some other networks, sending & receiving messages failed between those two devices. The 1st device says that the message was sent. But the 2nd device never receives the message. This is the challenge.

  5. Go back to using your Network 1. Sending & receiving messages back & forth is successful between those same two devices. Same configuration with Jami. No change. So it seems that the challenge is related to some network.


The likely cause of this challenge is that some networks are configured properly to allow Peer-To-Peer communication (P2P) connection. But other networks are not. For Jami to work properly, the network need to be configured appropriately to allow P2P connections.


To resolve this challenge, choose one of the following two options. In summary, the option 1 below is quick and easy, but with weaker privacy. You simply need to activate the free Jami OpenDHT. The option 2 below is very long and hard, but with strong privacy. As you need to install and configure your own OpenDHT server.

Option 1: Free OpenDHT


  1. Reminder:

    • This option 1 is quick and easy. Because you simply need to flip a switch within your Jami configuration. Easy :slight_smile: The challenge with this option 1 is that it’s weaker privacy, than the other option 2 below. Optionally, you could start with this present option 1. Then, in the future, switch to option 2. Or, depending on the context, switch between options 1 and 2. Below are the steps for activating option 1.

    • Jami has a free built-in optional feature called OpenDHT. Which is a free proxy server offered by Jamie. Which receive your IM than pass them on to your recipient. In turn, after your recipient receive your IM, he/she could choose to either send her reply directly to you or through any OpenDHT server to her/his liking. By default, the OpenDHT feature is deactivated in your Jami client.

  2. Using your Jami client for desktop. Select your appropriate Jami Ring account. Click on this setting button.
    This screenshot shows this button.

  3. Click on this “Account” horizontal tab button

  4. Click on this “Advanced settings” group to expend it

  5. Under “OpenDHT configuration” group. Activate this “Proxy”. This activates your device connection with the free Jami OpenDHT server.

  6. Still within this “OpenDHT configuration” group. Double check that your configuration are correct. If somehow your “OpenDHT configuration” are either missing or changed in good faith. Here are the correct default configuration values if you choose to use the free Jami OpenDHT server. The values in text format are:

    • “Proxy”: dhtproxy.jami.net:[80-95]
    • “Auto connect on local network”: ACTIVATED
    • “Bootstrap”: bootstrap.jami.net
  7. No need to restart your Jami. Within the next 1 to 2 minutes, you should receive any send message (IM).

    • If you do not receive any IM, try one of the following two sub-options:

      • Sub-option 1: Try to send a new IM message
      • Sub-option 2: Using the other device, using Jami, also activate the connection to the free Jami OpenDHT server.
    • Note: OpenDHT might resolve connection challenge. Because your IM message is send from your local network to the OpenDHT server. Then in turn from the OpenDHT server to your recipient. Similar to what Skype does. This is weaker privacy. But less risky to result in connection challenge. Speaking for myself. I trust the Jami OpenDHT server as it’s both owned and operated by Jami themselves. The benefit with Jami is that you’re free to choose between using P2P or a proxy OpenDHT server. Compare to Skype where they force you to use their proxy closed source server :frowning:

  8. If you installed Jami on multiple devices. For example, your mobile, your tablet, and your desktop. And if any one of those devices is not receiving Jami messages. Then you need to redo all the above steps for each device. This is a one time configuration.

    • Note:

      • One benefit with Jami is that you can customize this configuration per device.
  9. If you have multiple Jami Ring account. For example, one account for work, one account per client, plus a personal account. Then you need to redo all the above steps for each Jami Ring account. This is a one time configuration.

    • Note:

      • Another benefit with Jami is that you can customize each Jami Ring account to your liking.
      • Jami automatically synchronize your account(s) configuration across all your devices. Easy :slight_smile:
  10. Done. You have successfully activated Jami OpenDHT. Enjoy :slight_smile:

Option 2: Self-Hosted OpenDHT


  1. This second option is very long and hard. Because System Administrator skills are required. If you do have System Administrator skills, then the benefit of this 2nd option is that your Jami communications would be with very strong privacy.

  2. Use this documentation to install & configure you own self-hosted OpenDHT server at https://github.com/savoirfairelinux/opendht/wiki

  3. Related comment at https://forum.jami.net/t/anonymat-sur-jami/516/28


Why did I create this discussion, then answered myself?
So that in the future, it’s quick and easy to share this information. As this challenge is by far the most frequently faced challenge by newcomers to Jami.

Why did I not contribute those resolutions to this Jami documentation at https://docs.jami.net ?
This sounds like a great idea. I’ll be happy to try that when I’m available

1 Like

Hi @jimdunn :slight_smile: My replies are inline below

It’s a cool idea… but just a geek toy… not ready for prime time production use.

Maybe my previous message was not clear? Here is a shorter version of my reply below.

I put Jami on 2 of my phones, and could send msgs back and forth. But, as soon as one phone was across town from the other, issues… either no messages received (although they appeared to send; tried from both phones).

Thanks again for sharing your experience with Jami

One easy and quick way to resolve this challenge is to simply activate this Jami OpenDHT.

Today I simplified my previous message. If my previous message was clear. But flipping an off & on switch is presently outside your comfort zone. Then Jami might not be a good match for your present needs. If flipping a switch is within your comfort zone, and you’re interested to try it. I would love to hear your test result, if this is of interest to you.

Just to let you know, most users who complain are Jami users on Android devices -, On Android if you enable DHT proxy server (which seems to be the default setting when the app is installed) the messages don’t get delivered instantly nor calls get connected, the simple solution would be to try without DHT proxy server to start with.


Thanks @krishnak for sharing your finding :slight_smile: