Describe the Bug
I noticed that I couldn't connect recently and that there were changes in the server and client so I did some testing.
Server 1.14.1 works with client 0.4.1
Server 1.15.1 works with client 0.5.0
Server 1.15.1 does not work with 0.5.0. - Sits on "Registering" and never leaves or turns orange.
Standard windows 11 machine (same machine for all tests). The only thing I see in the docker logs that stands out with the failed connections is.
2026-01-25T17:34:45+00:00 [info]: Handling register olm message!
2026-01-25T17:34:45+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:34:46+00:00 [info]: Handling register olm message!
2026-01-25T17:34:46+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:34:47+00:00 [info]: Handling register olm message!
2026-01-25T17:34:47+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:34:48+00:00 [info]: Handling register olm message!
2026-01-25T17:34:48+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:34:48+00:00 [info]: All connections removed for OLM ID: xxxx
2026-01-25T17:34:48+00:00 [info]: Client disconnected - OLM ID: xxxx
2026-01-25T17:35:23+00:00 [info]: Establishing websocket connection
2026-01-25T17:35:23+00:00 [info]: Client added to tracking - OLM ID: xxxx, Connection ID: xxxxxecxxx2xxx2-xxx-xxxxx, Total connections: 1, Config version: 0
2026-01-25T17:35:23+00:00 [info]: WebSocket connection fully established and ready - OLM ID: xxxx
2026-01-25T17:35:23+00:00 [info]: Handling register olm message!
2026-01-25T17:35:24+00:00 [info]: Public key mismatch. Updating public key and clearing session info...
2026-01-25T17:35:24+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:35:24+00:00 [info]: Handling register olm message!
2026-01-25T17:35:24+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:35:25+00:00 [info]: Handling register olm message!
2026-01-25T17:35:26+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:35:26+00:00 [info]: Handling register olm message!
2026-01-25T17:35:26+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:35:27+00:00 [info]: All connections removed for OLM ID: xxxxx
Happy to do more testing if I can assist.
Environment
See Above.
To Reproduce
Connect as usual
Expected Behavior
connects the same as the old versions.
Describe the Bug
I noticed that I couldn't connect recently and that there were changes in the server and client so I did some testing.
Server 1.14.1 works with client 0.4.1
Server 1.15.1 works with client 0.5.0
Server 1.15.1 does not work with 0.5.0. - Sits on "Registering" and never leaves or turns orange.
Standard windows 11 machine (same machine for all tests). The only thing I see in the docker logs that stands out with the failed connections is.
2026-01-25T17:34:45+00:00 [info]: Handling register olm message!
2026-01-25T17:34:45+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:34:46+00:00 [info]: Handling register olm message!
2026-01-25T17:34:46+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:34:47+00:00 [info]: Handling register olm message!
2026-01-25T17:34:47+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:34:48+00:00 [info]: Handling register olm message!
2026-01-25T17:34:48+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:34:48+00:00 [info]: All connections removed for OLM ID: xxxx
2026-01-25T17:34:48+00:00 [info]: Client disconnected - OLM ID: xxxx
2026-01-25T17:35:23+00:00 [info]: Establishing websocket connection
2026-01-25T17:35:23+00:00 [info]: Client added to tracking - OLM ID: xxxx, Connection ID: xxxxxecxxx2xxx2-xxx-xxxxx, Total connections: 1, Config version: 0
2026-01-25T17:35:23+00:00 [info]: WebSocket connection fully established and ready - OLM ID: xxxx
2026-01-25T17:35:23+00:00 [info]: Handling register olm message!
2026-01-25T17:35:24+00:00 [info]: Public key mismatch. Updating public key and clearing session info...
2026-01-25T17:35:24+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:35:24+00:00 [info]: Handling register olm message!
2026-01-25T17:35:24+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:35:25+00:00 [info]: Handling register olm message!
2026-01-25T17:35:26+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:35:26+00:00 [info]: Handling register olm message!
2026-01-25T17:35:26+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-01-25T17:35:27+00:00 [info]: All connections removed for OLM ID: xxxxx
Happy to do more testing if I can assist.
Environment
See Above.
To Reproduce
Connect as usual
Expected Behavior
connects the same as the old versions.