search

11ty / api-indieweb-avatar

Return an optimized avatar image from a domain name input.
https://v1.indieweb-avatar.11ty.dev/
65 stars 11 forks source link

API returns nothing, or what's going on 11ty.dev? #18

Open reatlat opened 1 month ago

reatlat commented 1 month ago

recently I saw bug on 11ty.dev, and after 2 days its still there, not sure why but for me it seems like something broken ....

CleanShot 2024-07-17 at 19 05 40@2x

CleanShot 2024-07-17 at 19 05 55@2x

reatlat commented 1 month ago

quick update, its works if I use VPN with a US location, but I located in Spain, and its not working for some reasons

reatlat commented 1 month ago

One more update, issue have been resolved by switching from Google's DNS 8.8.8.8 and 8.8.4.4 to Claudflare 1.1.1.1 and 1.0.0.1

but is it something related to project infrastructure? orjust a bug of Google's DNS?

zachleat commented 1 month ago

Sorry about that, we moved hosting providers for the service yesterday so there may have been a small outage during the rollover! I tried to minimize it as much as possible but looks like it wasn’t as seamless as I’d have liked.

zachleat commented 1 month ago

I’ll be looking for other reports of this but this is the only report I’ve seen so far!

zachleat commented 1 month ago

I did also test proxy through Spain just now and that seems to be working for me as well

reatlat commented 1 month ago

@zachleat I checked again with my mobile, and all works fine, with Cloudflare DNS works fine, but my ISP and Googles DNS 8.8.8.8 not working here is a log I was able to capture

02:34:11.344636 [Connection] Incoming proxy protocol: HTTP
02:34:11.362491 [TLS] TLS Client Hello SNI: v1.indieweb-avatar.11ty.dev
02:34:11.363083 [Rule] Rule matched: FINAL
02:34:11.363473 [DNS] Use cached DNS result for v1.indieweb-avatar.11ty.dev. A record count: 2, AAAA record count: 0
02:34:11.363737 [Socket] Connecting with address: 76.76.21.241
02:34:11.363862 [Socket] Connecting with address: 76.76.21.22
02:34:12.364650 [Connector] Set up backup connection #2 via DIRECT
02:34:12.365164 [Socket] Connecting with address: 76.76.21.241
02:34:12.365335 [Socket] Connecting with address: 76.76.21.22
02:34:14.365183 [Connector] Set up backup connection #3 via DIRECT
02:34:14.366052 [Socket] Connecting with address: 76.76.21.241
02:34:14.366405 [Socket] Connecting with address: 76.76.21.22
02:34:17.365847 [Connector] Set up backup connection #4 via DIRECT
02:34:17.366793 [Socket] Connecting with address: 76.76.21.241
02:34:17.367116 [Socket] Connecting with address: 76.76.21.22
02:34:21.363935 [Connection] Disconnect with reason: Failed to establish connection (Connection timeout)

what interesting, I think IPs are correct... if we can trust DNSChecker

and I have no DNS cache.... so I feel issue in Google DNS 8.8.8.8 and 8.8.4.4

CleanShot 2024-07-18 at 02 42 25@2x

zachleat commented 1 month ago

Hmm—can you rope anyone else in to confirm? I did swap to use Google’s DNS to test and it loaded just fine.

Those IP addresses look okay to me, a la:

~ ᐅ ping cname.vercel-dns.com.          
PING cname.vercel-dns.com (76.76.21.93)
zachleat commented 1 month ago

Do any of the other API services fail to load for you? I migrated all of them:

https://www.11ty.dev/docs/api-services/

reatlat commented 1 month ago

all APIs works just fine except indieweb...

anyway I think issue in my ISP :( 

➜  ~ ping -c 3 https://v1.indieweb-avatar.11ty.dev
ping: cannot resolve https://v1.indieweb-avatar.11ty.dev: Unknown host

tested with 8.8.8.8 and 1.1.1.1 all works just fine

probably false alarm, I'm sure issue in my cheap ISP :)