Two Defguard instances issue

[Tenta-dev]

Hi,

We currently have two Defguard instances, each for a different site.

Adding the first instance using the one-click configuration works as expected. However, when I try to add the second instance, nothing happens, and the following log is produced:

[2026-01-12][08:51:06.295739658][INFO][tracing::span] read_socket;
[2026-01-12][08:51:06.295821619][INFO][zbus::object_server] dispatch_call; msg=Msg { type: MethodCall, serial: 6, sender: UniqueName(":1.227"), path: ObjectPath("/org/net_defguard/SingleInstance"), iface: InterfaceName("org.SingleInstance.DBus"), member: MemberName("ExecuteCallback"), body: Structure(Dynamic { fields: [Array(Dynamic { child: Str }), Str] }), fds: [] } hdr=Header { primary: PrimaryHeader { endian_sig: Little, msg_type: MethodCall, flags: BitFlags<Flags>(0b0), protocol_version: 1, body_len: 161, serial_num: 6 }, fields: Fields { path: Some(ObjectPath("/org/net_defguard/SingleInstance")), interface: Some(InterfaceName("org.SingleInstance.DBus")), member: Some(MemberName("ExecuteCallback")), error_name: None, reply_serial: None, destination: Some(BusName::WellKnown("org.net_defguard.SingleInstance")), sender: Some(UniqueName(":1.227")), signature: Structure(Dynamic { fields: [Array(Dynamic { child: Str }), Str] }), unix_fds: None } }
[2026-01-12][08:51:16.533910457][INFO][defguard_client::enterprise::periodic::config] Automatically retrieved the newest instance configuration from core for 1 instances, sleeping for 30s
[2026-01-12][08:51:46.68196741][INFO][defguard_client::enterprise::periodic::config] Automatically retrieved the newest instance configuration from core for 1 instances, sleeping for 30s
[2026-01-12][08:51:56.113807931][INFO][tracing::span] read_socket;
[2026-01-12][08:51:56.113891869][INFO][zbus::object_server] dispatch_call; msg=Msg { type: MethodCall, serial: 6, sender: UniqueName(":1.232"), path: ObjectPath("/org/net_defguard/SingleInstance"), iface: InterfaceName("org.SingleInstance.DBus"), member: MemberName("ExecuteCallback"), body: Structure(Dynamic { fields: [Array(Dynamic { child: Str }), Str] }), fds: [] } hdr=Header { primary: PrimaryHeader { endian_sig: Little, msg_type: MethodCall, flags: BitFlags<Flags>(0b0), protocol_version: 1, body_len: 161, serial_num: 6 }, fields: Fields { path: Some(ObjectPath("/org/net_defguard/SingleInstance")), interface: Some(InterfaceName("org.SingleInstance.DBus")), member: Some(MemberName("ExecuteCallback")), error_name: None, reply_serial: None, destination: Some(BusName::WellKnown("org.net_defguard.SingleInstance")), sender: Some(UniqueName(":1.232")), signature: Structure(Dynamic { fields: [Array(Dynamic { child: Str }), Str] }), unix_fds: None } }

When I manually add the second instance, it works. However, when both instances are connected, the second one has trouble retrieving the network data and disconnects after the configured timeout. This issue always affects the instance that is connected second.

For example:
We have instance 1 “INT” and instance 2 “RCT”. If I connect to instance 1 first and instance 2 second, the RCT instance is the one that struggles. If I connect to instance 2 first and instance 1 second, then the INT instance struggles.

This occurs on both Linux and Windows clients.

In the future, we are going to have three instances.

Best regards