Debian machines are on the 192.168.1.xxx network. I keep a W10
machine on the 192.168.2.x network, primarily to access the chewy.com
web site which, since about June, serves my Debian machines a blank
white page.
Is there an easy way to send the message (or just the URL) to the
Window$ machine?
Most importantly, though, I'd try to figure out why your browser on
Debian is having problems. If you create a brand new user account,
and run the browser with no add-ons, does it also have problems with
this web site? Maybe it's something in your main account's configuration.
On Fri, Nov 15, 2024 at 11:42:24PM -0500, Greg Wooledge wrote:
Most importantly, though, I'd try to figure out why your browser on
Debian is having problems. If you create a brand new user account,
and run the browser with no add-ons, does it also have problems with
this web site? Maybe it's something in your main account's configuration.
Hi, Greg. I think it has to do with DRM; a couple of times I have
seen a message to that effect flash on the screen briefly and
disappear.
One day I could access the web site on any of my Debian systems; the
next day I got only a blank white screen on all of them. CHEWY must
have changed something on the web server. I have complained to CHEWY
to no avail.
One of the CHEWY customer service people told me that her husband runs
Linux, and she spent about a half hour on the phone having me change
this and that; but the problem remained. I tried Firefox, Chromium,
and Brave.
I solved the problem by ordering a refurbished Window$ box for about a hundred dollars (free shipping). Life is too short to mess around
with things which can be avoided.
Debian machines are on the 192.168.1.xxx network. I keep a W10
machine on the 192.168.2.x network, primarily to access the chewy.com
web site which, since about June, serves my Debian machines a blank
white page. Only one of the Debian machines is set up for mail.
Now and then a mail message comes in to which I need to respond, but
the response link typically is a URL consisting of dozens of
characters, and it is the URL of a chewy.com web site or another web
site which is hostile to Debian.
Is there an easy way to send the message (or just the URL) to the
Window$ machine?
Example URL:[...]
https://clicks-paws.chewy.com/f/a/uBusczxQ2YB4qWyebLm8UA~~/AAQRxQA~/ RgRpFi0ZP4TxAWh0dHBzOi8vbWVvdy5jaGV3eS5jb20vcC9jcC83NzIxMTI0YjA0NjYzYz
Debian machines are on the 192.168.1.xxx network. I keep a W10
machine on the 192.168.2.x network, primarily to access the chewy.com
web site which, since about June, serves my Debian machines a blank
white page. Only one of the Debian machines is set up for mail.
Now and then a mail message comes in to which I need to respond, but
the response link typically is a URL consisting of dozens of
characters, and it is the URL of a chewy.com web site or another web
site which is hostile to Debian.
Is there an easy way to send the message (or just the URL) to the
Window$ machine?
Russell L. Harris <russell@rlharris.org> wrote:
On Fri, Nov 15, 2024 at 11:42:24PM -0500, Greg Wooledge wrote:
Most importantly, though, I'd try to figure out why your browser on >Debian is having problems. If you create a brand new user account,
and run the browser with no add-ons, does it also have problems
with this web site? Maybe it's something in your main account's >configuration.
Hi, Greg. I think it has to do with DRM; a couple of times I have
seen a message to that effect flash on the screen briefly and
disappear.
One day I could access the web site on any of my Debian systems; the
next day I got only a blank white screen on all of them. CHEWY must
have changed something on the web server. I have complained to
CHEWY to no avail.
One of the CHEWY customer service people told me that her husband
runs Linux, and she spent about a half hour on the phone having me
change this and that; but the problem remained. I tried Firefox,
Chromium, and Brave.
I solved the problem by ordering a refurbished Window$ box for
about a hundred dollars (free shipping). Life is too short to mess
around with things which can be avoided.
Would running remmina (or something similar) on you Linux systems
allow you to access the Windows box? I do this so I can run some
Epson scanner software on a windows 10 systme with control from my
Debian (xfce in my case) desktop. All you need to do at the Windows
end is allow access using RDP and it all 'just works'.
I keep a W10 machine on the 192.168.2.x network, primarily to access
the chewy.com web site which, since about June, serves my Debian
machines a blank white page.
If your Windows machine can run an ssh daemon that you can log into,
then you could use it as your SOCKS proxy, though I have no idea how
you'd go about setting up an sshd on Windows.
I get to the Chewy website with no issues using: Trixie, KDE and
Google Chrome browser. If you are getting a plain white screen on
Firefox then it is likely a firefox issue and not a debian issue. Try installing Google Chrome.
Is there an easy way to send the message (or just the URL) to the
Window$ machine?
Use a pastebin? Setup mail in Windows? Connect to the Windows machine
via remote desktop and remotely use the browser there? There are so many
ways to skin that cat.
Debian machines are on the 192.168.1.xxx network. I keep a W10
machine on the 192.168.2.x network, primarily to access the chewy.com
web site which, since about June, serves my Debian machines a blank
white page.
With javascript disabled for chewy,com I get a blank white page with
Debian 12 and Firefox. Allowing javascript seems to result in a fully >functional site.
It may well be that you have permissions like javascript and cross-site >cookies tightened up so far on Linux that some sites don't work. You
then perhaps go to a Windows machine with no such protections in order
to make that work.
Long term I would suggest that isn't ideal and maybe relaxing some
security features in your Linux browser might be worth it, or running
such a browser in a virtual machine, rather than having to have a whole >separate computer.
On Sat, Nov 16, 2024 at 01:15:17PM +0000, Andy Smith wrote:
With javascript disabled for chewy,com I get a blank white page with
Debian 12 and Firefox. Allowing javascript seems to result in a fully
functional site.
I know nothing about javascript; how do I "allow" javascript? Or,
what did I do to disallow javascript?
It may well be that you have permissions like javascript and cross-site
cookies tightened up so far on Linux that some sites don't work.
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.
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;
* 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.
* 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.
* 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.
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?
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).
Debian machines are on the 192.168.1.xxx network. I keep a W10
machine on the 192.168.2.x network, primarily to access the chewy.com
web site which, since about June, serves my Debian machines a blank
white page.
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. Several people (including myself) have responded saying
that chewy.com works just fine for them from a Debian web browser.
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;
in a follow-up, they said they've tried Firefox, Chromium, and Brave.
Other people have reported that it works in Firefox and Chrome.
* 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.
* 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.
* 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. 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?
OK, add another item to the list:
* Server-side blocking. Whether based on the client's IP address or
user agent or cookies or any other data, the web server might be
rejecting this client's requests specifically.
If you go to any web site that reports your IP address (for example, ><http://wooledge.org/myip.cgi>), do you get the same address from
the Debian system and from the Windows system?
I routinely get that "blank white page" result in firefox here, and
find that fiddling with the settings in the noscript plugin often
fixes it. OTOH, if a web site wants to be *that* obnoxious I'll
often decide that they're not worth the trouble of bothering
with. :-)
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).
"Roy J. Tellason, Sr." <roy@rtellason.com> wrote:
... if a web site wants to be *that* obnoxious I'll often decide that
they're not worth the trouble of bothering with. :-)
+1
On Sun, Nov 17, 2024 at 09:34:00 +0000, debian-user@howorth.org.uk wrote:
I was the 'guy in England', but that's irrelevant because the problem
there was sites that were discriminating based on the user-agent string supplied by the browser. Here it's simply a question of whether the
browser has javascript enabled. Same symptoms, completely different
cause.
Except the OP in this thread claims he has never disabled Javascript
(didn't even know what that *meant*), and in fact does not yet know
what's causing the problem.
"Russell L. Harris" <russell@rlharris.org> wrote:
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).
I was the 'guy in England', but that's irrelevant because the problem
there was sites that were discriminating based on the user-agent string supplied by the browser. Here it's simply a question of whether the
browser has javascript enabled. Same symptoms, completely different
cause.
On Sun, Nov 17, 2024 at 09:34:00 +0000, debian-user@howorth.org.uk
wrote:
"Russell L. Harris" <russell@rlharris.org> wrote:
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).
I was the 'guy in England', but that's irrelevant because the
problem there was sites that were discriminating based on the
user-agent string supplied by the browser. Here it's simply a
question of whether the browser has javascript enabled. Same
symptoms, completely different cause.
Except the OP in this thread claims he has never disabled Javascript
(didn't even know what that *meant*), and in fact does not yet know
what's causing the problem.
On Sun, 17 Nov 2024, debian-user@howorth.org.uk wrote:
"Roy J. Tellason, Sr." <roy@rtellason.com> wrote:
... if a web site wants to be *that* obnoxious I'll often decide
that they're not worth the trouble of bothering with. :-)
+1
My +1 as well, Roger
On Sun, 17 Nov 2024 09:30:20 -0500
Greg Wooledge <greg@wooledge.org> wrote:
Except the OP in this thread claims he has never disabled Javascript (didn't even know what that *meant*), and in fact does not yet know
what's causing the problem.
I've seen the odd website that FF won't display, even with No-Script disabled. So far, such sites seem to work with Opera. Never bothered investigating further.
Yep, if a web designer can't put a single character on a screen
without using JS, the rest of his offering is not likely to be worth
making an effort to look at.
On Sun, Nov 17, 2024 at 09:34:00 +0000, debian-user@howorth.org.uk
wrote:
"Russell L. Harris" <russell@rlharris.org> wrote:
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).
I was the 'guy in England', but that's irrelevant because the
problem there was sites that were discriminating based on the
user-agent string supplied by the browser. Here it's simply a
question of whether the browser has javascript enabled. Same
symptoms, completely different cause.
Except the OP in this thread claims he has never disabled Javascript
(didn't even know what that *meant*), and in fact does not yet know
what's causing the problem.
Joe writes:
Yep, if a web designer can't put a single character on a screen
without using JS, the rest of his offering is not likely to be worth
making an effort to look at.
They don't use JS. They use "website builders" that produce
unreadable masses of HTML and JS that pull in chunks of JS from a
dozen or more random sources out on the Net. The designers neither
know nor care what that JS does as long as it puts the dancing doggie
in right place on your screen.
Anyway, as I think we all mostly agree, there is some misconfiguration
going on here that is causing OP's web browsing experience on Debian to
be compromised.
On Sun, Nov 17, 2024 at 02:41:24PM +0000, Andy Smith wrote:
Anyway, as I think we all mostly agree, there is some misconfiguration going on here that is causing OP's web browsing experience on Debian to
be compromised.
I have here a spare machine. In the hope of resolving the matter in
the company of experts, I propose to do another installation of
Debian, using netinst with the "expert" option.
I am going to instruct Debian to use the entire drive, and to use my
approx server as the Debian repository.
As soon as the installation of Debian completes, I plan to use
Synaptic to install Firefox-ESR and Chromium from the Debian
repository.
At this point, I can connect the machine directly to the modem
provided by the ISP.
Have I forgotten anything?
On Sun, 17 Nov 2024 09:47:20 -0600
John Hasler <john@sugarbit.com> wrote:
Joe writes:
Yep, if a web designer can't put a single character on a screen
without using JS, the rest of his offering is not likely to be worth making an effort to look at.
They don't use JS. They use "website builders" that produce
unreadable masses of HTML and JS that pull in chunks of JS from a
dozen or more random sources out on the Net. The designers neither
know nor care what that JS does as long as it puts the dancing doggie
in right place on your screen.
Yes, I realise that, but it would not be beyond even the most feeble
website designer to manually edit in a string saying something like 'JavaScript is necessary to display this page', which would be
overwritten by the content if JS is enabled.
OK, it's not much, but it's less hostile than a completely blank screen
which says 'we don't give a damn about you if you don't do things our
way'.
I've seen 'HTML' embedded in emails, I know nobody has manually typed
the thousands of characters of stupid formatting markup, and certainly
almost nobody actually makes an effort to display something useful for text-only readers. I don't expect the average web surfer to know that
there's more than one way to do things, but I do expect those who
aspire to create content to be a bit more aware.
I have here a spare machine. In the hope of resolving the matter in
the company of experts, I propose to do another installation of
Debian, using netinst with the "expert" option.
On Sun, 17 Nov 2024 17:39:36 +0000
"Russell L. Harris" <russell@rlharris.org> wrote:
I have here a spare machine. In the hope of resolving the matter in
the company of experts, I propose to do another installation of
Debian, using netinst with the "expert" option.
Possibly this is overkill. Try shutting down your browser, then moving
aside your browser configuration directory (i.e. renaming it), then
starting up your browser again. This will usually force the browser to >re-initialize everything.
With the approx server, reinstallation is quick, and this being a
spare machine, there is no need to install a bunch of packages and set
up the desktop. Anyway, the installation is complete, and now I have
a pristine installation, but the problem remains. I am all ears.
The only customization I made was to install xfce rather than gnome.
I am using the browser (Firefox ESR) which was installed automatically
with the desktop (xfce).
For the installation (inside the LAN), the ip address was
192.168.1.48. That resulted in a blank screen for chewy.com.
Now I connected the machine direct to the ISP-supplied modem, and used auto-configuration, reporting an ip address of 192.168.11.12. This
also results in a blank screen for chewy.com. But arcamax.com
displays properly.
wooledge.org/myip.cgi reports an ip of 38.100.76.16.
this address, so server-side Geo IP blocking seems unlikely.
If no browser extensions have been installed, then the most likely causes >would seem to be a client-side firewall, or name resolution shenanigans.
What's in your /etc/resolv.conf file?
If you change the /etc/resolv.conf file to contain only "nameserver 1.1.1.1" >(without the quotes, of course), does anything change?
On Sun, Nov 17, 2024 at 08:33:25PM -0500, Greg Wooledge wrote:
https://www.iplocation.net/ip-lookup reports a location of Texas for
this address, so server-side Geo IP blocking seems unlikely.
A rural area a little south of Austin. My ISP is RTA (rtatel.com).
On Mon, Nov 18, 2024 at 09:18:27AM +0700, Max Nikulin wrote:
Hope, you did *not* log in into a Firefox account to sync bookmarks, add-ons, and some preferences.
No, I did not.
You may try to open Web Developer Tools (under "More tools" in the hamburger menu, [F12] or [Ctrl+Shift+I]).
Are there any errors in Console ([Ctrl+Shift+K])?
A bunch. Too many for me to type.
I tested https://www.chewy.com/ on a clean install of FireFox ESR with no >plugins and the site works fine.
Try purging Firefox and reinstalling.
sudo apt purge firefox-esr
sudo apt install firefox-esr
Google Chrome also works fine with no issues as well.
Hope, you did *not* log in into a Firefox account to sync bookmarks,
add-ons, and some preferences.
You may try to open Web Developer Tools (under "More tools" in the
hamburger menu, [F12] or [Ctrl+Shift+I]).
Are there any errors in Console ([Ctrl+Shift+K])?
The Network tab ([Ctrl+Shif+E]) is another source of insights, but it >requires some experience. What is the status of first record after
reload (Initiator: document)? Are many other resources loaded?
For Firefox the authoritative source is about:networking#dns rather
than /etc/resovl.conf since DNS over HTTPS is likely enabled by
default. There is about:networking#dnslookuptool for queries.
On 18/11/2024 09:47, Russell L. Harris wrote:I thank you.
On Mon, Nov 18, 2024 at 09:18:27AM +0700, Max Nikulin wrote:
You may try to open Web Developer Tools (under "More tools" in the >>>hamburger menu, [F12] or [Ctrl+Shift+I]).
Are there any errors in Console ([Ctrl+Shift+K])?
A bunch.?? Too many for me to type.
Right click on any entry allows to copy or to save all messages.
hint: http://paste.debian.net/)And I thank you again.
On Mon, Nov 18, 2024 at 10:30:06AM +0700, Max Nikulin wrote:
On 18/11/2024 09:47, Russell L. Harris wrote:
On Mon, Nov 18, 2024 at 09:18:27AM +0700, Max Nikulin wrote:
You may try to open Web Developer Tools (under "More tools" in
the hamburger menu, [F12] or [Ctrl+Shift+I]).
Are there any errors in Console ([Ctrl+Shift+K])?
A bunch.?? Too many for me to type.
Right click on any entry allows to copy or to save all messages.I thank you.
hint: http://paste.debian.net/)And I thank you again.
That was really easy!
The message id is russell#1
Am 16.11.24 um 05:42 schrieb Greg Wooledge:
If your Windows machine can run an ssh daemon that you can log into,
then you could use it as your SOCKS proxy, though I have no idea how
you'd go about setting up an sshd on Windows.
Should not be to hard using Windows' built-in WSL (you can even run most parts of Debian on it) or the free Cygwin environment.
Perhaps try Magic-Wormhole:
https://magic-wormhole.readthedocs.io/en/latest/
apt install magic-wormhole
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 163:32:43 |
| Calls: | 10,385 |
| Calls today: | 2 |
| Files: | 14,057 |
| Messages: | 6,416,510 |