On Sat, Nov 16, 2024 at 01:03:34PM -0500, Greg Wooledge wrote:
I've been thinking about this some more, and I'd like to try to list
all the ways the OP might have caused this to fail.
We start by observing that nobody else has been able to reproduce the
OP's failure.
Two or three months ago, a guy in Australia and a guy in England
reported the same problem (blank white screen).
So, the problem appears to be unique to the OP's setup.
What could cause this?
* Wrong browser. We don't know which browser the OP is using primarily;
Primarily Firefox. I also routinely use Chromium.
* Browser configuration. The OP might have installed an add-on that's
interfering with this site, or they might have changed a setting.
A few people have suggested that the OP try a pristine browser profile,
or a pristine user account with no customizations.
I have approx running on one machine here, so I can reinstall using
netinst fairly quickly. And I have been given several old machines,
so I several times have done a no-compromise clean install (via
netinst). Yet, the fresh installation fails to browse CHEWY.
* Firewall. The OP mentions separate networks. It's unclear whether
the configuration of the router/firewall is different between the
two networks. A firewall could be blocking traffic to some web
server(s) that are needed to render this site, or there could be
a misbehaving proxy, etc. Moving the Debian host to the other network
might be a quick way to test this.
I have a machine running iphole. But that machine is inside the GREEN
network, and the firewall has no special knowledge of it. Each
machine in the network must be configured individually (through the
network manager) to use iphole.
And I have bypassed everything by connecting directly to the router
(provided by the ISP) to which the firewall is connected. The problem
remains.
* DNS blocking. Some people edit their /etc/hosts files to prevent
connections to various hosts, and then they often forget they've
done this. The OP might want to check whether their /etc/hosts file
has been modified.
Pristine Debian-12 installation.
Or, if the Debian system is running its own
nameserver, the nameserver's configuration should be checked (or
temporarily switch the local nameserver to the one used by the
Windows systems).
Anything else?
Perhaps the quickest solution is to setup a mail client on the Window$
machine -- a time-machine journey back to the year A.D. 2000 when a
genuine Y2K bug (in MS Word 5.0 for DOS) impelled a search which
brought me out of the mire of Windows and to Debian.
RLH
