Kagi assets fail to load trouble when used over ipv6

Lerzun

Hello!
When I load Kagi for the first time after booting a computer, or if I haven't used it for some time, there's an issue with the loading of the kagi css. I have to refresh the page a few times, and then it's working correctly. I guess once the CSS has been loaded in the browser cache, it works until the cache has expired or something.

As you can see, the display is quite broken:

I have the exact same issue on multiple computers, browsers and OS.
To replicate the issue, there's only one step, launching a browser that has'nt loaded kagi for some hours.

If you need more logs or anything, I'd be happy to help.

Thanks a lot,
Lerzun

Everything should load fine without having to refresh the page.

Vlad

Lerzun Can you provide more details about the region you are accessing from, do you use VPN or anything elese that comes to mind why these resources would not load for you?

In addition can you try accessing kagi from mobile phone to help localize the issue?

Lerzun

Vlad Thanks for your answer.

We're accessing kagi from france
Our ISP is OVH
We don't use VPN, it's just a straight connection, nothing weird.

I've just tried on mobile, and it seems to be working fine. The only difference between my mobile and our computers is that I don't use the same DNS resolver. I really don't see why it could cause any issue, but I've just changed the DNS resolver on my computer. I'll update this post in a few hours. I don't have a lot of hope, but we'll see!

Ok I was wrong, I tried with my mobile, and it works with the 4G connexion, but not in wifi. If I try on wifi, I have the same issue (and without any surprise, changing DNS resolver does nothing).

So now I know the issue resides in our home internet connection. But I can't understand why only kagi has this issue.

EDIT: Disabling ipv6 seems to have resolved the issue. I have no idea if there's a problem with the way my ISP does ipv6, or if kagi does something weird. I'm just glad it works now. If you need further tests, I can help.

Vlad

Lerzun

Disabling ipv6 seems to have resolved the issue

Thanks this was the crucial piece of infomration I was looking for

LuanPhan

Hi @Lerzun ,

Thank you for your assistance. It appears that the IPv6 connectivity to assets.kagi.com from your end is experiencing instability. Would you kindly provide me with the output of the following command from your perspective?

sudo traceroute -6 -T -p 443 assets.kagi.com

Lerzun

Hello LuanPhan
I'm not home right now, I'll try it this week-end.

Lerzun

LuanPhan Sorry for the slight delay. Here are the results:

traceroute to assets.kagi.com (2600:9000:218c:bc00:f:ce53:f180:93a1), 30 hops max, 80 byte packets 1 2001:41d0:fc15:e000:24cc:52ff:fe06:307d (2001:41d0:fc15:e000:24cc:52ff:fe06:307d) 0.028 ms 0.021 ms * 2 2001:41d0:fc15:e000:f54e:dd1:2ac7:7f36 (2001:41d0:fc15:e000:f54e:dd1:2ac7:7f36) 0.346 ms * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * 2001:41d0:aaaa:100::7 (2001:41d0:aaaa:100::7) 36.875 ms 2001:41d0:aaaa:100::13 (2001:41d0:aaaa:100::13) 21.180 ms 8 2001:41d0:aaaa:100::7 (2001:41d0:aaaa:100::7) 22.792 ms 36.607 ms * 9 * 2001:41d0:aaaa:100::2 (2001:41d0:aaaa:100::2) 13.105 ms * 10 ae301.par-pa3-pb2-ptx.fr.eu (2001:41d0::26a9) 13.052 ms be305.par-th2-pb3-nc5.fr.eu (2001:41d0::25d1) 13.040 ms ae300.par-pa3-pb2-ptx.fr.eu (2001:41d0::26a7) 13.019 ms 11 2001:41d0::26f5 (2001:41d0::26f5) 12.654 ms 12.638 ms * 12 2a01:578:0:13::6c (2a01:578:0:13::6c) 13.640 ms 2a01:578:0:13::68 (2a01:578:0:13::68) 21.848 ms 2a01:578:0:13::6b (2a01:578:0:13::6b) 11.776 ms 13 2a01:578:0:13::37 (2a01:578:0:13::37) 12.287 ms * 2a01:578:0:13::36 (2a01:578:0:13::36) 11.020 ms 14 2a01:578:0:13::8 (2a01:578:0:13::8) 11.398 ms 2620:107:4000:ae90::f001:1a (2620:107:4000:ae90::f001:1a) 11.329 ms * 15 2620:107:4000:cfff::f202:fac3 (2620:107:4000:cfff::f202:fac3) 14.407 ms 2620:107:4000:c5c0::f3fd:d (2620:107:4000:c5c0::f3fd:d) 14.179 ms * 16 * * * 17 * * * 18 * * 2620:107:4000:cfff::f202:fac3 (2620:107:4000:cfff::f202:fac3) 15.482 ms 19 2600:9000:218c:bc00:f:ce53:f180:93a1 (2600:9000:218c:bc00:f:ce53:f180:93a1) 15.394 ms *

Does it help you?

LuanPhan

Lerzun
Yes thanks, it does help. The result seems good as you don't reach any timeout and reach the target well.

Is the issue still consistent from your end?

Lerzun

LuanPhan Indeed, I soon as I enable IPV6, i can reproduce the issue.

bert

Randomly Kagi failed to load. I've seen this before, but I can't think of anything that tends to cause it (maybe it's more common after Kagi releases an update?). Looks like a white page with no CSS.

Web inspector shows:

System:
macOS 14.3.1
Safari Version 17.3.1
Kagi extension: 2.2.3

N/A

Vlad

bert Can you confirm your region? Are you on a VPN? Do you use DNS over ipv6?

Can you still reproduce the issue? That looks like CDN failing to connect.

bert

I am in the US East, using iCloud private relay. Restarting Safari fixed the issue so I guess this can be closed.

Vlad

bert Do you know if you were using ipv6?

bert

Not sure, but it appears to be enabled on my computer.