Outgoing federation request had an invalid signature for dimka511.pp.ua

Matrix Connectivity Tester Support
1

Hi!

The tested server is dimka511.pp.ua.

First of all, thank you for creating the Matrix Connectivity Tester. It has been very useful while setting up my homeserver.

I’m running Tuwunel 1.8.2, and the report shows the following warning:

Outgoing federation request had an invalid signature

This server did reach us, but the request wasn’t validly signed with its own current key — check for significant clock skew, or a signing key that doesn’t match what /_matrix/key/v2/server currently publishes.

However, everything else appears to be healthy:

  • Federation: OK

  • All tested IP addresses pass TLS and Ed25519 verification.

  • /_matrix/key/v2/server publishes the expected signing key.

  • The tester reports MatchingSignature: true and ValidEd25519: true for every tested address.

  • The homeserver successfully reaches your server (ReceivedIncomingRequest: true).

I’m trying to understand exactly what this warning means.

Could you clarify:

  1. Which outgoing request is being verified?

  2. Which signature is considered invalid?

  3. Is this signature expected to match the key published by /_matrix/key/v2/server, or is a different signature being checked?

  4. Are there common causes for this warning besides clock skew or an incorrect signing key?

  5. Could this be a false positive or an issue in the tester?

If additional logs or diagnostic information would be useful, I’d be happy to provide them.

Thanks for your help!

3

Hi :slight_smile:

It seems you actually hit a bug in the my code.
I fixed this now and it should now work again. Your server seems to be perfectly healthy.

Sorry for the hassle :slight_smile: