Open 3isenHeiM opened 2 months ago
EDIT : I've tried with let's encrypt certificates and the issue is still present.
I've modified the code to avoid raising a RequestTimedOutErrors
anytime there is an error to catch, because then it masks the real error.
Commenting the line https://github.com/element-hq/synapse/blob/v1.114.0/synapse/http/client.py#L933
request_deferred.addErrback(_timeout_to_request_timed_out_error)
And re-running the server allowed me to get the true error:
twisted.web._newclient.ResponseNeverReceived: [<twisted.python.failure.Failure OpenSSL.SSL.Error: [('SSL routines', '', 'tlsv1 alert internal error')]>]
Here are the ciphers offered by my IdP server (thanks this comment):
nmap --script ssl-enum-ciphers -p 443 auth.rtss.ninja
Starting Nmap 7.95 ( https://nmap.org ) at 2024-09-06 13:21 CEST
Nmap scan report for auth.rtss.ninja (172.18.0.1)
Host is up (0.00010s latency).
PORT STATE SERVICE
443/tcp open https
| ssl-enum-ciphers:
| TLSv1.2:
| ciphers:
| TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (secp256r1) - A
| TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (secp256r1) - A
| TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 (secp256r1) - A
| compressors:
| NULL
| cipher preference: client
| TLSv1.3:
| ciphers:
| TLS_AKE_WITH_AES_128_GCM_SHA256 (ecdh_x25519) - A
| TLS_AKE_WITH_AES_256_GCM_SHA384 (ecdh_x25519) - A
| TLS_AKE_WITH_CHACHA20_POLY1305_SHA256 (ecdh_x25519) - A
| cipher preference: server
|_ least strength: A
Nmap done: 1 IP address (1 host up) scanned in 0.37 seconds
Can you confirm the length of the client secret ?
The client secret is 32 hex chars long.
The client secret is 32 hex chars long.
Increase it to at least 128 chars long.
My mistake, it was 64 chars long.
I generate them using openssl rand -hex 32
.
Will try, thanks for the hint
Description
I've configured my OIDC server (Authentik) for Synapse using the official guide.
My
homeserver.yml
is populated as this (the URL of the matrix server ismatrix.tld
):However, at the
docker compose up
, the synapse server restarts in loop because it can't initialize the provider. It seems it reaches a timeout, from the logs, although it doesn't even wait half a second and directly restarts.Here are the logs:
But I can browse to the Element homepage, and then when clicking on "Sign in", I get these log lines:
I have this page:
I don't know why is there a timeout. My OIDC server is using a self-signed certificate, but I've patched the Dockerfile to add the CA to the trusted store.
How could I further debug this ?
Thanks
Steps to reproduce
docker compose up
Homeserver
self-hosted, not federated
Synapse Version
1.113.0
Installation Method
Docker (matrixdotorg/synapse)
Database
PostgreSQL
Workers
Single process
Platform
Dockerized with docker compose.
Configuration
No response
Relevant log output
Anything else that would be useful to know?
No response