Outgoing federation check: target never reached us back

Matrix Connectivity Tester Support
1

Hi!

Since August 17th 17:40, my home server is in a down/recovered loop every 45 minutes or so.

Message from service:

outgoing federation check: target never reached us back (no incoming callback received)

My continuwuity server log shows:

août 22 11:57:29 belette64 conduwuit[2196819]: 2026-08-22T09:57:29.807136Z  WARN conduwuit_api::router::auth: Failed to extract authorization: no access token found, but this endpoint requires one
août 22 11:57:30 belette64 conduwuit[2196819]:   2026-08-22T09:57:30.569951Z ERROR conduwuit_service::rooms::alias::remote: Unable to resolve remote room alias #VY58oafRwm8nFxGH:v4.connectivity-tester.mtrnord.blog: Remote server v4.connectivity-tester.mtrnord.blog responded with: [404 / M_NOT_FOUND] Room alias not found.
août 22 11:57:30 belette64 conduwuit[2196819]:     at src/service/rooms/alias/remote.rs:18 on conduwuit:worker ThreadId(3)
août 22 11:57:30 belette64 conduwuit[2196819]:     in conduwuit_service::rooms::alias::resolve with room_alias="#VY58oafRwm8nFxGH:v4.connectivity-tester.mtrnord.blog"
août 22 11:57:30 belette64 conduwuit[2196819]:   2026-08-22T09:57:30.576136Z ERROR conduwuit_service::rooms::alias::remote: Unable to resolve remote room alias #E881jg32Jl4BEheS:v6.connectivity-tester.mtrnord.blog: Remote server v6.connectivity-tester.mtrnord.blog responded with: [404 / M_NOT_FOUND] Room alias not found.
août 22 11:57:30 belette64 conduwuit[2196819]:     at src/service/rooms/alias/remote.rs:18 on conduwuit:worker ThreadId(3)
août 22 11:57:30 belette64 conduwuit[2196819]:     in conduwuit_service::rooms::alias::resolve with room_alias="#E881jg32Jl4BEheS:v6.connectivity-tester.mtrnord.blog"

Last upgrade on my server was made on 15th, so nothing changed between 15th and 17th.

Is there someting I can report? Each time I go to the online webpage, everything’s fine.

3

I think its a problem in my code. In that timeframe I changed how outgoing federation works and how the alert thresholds work to get a more stable result. But a side effect of this is that some servers seem to not work well with that. I am going to take today to hopefully improve/rewrite the logic for this. I will report back when I get a fix out. Sorry for the inconvenience!

4

I reworked the code now and it should have stopped happening now. If there are any further issues please report them again :slight_smile: