This article provides instructions on explicitly configuring your Ditto instance to listen for connections on a specific port and to connect to remote instances using a host (IP) and port. 

Although Ditto automatically attempts to connect to other instances on the Local Area Network (LAN), Bluetooth Low Energy (LE), and Apple Wireless Direct Link (AWDL), supplying a 

ou manually enable peer-to-peer connections using 

You can enable and disable transport protocols for all connected Small Peers by doing either of the following. 

If you need additional connection configurations for the current Ditto instance, configure it to listen for connections on a specific port and to connect to remote instances using a host (IP) and port:

The Big Peer generates certificates automatically for each Small Peer. A certificate involves an expiration date and AppID, among other credentials. Read more here about how it works.

In order to sync with other devices, a peer must connect to the Big Peer at least once. To do this, you must use either 

We recommend using OnlinePlayground for development and OnlineWithAuthentication for production apps. If you only want to use the Big Peer for authentication without syncing to the cloud, you can use 

If you know the host and port of another remote Ditto peer and would like to connect to it, construct a 

 separated by a colon, add the host and port to the 

For example, the following indicates there are two other Small Peers known to Ditto and provides details of their network locations, including the IP addresses and port numbers associated with each peer:

Ensure WebSocket connections are discoverable across peers within your local network: 

You can enable the Ditto instance to listen for incoming connections from other remotes Ditto peers on a specific port. You can think of this as setting up your Ditto as a "server" that can listen to connections from other peers.

In this example, we would like our Ditto instance to listen to 

Incoming connections from other Ditto peers will be able to connect only if the port is accessible. Depending on your deployment 

be sure to check that external connections can reach the port

 that you have specified in your configuration. You may need to set up port forwarding if external ports map differently to your host.

You can specify several modes of transport configuration within 

. The following snippet shows you a ditto instance that can:

If syncing over Bluetooth LE is a critical part of your application you may want to warn the user if they are missing the permission or if the hardware is disabled. Ditto will help you by reporting conditions via a delegate or callback object.

First, while configuring Ditto, assign a delegate or a callback to receive notifications.

Using Mesh Presence

Customizing Transports Configurations

linux_aarm_supported_version

android_supported_version

ipados_supported_version

ios_supported_version

windows_x64_supported_version

mac_supported_version

linux_x64_supported_version

Managing Redundant Bluetooth LE Connections

Using ALTER SYSTEM

ditto

Where you get expert information for building cloud‑optional apps using Ditto.

SDK v4.7

Welcome to Ditto Docs - V4.7

Sync Credentials

Swift

Kotlin

JavaScript Web

Node.js

React Native

Java

Rust

Flutter beta

Customizing Transports Configurations

Enabling and Disabling Transports

Configuring Additional Settings

Syncing with Big Peer

Connecting to Remote Small Peers

Initializing WebSocket Connections

Listening for Connections

Combining Multiple Transports

Monitoring Conditions