-
-
Notifications
You must be signed in to change notification settings - Fork 106
Error 500: Unable to Verify a user #720
Comments
To add to this, sending/recieving media works fine. Messages work absolutely fine also |
Are you able to run a debug build and see if you can find any debug logs related that would help identify the issue more clearly? |
Tested again with this image: main-7bf92c8a3710eeff229bd86bc81a89daa94b66d5-debug Logs: ` 2025-03-24T13:15:55.961403Z ERROR conduwuit_router::request: 500 Internal Server Error, method: POST, uri: /_matrix/client/v3/keys/signatures/upload 2025-03-24T13:15:55.961483Z DEBUG router{method=POST path=/_matrix/client/v3/keys/signatures/upload}: tower_http::trace::on_response: finished processing request latency=0 ms status=500 2025-03-24T13:15:56.366699Z DEBUG router{method=OPTIONS path=/_matrix/client/v3/rooms/:room_id/receipt/:receipt_type}: tower_http::trace::on_response: finished processing request latency=0 ms status=200 2025-03-24T13:15:57.985261Z DEBUG router{method=POST path=/_matrix/client/v3/keys/signatures/upload}: tower_http::trace::on_response: finished processing request latency=2 ms status=500 2025-03-24T13:15:58.427048Z DEBUG router{method=PUT path=/_matrix/federation/v1/send}:request:handle{active=1 handled=177}: conduwuit_api::router::args: PUT /_matrix/federation/v1/send/1742818853469 {"host": "matrix.sourcedomain.io", "x-request-id": "9f81264e5446ffa8b06ee163a615e7ac", "x-real-ip": "79.72.84.56", "x-forwarded-for": "79.72.84.56", "x-forwarded-host": "matrix.sourcedomain.io", "x-forwarded-port": "443", "x-forwarded-proto": "https", "x-forwarded-scheme": "https", "x-scheme": "https", "x-original-forwarded-for": "79.72.84.56", "content-length": "303", "user-agent": "Synapse/1.126.0", "accept-encoding": "gzip, br", "authorization": Sensitive, "cdn-loop": "cloudflare; loops=1", "cf-connecting-ip": "79.72.84.56", "cf-ipcountry": "GB", "cf-ray": "925670b9f96d94bb-LHR", "cf-visitor": "{"scheme":"https"}", "cf-warp-tag-id": "272edfe2-5f3d-4067-8ae5-b5e06a6e6c02", "content-type": "application/json"} 2025-03-24T13:16:02.220302Z DEBUG router{method=POST path=/_matrix/client/v3/keys/signatures/upload}: tower_http::trace::on_response: finished processing request latency=2 ms status=500 2025-03-24T13:16:11.205774Z DEBUG router{method=OPTIONS path=/_matrix/client/v3/keys/signatures/upload}: tower_http::trace::on_response: finished processing request latency=0 ms status=200 2025-03-24T13:16:11.212753Z DEBUG router{method=POST path=/_matrix/client/v3/keys/signatures/upload}: tower_http::trace::on_response: finished processing request latency=0 ms status=500 2025-03-24T13:16:12.714414Z DEBUG router{method=POST path=/_matrix/client/v3/keys/query}:request:handle{active=3 handled=73}:request:fed{dest="matrix.destination.io"}:Connection{peer=Client}: h2::codec::framed_write: send frame=GoAway { error_code: NO_ERROR, last_stream_id: StreamId(0) } Obfsucated source and destination domain. But hopefully this is of some help? I'll keep the container running for now so It keeps generating logs like this. |
This doesn't show any real error messages. I think I see a few places of where this error is coming from, but this is unfortunately legacy / potentially broken code we still haven't refactored from upstream yet. Are you able to grep for |
I can't find the keyid_key in these logs. Nor am I able to descern what exactly you'd be looking for in relation to that path. As far as I can tell, what you're asking for doesn't really exist. Perhaps I need to also change the RUST_LOG env settings to debug also? |
I added some extended debug logging in this area, are you able to run a debug build and get debug and warn logs if this issue still happens? I also tried adjusting the logic to not fail the request entirely and just skip over malformed keys. |
Tested again with: main-00f7745ec4ebcea5f892376c5de5db1299f71696-debug Seem to get the same results. I have attached logs of this. I can at a glance see some warning in here. Hope this if of some help. |
Okay I was able to get the logs of what I want now to know where this specific problem is coming from:
It seems like somehow, possibly because the lack of checks previously that were recently added in the last few weeks, malformed keys were uploaded then stored in the database. I think I can just add some kind of transparent "migration" that will just delete any malformed keys in the database and then the client can just happily re-upload them again. I'll let you know if I have something to test again. |
Hi,
When trying to validate a user in a private chat on another server, I'm unable to verify them. We're able to do the emoji verification process, where they eventually end up with me being verified. But they never end being verified for me.
I have tried this both on the Element Desktop app, and Element Web application.
The log output of the system gives:
` 2025-03-24T12:29:25.531038Z ERROR conduwuit_router::request: 500 Internal Server Error, method: POST, uri: /_matrix/client/v3/keys/signatures/upload
at src/router/request.rs:105 on conduwuit:worker ThreadId(2)
2025-03-24T12:29:25.531067Z ERROR tower_http::trace::on_failure: response failed, classification: Status code: 500 Internal Server Error, latency: 0 ms
at /nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-vendor-cargo-deps/c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0/tower-http-0.6.2/src/trace/on_failure.rs:93 on conduwuit:worker ThreadId(2)
2025-03-24T12:29:27.581532Z ERROR 8000 conduwuit_router::request: 500 Internal Server Error, method: POST, uri: /_matrix/client/v3/keys/signatures/upload
at src/router/request.rs:105 on conduwuit:worker ThreadId(4)
2025-03-24T12:29:27.581610Z ERROR tower_http::trace::on_failure: response failed, classification: Status code: 500 Internal Server Error, latency: 0 ms
at /nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-vendor-cargo-deps/c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0/tower-http-0.6.2/src/trace/on_failure.rs:93 on conduwuit:worker ThreadId(4)
2025-03-24T12:29:31.593249Z ERROR conduwuit_router::request: 500 Internal Server Error, method: POST, uri: /_matrix/client/v3/keys/signatures/upload
at src/router/request.rs:105 on conduwuit:worker ThreadId(4)
2025-03-24T12:29:31.593444Z ERROR tower_http::trace::on_failure: response failed, classification: Status code: 500 Internal Server Error, latency: 0 ms
at /nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-vendor-cargo-deps/c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0/tower-http-0.6.2/src/trace/on_failure.rs:93 on conduwuit:worker ThreadId(4)`
I originally tested this on: v0.5.0-rc3-b6e9dc3d98704c56027219d3775336910a0136c6
I have now tested this on: main-7bf92c8a3710eeff229bd86bc81a89daa94b66d5-haswell
Both giving the same result. I am verified on their end, I'm unable to be verified on my end.
My configuration: https://github.com/tajinder400/home-ops/blob/main/kubernetes/apps/communication/conduwuit/app/helmrelease.yaml
The text was updated successfully, but these errors were encountered: