Can't connect with OLM #2292
Closed
TheDietrich
started this conversation in
General
Replies: 1 comment
|
Why was this closed? I have the same issue when trying to connect via Android. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello everyone, I'm currently trying out OLM, but I'm encountering more and more problems. Does anyone here have any ideas?
Thanks in advance for your help.
Pangolin Logs:
2026-01-21T18:07:29+00:00 [info]: All connections removed for OLM ID: 6etxnwk5fsk09ag
2026-01-21T18:07:29+00:00 [info]: Client disconnected - OLM ID: 6etxnwk5fsk09ag
2026-01-21T18:07:40+00:00 [info]: Establishing websocket connection
2026-01-21T18:07:40+00:00 [info]: Client added to tracking - OLM ID: 6etxnwk5fsk09ag, Connection ID: 0a58d59e-a2f4-4091-a075-74bb2b5f100d, Total connections: 1
2026-01-21T18:07:40+00:00 [info]: WebSocket connection established - OLM ID: 6etxnwk5fsk09ag
2026-01-21T18:07:40+00:00 [info]: Handling register olm message!
2026-01-21T18:07:40+00:00 [info]: Public key mismatch. Updating public key and clearing session info...
2026-01-21T18:07:40+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-21T18:07:41+00:00 [info]: Handling register olm message!
2026-01-21T18:07:41+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-21T18:07:42+00:00 [info]: Handling register olm message!
2026-01-21T18:07:42+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-21T18:07:43+00:00 [info]: Handling register olm message!
2026-01-21T18:07:43+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-21T18:07:44+00:00 [info]: Handling register olm message!
2026-01-21T18:07:44+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-21T18:07:45+00:00 [info]: Handling register olm message!
2026-01-21T18:07:45+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-21T18:07:46+00:00 [info]: Handling register olm message!
2026-01-21T18:07:46+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-21T18:07:47+00:00 [info]: Handling register olm message!
2026-01-21T18:07:47+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-21T18:07:48+00:00 [info]: Handling register olm message!
2026-01-21T18:07:48+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-21T18:07:49+00:00 [info]: Handling register olm message!
2026-01-21T18:07:49+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
olm:
Starting service with args: [--id XX--secret XX--endpoint https://XX/]
Saved service args to: C:\ProgramData\olm\service_args.json
INFO: 2026/01/21 19:00:13 Olm version 1.3.0
DEBUG: 2026/01/21 19:00:13 Saved full olm config with all options
INFO: 2026/01/21 19:00:15 Starting HTTP server on socket olm
INFO: 2026/01/21 19:00:15 Created shared UDP socket on port 57136 (refcount: 2)
INFO: 2026/01/21 19:00:15 Starting hole punch for 1 exit nodes
INFO: 2026/01/21 19:00:16 Websocket Connected
INFO: 2026/01/21 19:00:16 Sent initial ping message
INFO: 2026/01/21 19:00:26 SendMessageInterval timed out after 10 attempts for message type: olm/wg/register
All reactions