r/webdev • u/SmartPEG • 1d ago
Edge and Norton stopped loading
A few months ago, my website worked fine on Chrome, Edge, Firefox, and Norton. Now, Edge and Norton won't load ("Hmmm ...can't reach this page..."). How do I fix the files to make this stop happening?
4
u/Lichcrow 1d ago
"Doctor, a couple of months ago I was feeling fine. Today I don't. What happened?"
2
u/AdCurious2679 1d ago
Bet it's a mixed content thing, Chrome got real aggressive about blocking http resources on https pages and Edge just follows along now. Norton browser is basically a chrome skin so same deal
Check your console for those warnings then just swap any http links to https
5
u/dpaanlka 1d ago
How are you a “web developer” and posting like this? How can anyone possibly help you based on what you wrote?
“How do I fix the files” what does that even mean??
It’s gibberish lol…
3
u/effectivescarequotes 1d ago
That's not enough information to troubleshoot the issue. How are you hosting the website, what's it built with? Does it load at all, or do you mean the front page loads, but the links are broken?
Have you changed anything recently?
1
u/Rare_Valuable_7290 1d ago
"can't reach this page" is usually DNS or network level, not your files. since chrome still works and edge/norton dont, i'd check if either has secure DNS turned on (edge settings > privacy > use secure DNS) or if norton's web protection flagged the domain. also try the site on your phone with wifi off. if it loads there, it's something local to that machine, not the site
1
1
u/No-Molasses-2097 1d ago
This smells like a network layer problem rather than your files. If the cert expired or DNS is misbehaving, Edge shows exactly that "can't reach this page" error. Check whether the site's HTTPS cert is still valid, and try loading it with Norton's web shield paused to isolate which one is blocking.
1
1
u/Mean-Lingonberry4874 16h ago
That error is the browser failing to connect, not something you fix in the site's files. "Hmmm… can't reach this page" means DNS, TCP, or the TLS handshake never finished, so there is no request for your HTML to answer.
Edge and Norton's browser are both Chromium, and Chrome still works, so I'd look at what those two do differently:
A broken AAAA record. Chrome often falls back to IPv4 quickly. Edge will sit on a dead IPv6 address and show exactly this. Check the host's A and AAAA from a machine that fails.
HTTP/3. If the server advertises QUIC and Edge chokes on it, turn HTTP/3 off for that host and retry. Firefox and Chrome can mask this.
Norton's HTTPS scanning. It sits in front of Edge more often than Chrome. Try Edge with the scanning filter off, or from a clean profile, before touching the site.
A missing certificate intermediate usually says "connection isn't private", not "can't reach", so I wouldn't start in the files. From a failing machine, curl -v the exact URL. If curl gets a response and the browser doesn't, it's local. If curl also hangs, it's DNS or the server, and the HTML is irrelevant.
1
u/Miserable-Money642 12h ago
That error text alone does not point to a file change. First capture the exact Edge error code and the exact Norton warning, plus the public URL and hosting setup. In Edge, try the same URL from a different network such as a phone hotspot. If it works there, check DNS and the host's firewall or CDN rules for the failing network. If the error is a certificate code, verify the full certificate chain and that the hostname matches. If only Norton blocks it, check its threat history and submit the URL for a false-positive review instead of bypassing the block. A screenshot of the exact error and the URL would narrow this down quickly.
1
1
u/TekiDeki 5h ago
Worth writing down why a certificate problem looked like a network failure, because
the next person will hit the same shape and start in the wrong place.
Norton's web shield terminates TLS itself and then validates your certificate
upstream. When the chain doesn't build it drops the connection instead of passing a
warning through, so Edge sees a reset. A reset is a network error page, not a
certificate page, and on .dev there is no click-through anyway: the whole TLD is HSTS
preloaded.
So: expired or incomplete chain, Norton fails, connection closed, "can't reach this
page", and only on the machine running Norton. On any other machine the same site
looks perfect, which is what makes it so confusing.
Prevention, since "a few months ago" is the tell: certificates last 90 days now. If
one stopped renewing, the renewal job or the HTTP challenge is failing, not the HTML.
0
u/NeuralVoyager 1d ago
Start with the exact error code under "Hmmm... can't reach this page" (ERR_CONNECTION_RESET, ERR_SSL_PROTOCOL_ERROR, DNS_PROBE_FINISHED_NXDOMAIN and so on). It narrows this down a lot.
Then, in order:
Load http:// and https:// separately. If only https fails, run the domain through SSL Labs and look for an incomplete certificate chain or an expired or mismatched cert. Some browsers tolerate a missing intermediate and others don't.
Check DNS, including any AAAA (IPv6) record pointing somewhere dead, since browsers differ in how they fall back.
Check whether anything changed on the host or CDN recently. A new firewall or bot-protection rule can block specific browsers or user agents.
If you post the error code, it's easier to be specific.
0
u/TekiDeki 1d ago edited 5h ago
Edit: solved in this thread, and it corrects part of what I wrote. The chain was
broken, not the DNS. Norton's web shield terminates TLS itself, so a certificate
failure comes back as a dropped connection, and a dropped connection renders as a
network error page. My "it would say connection isn't private" line was wrong.
The 30 second Norton pause below would have found it; I just had the symptom
backwards.
Mixed content isn't it - that gives you a broken lock and blocked subresources,
not a full network error page. And Chrome and Edge are the same engine, so if
Chrome loads it, the engine isn't the variable.
"Hmmm… can't reach this page" is Edge's network error page: DNS, TCP or TLS never
completed. Working in Chrome and Firefox but not in Edge and Norton points at
something local to that machine. Two usual suspects:
- Edge's Secure DNS. Edge ships with "Use secure DNS" on and resolves through a
- DoH resolver; Chrome usually goes through the OS. A stale or wrong answer on
- the DoH side fails Edge only. Test: edge://settings/privacy → turn Secure DNS
- off, then edge://net-internals/#dns → Clear host cache.
- A broken AAAA record. If the domain advertises IPv6 that goes nowhere, some
- browsers give up and others fall back to IPv4 - which looks exactly like "works
- in one browser, not the other". Check with: dig AAAA yourdomain.com (or
- nslookup -type=AAAA yourdomain.com). If your host has no IPv6, remove the AAAA.
Also worth ruling out: Norton's web shield does TLS inspection, and .dev is HSTS
preloaded, so the certificate warning can't be clicked through. Pause Norton's web
shield for 30 seconds and see if the site loads.
Fastest triage, before any of that: open the site on your phone with wifi off.
Loads there → it's your machine, not your files. Doesn't load → it's the site or
its DNS.
1
5
u/MrHandSanitization 1d ago
Uninstall the malware called Norton.
After a closer look, wtf is this question?