Master replied with a UUID we don't understand

[CanRau]

Describe the bug

I just started using KeyDB and am not exactly sure if this is a bug, as everything seems to be fine, I've ssh'd into both machines and they seem to have the same state, also in the last line it reads (Non critical) so not sure what to make of those messages, just want to understand if and how to fix this or if it's expected/ok in certain scenarios?

Also those log blocks are repeated, they seem to have stopped at the moment but are basically continuous.

Both leaders log

# Master replied with a UUID we don't understand
* Connecting to MASTER fdaa:2:e2b:a7b:bada:d647:d3b1:2:6379
* MASTER <-> REPLICA sync started
* Non blocking connect for SYNC fired the event.
* Master replied to PING, replication can continue...
* (Non critical) Master does not understand REPLCONF listening-port: -Reading from master: Connection timed out

To reproduce

I've set the 2 instances in 2 different regions on fly.io according to this repo https://github.com/fly-apps/keydb

this is my complete keydb.conf

dir /data/ 
protected-mode no 
appendonly yes
save 900 1
save 300 10
save 60 10000
active-replica yes
replica-read-only no
multi-master yes
replica-serve-stale-data yes
maxmemory-policy noeviction

though I got the same with the original conf from the repo

[msotheeswaran-sc]

What version of KeyDB are each of the servers?

[CanRau]

eqalpha/keydb:x86_64_v6.3.3, deployed via fly.io they create multiple instances off of the same Dockerfile

let me know what else I can supply to help

[msotheeswaran-sc]

The log means that there was an issue sending the port the replica is running on to the master, however the master doesn't need this information, it is only used to log out where replicas are running, so if that is not necessary information for you there is no concern.