Images not loading

xnacly

Nothing here is loading for me, i get these failures in latest firefox (153.0.4 (64-bit))

Security Error: Content at https://kagi.com/images?q=oxide+server+rack may not load or link to file:///.
Content-Security-Policy: The page’s settings blocked the loading of a resource (default-src) at https://kagi.com/images?q=oxide+server+rack because it violates the following directive: “default-src 'none'”

I tried disabling ublock, i tried disabling enhanced protection, still, no images are loading, same in private session

Images to load tbh

z64

Hi there,

Could you confirm how persistent this is?

Is it only for this search term, or any images search you do?
If you repeat the same search now, does it happen again?

Lastly, one off the wall idea I had was just to double check if you have any custom CSS enabled.

garbage

I have the same problem but not because of the security error. It seems like the host at p.kagi.com is not responding.

➜ ~ traceroute p.kagi.com traceroute: Warning: p.kagi.com has multiple addresses; using 188.114.97.5 traceroute to cdn-kagi.com (188.114.97.5), 64 hops max, 40 byte packets 1 192.168.1.1 (192.168.1.1) 10.676 ms 4.911 ms 4.777 ms 2 192.168.144.1 (192.168.144.1) 8.207 ms 7.823 ms 7.851 ms 3 217.11.111.56 (217.11.111.56) 9.289 ms 217.11.111.80 (217.11.111.80) 8.999 ms 217.11.111.56 (217.11.111.56) 8.485 ms 4 217.11.111.32 (217.11.111.32) 16.931 ms 19.559 ms * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * [...]

➜ ~ nc -zv -w 30 188.114.97.5 443 nc: connectx to 188.114.97.5 port 443 (tcp) failed: Operation timed out

➜ ~ curl -v "https://p.kagi.com/proxy/images?c=...." * Host p.kagi.com:443 was resolved. * IPv6: 2a06:98c1:3121::5, 2a06:98c1:3120::5 * IPv4: 188.114.97.5, 188.114.96.5 * Trying 188.114.97.5:443... * Trying [2a06:98c1:3121::5]:443... * connect to 188.114.97.5 port 443 from 192.168.1.36 port 61420 failed: Operation timed out * Trying 188.114.96.5:443... * connect to 2a06:98c1:3121::5 port 443 from fd87:1f69:d383:b3ef:41f:9418:9b68:7637 port 61421 failed: Operation timed out * Trying [2a06:98c1:3120::5]:443... * connect to 188.114.96.5 port 443 from 192.168.1.36 port 61453 failed: Operation timed out * connect to 2a06:98c1:3120::5 port 443 from fd87:1f69:d383:b3ef:41f:9418:9b68:7637 port 61454 failed: Operation timed out * Failed to connect to p.kagi.com port 443 after 150213 ms: Couldn't connect to server * Closing connection curl: (28) Failed to connect to p.kagi.com port 443 after 150213 ms: Couldn't connect to server

z64

garbage Thanks. I would ask you the same questions that I asked in my previous post; Does this happen with any kind of consistency, only for particular searches, etc.?

Feldherren

I've been having the same problem, and it's been happening for any search term I check images for. I have occasionally seen searches display some image thumbnails if I scroll down a fair distance, but often it just doesn't return images at all, no matter how far I scroll.

So I'd say it's pretty consistently just failing to display thumbnails, regardless of search.

kawahwookiee

Kagi Images intermittently/consistently fails because p.kagi.com is unreachable from my normal network.
DNS:
p.kagi.com -> cdn-kagi.com -> 188.114.96.5, 188.114.97.5
Without VPN: both addresses time out establishing TCP/443. This reproduces with curl and nc, so it is independent of Safari.

Trying 188.114.96.5:443...
ipv4 connect timeout
Trying 188.114.97.5:443...
ipv4 connect timeout
curl: (28) Failed to connect ... port 443

With VPN: the same 188.114.96.5:443 connects immediately, TLS succeeds, and Cloudflare returns HTTP/2:

Connected to p.kagi.com (188.114.96.5) port 443
SSL connection using TLSv1.3
server: cloudflare
cf-ray: ...-MAD

cdn-kagi.com behaves identically.
Cloudflare trace reaches Madrid in both cases:

no VPN: colo=MAD, sliver=050-tier1
VPN:    colo=MAD, sliver=010-tier1

I have also reproduced the failure using a cellular hotspot, while using a VPN fixes it.
This appears to be a Cloudflare/network-path issue for the Kagi CDN rather than a browser, DNS, TLS, or Kagi Images frontend problem.