Sync Timeout: No path to relay

[Vider06]

I am currently connected to 1 relay , 1 hop of distance, and when I try to sync recent messages the first time it says: Sync Timeout: No path to relay, the other times sync timeout.

[serialrf433]

This is not a helpful issue report.
How should people try to reproduce and fix this problem when you do not even publish the ID of the relay you are having issues with?
How should people know what Columba version you are using and what OS version you are using in onto when you do not share any of those information?

It would be the same like when i open a issue report on a webbrowser, do not tell the browser version and the OS i am using, and say 'when i try to visit one website, it fails'.
I hope you understand on your own that the issue report how you wrote it is not helpful.

[Vider06]

Sorry, Imma give everything here.
Columba 0.9.19 (919000)
Build: 8f30c12 (2026-03-12 05:00)
Android 16 (API 36)
Device: SM-A346B by samsung
Reticulum: 1.1.3
LXMF: 0.9.2
BLE-Reticulum: 0.2.2
Destinwtion Hash: 0644032081ec4c00a0114c648214de30

[serialrf433]

I can sort of reproduce the error. But the relay you are using ( 0644032081ec4c00a0114c648214de30 ) is also a bit strange. It seems to be broken. When you get the no path issue, then you was not able to reach the relay. But when the sync time outs, then you was able to reach it but it was not functional.

Some further investigation is required. Sadly the other people asked to also test and report their experience with the relay do not liked to spend time into testing it.

Is this a relay you have chosen manual or had Columba chosen it automaticly because of the low hop count to the relay?

You can choose a different relay to not continue to have issues with your current relay.