Sender | Message | Time |
---|---|---|
7 Dec 2021 | ||
Github [@neilalexander:matrix.org] | [matrix-org/dendrite] MFAshby synchronize pull request #2060: Added std type to logging config. [open] - https://github.com/matrix-org/dendrite/pull/2060 | 11:53:51 |
Github [@neilalexander:matrix.org] | [matrix-org/dendrite] MFAshby synchronize pull request #2060: Added std type to logging config. [open] - https://github.com/matrix-org/dendrite/pull/2060 | 13:47:01 |
bn4t_ joined the room. | 14:36:11 | |
bn4t_ set a profile picture. | 14:36:28 | |
8 Dec 2021 | ||
James [away] changed their display name from James [AEDT +11] to James [away]. | 01:30:57 | |
Github [@neilalexander:matrix.org] | [matrix-org/dendrite] bn4t opened pull request #2070: Don't ignore config flag for yggdrasil demo if set [open] - https://github.com/matrix-org/dendrite/pull/2070 | 09:00:29 |
Github [@neilalexander:matrix.org] | [matrix-org/dendrite] bn4t synchronize pull request #2070: Don't ignore config flag for yggdrasil demo if set [open] - https://github.com/matrix-org/dendrite/pull/2070 | 09:11:35 |
9 Dec 2021 | ||
Github [@neilalexander:matrix.org] | [matrix-org/dendrite] neilalexander opened pull request #2071: Return event NID from `StoreEvent`, match PSQL vs SQLite behaviour, tweak backfill persistence [open] - https://github.com/matrix-org/dendrite/pull/2071 | 13:53:43 |
Github [@neilalexander:matrix.org] | [matrix-org/dendrite] neilalexander review_requested pull request #2071: Return event NID from `StoreEvent`, match PSQL vs SQLite behaviour, tweak backfill persistence [open] - https://github.com/matrix-org/dendrite/pull/2071 | 13:53:44 |
Github [@neilalexander:matrix.org] | [matrix-org/dendrite] neilalexander closed pull request #2071: Return event NID from `StoreEvent`, match PSQL vs SQLite behaviour, tweak backfill persistence [closed] - https://github.com/matrix-org/dendrite/pull/2071 | 15:03:28 |
10 Dec 2021 | ||
James [away] left the room. | 03:32:58 | |
rhymefororange | Hi everyone. I'm new to dendrite and would like to start contributing. I tried to follow the instructions for docker monolith deployment, but when I start the monolith container I get this error:docker-monolith-1 | time="2021-12-10T13:13:43.298170403Z" level=panic msg="failed to start kafka consumer" func="setupKafka\n\t" file=" [kafka.go:27]" error="kafka: client has run out of available brokers to talk to (Is your cluster reachable?)" I looked into the docker compose file and it turns out running docker-compose -f docker-compose.deps.yml up instead of docker-compose -f docker-compose.deps.yml up postgres fixes the problem, because it starts the kafka container that the consumers are looking for. Is that a bug in the docs or am I missing something? | 13:19:04 |
rhymefororange | * Hi everyone. I'm new to dendrite and would like to start contributing. I tried to follow the instructions for docker monolith deployment, but when I start the monolith container I get this error:docker-monolith-1 | time="2021-12-10T13:13:43.298170403Z" level=panic msg="failed to start kafka consumer" func="setupKafka\n\t" file=" [kafka.go:27]" error="kafka: client has run out of available brokers to talk to (Is your cluster reachable?)" I looked into the docker compose file and it turns out running docker-compose -f docker-compose.deps.yml up instead of docker-compose -f docker-compose.deps.yml up postgres fixes the problem, because it starts the kafka container that the consumers are looking for. Is that a bug in the docs or am I missing something? | 13:19:24 |
neilalexander | In reply to @rhymefororange:zlol.lg.uaYou probably want to run a monolith Dendrite deployment, make sure that use_naffka is set in your Dendrite config and then forego running Kafka altogether | 13:31:24 |
rhymefororange | In reply to @neilalexander:matrix.orgYep, that is what I missed, thanks. I used dendrite-config.yaml from build/docker/config where use_naffka is set to false instead of using dendrite-config.yaml from root of the project. | 13:49:13 |
Github [@neilalexander:matrix.org] | [matrix-org/dendrite] PiotrKozimor synchronize pull request #1842: Implement Pushers API [open] to danpe - https://github.com/matrix-org/dendrite/pull/1842 | 13:53:56 |
neilalexander | I think the one in build/docker/config is just prepopulated with database connection strings and paths that make sense for Docker | 13:58:38 |
neilalexander | * I think the one in build/docker/config is just prepopulated with database connection strings and paths that make sense for Docker+PSQL | 13:58:42 |
rhymefororange | But now I have a different problem. When I point element to https://localhost:8448 it says that this does not apper to abe a valid homeserver address and I see docker-monolith-1 | 2021/12/10 13:47:42 http: TLS handshake error from 172.21.0.1:48812: remote error: tls: bad certificate in the logs. I generated the certificates and placed them in build/docker (which is where I launch the containers from) and build/docker/config (which is mounted in the container AFAIK). Am I missing something again? plaintext http://localhost:8008 works fine | 14:39:40 |
rhymefororange | * But now I have a different problem. When I point element to https://localhost:8448 it says that this does not apper to be a valid homeserver address and I see docker-monolith-1 | 2021/12/10 13:47:42 http: TLS handshake error from 172.21.0.1:48812: remote error: tls: bad certificate in the logs. I generated the certificates and placed them in build/docker (which is where I launch the containers from) and build/docker/config (which is mounted in the container AFAIK). Am I missing something again? plaintext http://localhost:8008 works fine | 14:39:51 |
rhymefororange | * But now I have a different problem. When I point element to https://localhost:8448 it says that this does not apper to be a valid homeserver address and I seedocker-monolith-1 | 2021/12/10 13:47:42 http: TLS handshake error from 172.21.0.1:48812: remote error: tls: bad certificate in the logs. I generated the certificates and placed them in build/docker (which is where I launch the containers from) and build/docker/config (which is mounted in the container AFAIK). Am I missing something again? plaintext http://localhost:8008 works fine | 14:39:58 |
rhymefororange | * But now I have a different problem. When I point element to https://localhost:8448 it says that this does not apper to be a valid homeserver address and I seedocker-monolith-1 | 2021/12/10 13:47:42 http: TLS handshake error from 172.21.0.1:48812: remote error: tls: bad certificate in the logs. I generated the certificates and placed them in build/docker (which is where I launch the containers from) and build/docker/config (which is mounted in the container AFAIK).Am I missing something again? plaintext http://localhost:8008 works fine | 14:40:33 |
neilalexander | Unless those certificates came from a signed authority then they will not pass client validation checks, which is normal | 14:48:29 |
neilalexander | ... but if you just want to talk to the HS for development purposes then using plain HTTP on port 8008 would be fine | 14:48:40 |
rhymefororange | Ok. I thought I could deploy locally with self-signed certificates and use it that way even if the browser tells me it if insecure and I have to accept it. | 14:56:43 |
rhymefororange | * Ok. I thought I could deploy locally with self-signed certificates and use it that way even if the clients tells me it if insecure and I have to accept it. | 14:57:44 |
rhymefororange | So only the CA-issued certs are going to work with matrix clients because they do the validation, right? | 14:58:14 |
rhymefororange | * Ok. I thought I could deploy locally with self-signed certificates and use it that way even if the client tells me it if insecure and I have to accept it. | 14:58:36 |
rhymefororange | * Ok. I thought I could deploy locally with self-signed certificates and use it that way even if the client tells me it is insecure and I have to accept it. | 14:58:42 |
neilalexander | Unless the client has a switch to not validate the certificates, yep | 15:02:23 |