0.6.3 Update did not fix DNS issue

[OscarsWorldTech]

Describe the Bug

Updated to IOS version 0.6.3. and reset the account on it. Still get stuck on registering. I even deleted the app and restarted phone after to no avail. Please see logs below from the Pangolin container whenever I try to connect:

2026-03-28T19:06:22+00:00 [info]: Handling register olm message!
2026-03-28T19:06:22+00:00 [info]: Public key mismatch. Updating public key and clearing session info...
2026-03-28T19:06:22+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-03-28T19:06:24+00:00 [info]: Handling register olm message!
2026-03-28T19:06:24+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-03-28T19:06:26+00:00 [info]: Handling register olm message!
2026-03-28T19:06:26+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-03-28T19:06:28+00:00 [info]: Handling register olm message!
2026-03-28T19:06:28+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-03-28T19:06:30+00:00 [info]: Handling register olm message!
2026-03-28T19:06:30+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-03-28T19:06:32+00:00 [info]: Handling register olm message!
2026-03-28T19:06:32+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register
2026-03-28T19:06:34+00:00 [info]: Handling register olm message!
2026-03-28T19:06:34+00:00 [warn]: Client last hole punch is too old and we have sites to send; skipping this register

Environment

• OS Type & Version: Ubuntu 24.04.4 LTS
• Pangolin Version: v1.16.2 EE
• Gerbil Version: Latest
• Traefik Version: Latest
• Newt Version: Latest
• Client Version: (if applicable)

To Reproduce

1. Download the Pangolin IOS app
2. Sign into the app
3. Try to connect to instance
4. Gets stuck registering

Expected Behavior

It should connect regardless of the DNS settings

[oschwartz10612]

Could you take a look at fosrl/pangolin#2384 and make sure this is not the issue? Does the register only fail if you set certain DNS settings? If so what are they?

[OscarsWorldTech]

Could you take a look at fosrl/pangolin#2384
and make sure this is not the issue?

Does the register only fail if you set certain DNS settings? If so what
are they?

I can confirm that the above discussion is not the issue has I reset up Pangolin in a brand new Hetzner VPS.

The register fails on either no DNS settings or DNS set to 1.1.1.1.

[ytzelf]

I have a similar issue - 21820/udp opened on vps, iptables and docker-compose.yml
Issue appeared after 0.6.2 and was working between Jan 30 and this update so I guess not related to https://github.com/orgs/fosrl/discussions/2384

[OscarsWorldTech]

Is there a way to revoke client keys/hole punches from the instance? I have a theory that the issue has something to do with Pangolin not fully updating the public key and clearing the session info.

[OscarsWorldTech]

I dug around in the database a bit and tried to delete the client, the client keys, and the client history to no avail.

I hope this gets fix soon as prior to this issue it was working flawlessly.