Dev tools shows that Chrome is stalling on a 10.0 second DNS lookup, which suggests a timeout, but there's no remote resources being fetched. This is a toy "hello world" PHP project with everything served from localhost.
-
-
Show this thread
-
Gold star here goes to
@derivativeburke. The issue was that my /etc/hosts entry didn't have an ipV6 address. Adding it fixed the timeout. 127.0.0.1 site.local <-- 10.0 second DNS timeout 127.0.0.1 ::1 site.local <-- works instantlyhttps://twitter.com/derivativeburke/status/1283253490811236352 …Show this thread -
Now the important question: who do I murder, and in what order?
Show this thread
End of conversation
New conversation -
-
-
Guessing DNS over HTTPS default in chrome.https://blog.chromium.org/2020/05/a-safer-and-more-private-browsing-DoH.html …
-
this has bitten me enough times that I finally wrote it down for myself. (in
@firefox, but the same setting...)
End of conversation
New conversation -
-
-
Are you working with a framework or boilerplate that could possibly be loading external resources, like other .js, .css, imgs or fonts?
-
No, this is a small, raw project with no remote resources, no images, fonts, remote requests of any kind I can think of.
- Show replies
New conversation -
-
-
Also in other browsers?
-
No, Chrome specific
End of conversation
New conversation -
-
-
Checkout the network tab in the dev tools. you might also need to enable out-of-blink-cors to view any CORS preflight requests that are happening.
-
Nevermind, just realized who I was tweeting to. You probably tried this already.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.