Failed to join #continuwuity:continuwuity.org #1737

New issue

Open

opened 2026-05-05 20:29:46 +00:00 by Esjott · 3 comments

Esjott commented

2026-05-05 20:29:46 +00:00

Hi there,

after some small break I tried to join #continuwuity:continuwuity.org from my home server (running 0.5.8) and the following error message appears in my client:

Failed to join #continuwuity:continuwuity.org:
Answer from continuwuity.org: [401 / M_UNAUTHORIZED] Unauthorized: Failed to fetch signing keys: Failed to fetch federation signing-key key_id=ed25519:GEl2fXW8 origin=esjott.one

Would ask in the room, but, well....

An !admin debug ping continuwuity.org returned:

Got response which took 1.693983132s time:
{
  "name": "continuwuity",
  "version": "0.5.8 (0e1f068)"
}`

Where should I look at?

Hi there, after some small break I tried to join #continuwuity:continuwuity.org from my home server (running 0.5.8) and the following error message appears in my client: ``` Failed to join #continuwuity:continuwuity.org: Answer from continuwuity.org: [401 / M_UNAUTHORIZED] Unauthorized: Failed to fetch signing keys: Failed to fetch federation signing-key key_id=ed25519:GEl2fXW8 origin=esjott.one ``` Would ask in the room, but, well.... An `!admin debug ping continuwuity.org ` returned: ``` Got response which took 1.693983132s time: { "name": "continuwuity", "version": "0.5.8 (0e1f068)" }` ``` Where should I look at?

👍 1

nex commented

2026-05-05 21:23:05 +00:00

Owner

It looks like your server advertises an illegal signing key @ https://esjott.one/_matrix/key/v2/server. ed25519: a_FCfg is not a valid identifier, so continuwuity is unable to parse your signing key. Did you switch your domain from a synapse server to a continuwuity server or something? I'm not sure how this is even possible

It looks like your server advertises an illegal signing key @ https://esjott.one/_matrix/key/v2/server. `ed25519: a_FCfg` is not a valid identifier, so continuwuity is unable to parse your signing key. Did you switch your domain from a synapse server to a continuwuity server or something? I'm not sure how this is even possible

Esjott commented

2026-05-06 05:44:14 +00:00

Author

Oh that is strange... I used dendrite before on that domain and switched to conduwuit some ages ago and went to continuwuity right after conduwuit being archived..
But that sounds like me, having things happen nobody knows how it is possible :D Is there a way to fix that? (discarding everything and starting on a new domain would be possible, too, if nothing else helps..) Is it possible to generate new keys?

Oh that is strange... I used dendrite before on that domain and switched to conduwuit some ages ago and went to continuwuity right after conduwuit being archived.. But that sounds like me, having things happen nobody knows how it is possible :D Is there a way to fix that? (discarding everything and starting on a new domain would be possible, too, if nothing else helps..) Is it possible to generate new keys?

nex commented

2026-05-09 19:31:07 +00:00

Owner

Yeah we identified the issue and are working on it internally, it's deeper rooted than it looks, and even wiping your database will just defer it happening again until not long after. the only way you can "fix" this for now is by using a different server_name, otherwise you'll just have to wait until we've fixed it unfortunately :(

nex added the

labels

2026-05-09 19:32:40 +00:00

nex self-assigned this