Hi,
since the automatic app update, I've been having problems. As long as I'm on my home wifi, everything works just fine. But as soon as I'm on my 5G connection, the client claims it's unable to connect. My current theory is that the new client prefers IPv6 connections over IPv4, and actually doesn't fall back to IPv4 when IPv6 can't be reached. In my setup, even though an IPv6 address is published for my URL, since my home router doesn't support forwarding of IPv6 connections, only IPv4 is reachable from outside the home.
Questions: a) does this sound like a logical explanation for the problems I'm seeing, and b) is there any chance we can get a switch to disable IPv6 (or automatically fall back to IPv4), since I'm sure I'm not the only one in this position. Unfortunately, due to the dynamic DNS nature of my URL, I can't disable the publishing of an IPv6 address at the moment.
Same here, in WiFi it works, the moment I go outside and it switches to LTE, it is dead like a stone....
I assume the same, IPv6 is preferred of IPv4 and does not fallback. I changed my APN now and it worked:
https://www.traccar.org/forums/topic/new-app-a-catastrophe/#post-111659
My server is IPv4 only but it is behind Cloudflare, and CF uses v4 and v6 for DNS resolution. CF should "rewrite" / "relay" v6-packet as v4-packet to my server. But I think something break here. I think with the changed APN, everything is v4 and it works this way.
But the old app worked with the original APN (v6) too...
Hi,
since the automatic app update, I've been having problems. As long as I'm on my home wifi, everything works just fine. But as soon as I'm on my 5G connection, the client claims it's unable to connect. My current theory is that the new client prefers IPv6 connections over IPv4, and actually doesn't fall back to IPv4 when IPv6 can't be reached. In my setup, even though an IPv6 address is published for my URL, since my home router doesn't support forwarding of IPv6 connections, only IPv4 is reachable from outside the home.
Questions: a) does this sound like a logical explanation for the problems I'm seeing, and b) is there any chance we can get a switch to disable IPv6 (or automatically fall back to IPv4), since I'm sure I'm not the only one in this position. Unfortunately, due to the dynamic DNS nature of my URL, I can't disable the publishing of an IPv6 address at the moment.