GOOGLE CHROME ERROR PAGE - DUE TO NULLS IN HEADER OF ROUTER SETTINGS PAGE

[Retired_Member]

There is an emerging issue for users of Google Chrome Browser

My NetGear Router D7000 – Nighthawk AC1900 WiFi VDSL/ADSL Modem Router

If I try to access http://192.168.0.1/ using Chrome, Chrome gives an error page.

Accoding to Googles Chromium Developers, this issue can only be solved by NetGear, so for all routers which have this issue, they will need a firmware update to solve the problem of having Nulls in the Header of the Router Setup Pages

Before commenting, please read the following discussion at Chromium Issues :

https://bugs.chromium.org/p/chromium/issues/detail?id=929170

See also the linked Duplicate issue there.

Note the usual advice has all been tried, clearing cache etc.

If I use Microsoft Edge Browser logging in to my router is not a problem. I also temporarily installed the NetGear Genie and tried logging in to the router with that .. Again no issues.

But for however many people out there will be trying to login to similar routers with todays number 1 market share browser, Google Chrome, they will not be able to get access if they are running the latest Stable version of Chrome, v72 or later.

I guess not all router models will have such issues, unless they all have Nulls in their setup pages headers for some strange reason ?

But it looks like the Chromium devs are unwilling to undo this change, because Nulls can potentially cause issues.

Lastly :

How do we get someone within NetGear Development to take notice of this issue ???

Contacting someone in an appropriate department in NetGear seems to be an impossible task so far, I fired an email to sales@ with a note to pass it on to someone relevant, but I dont have high hopes of that working, and have not received any kind of response / acknowledgement.

[antinode]

> [...] having Nulls in the Header of the Router Setup Pages [...]

   Has the source and/or location of the NUL characters been determined?

[michaelkenward]

---

@Retired_Member wrote:

I guess not all router models will have such issues, unless they all have Nulls in their setup pages headers for some strange reason ?

---

No issue here with R7800 on latest firmware.

---

Contacting someone in an appropriate department in NetGear seems to be an impossible task so far, I fired an email to sales@ with a note to pass it on to someone relevant, but I dont have high hopes of that working, and have not received any kind of response / acknowledgement.

---

Something for @DarrenM, @ChristineT or one of the other fine Netgear minders here.

[Retired_Member]

---

@antinode wrote:

> [...] having Nulls in the Header of the Router Setup Pages [...]

   Has the source and/or location of the NUL characters been determined?

---

See comment #9 by mmenke@chromium.org on the Chromium issue page linked in the OP

[quote]

It's definitely returning nulls, and no proxy in use, so this is likely coming directly from the modem:

HTTP/1.1 401 Unauthorized
Set-Cookie: <not including this here, though it's just a session token>
Server: 
Date: Thu, 07 Feb 2019 04:56:14 GMT
WWW-Authenticate: Basic realm="NETGEAR D7000"
Content-Type: text/html
Content-Language: en-US,en;q=0.9
X-Frame-Options: SAMEORIGIN
<NULL>
9
X-XSS-Protection: 1;mode=block
<NULL>
X-Content-Type-Options: nosniff
<NULL>Connection: close


I assume you've tried updating your firmware?

[/quote]

The information was gleaned from a log I created, and the source is from the router

Those <NULL> lines are the problem, and why Chrome v72 or above will not access a router page which contains them.

Obviously not all router models will have the same issue, nor use the same firmware.

[Retired_Member]

---

Something for @DarrenM, @ChristineT or one of the other fine Netgear minders here.

---

Thank you I have PM'd Darren, fingers crossed he will be able to ping the relevant department.

Edit : Good news - Darren has escalated this to their engineers

[michaelkenward]

Nice one. Let's hope that they get a response.

[gbensonii]

I can confirm that this is happening on my router (Netgear C6300 - Firmware V3.01.26) as well. I am running a network with several Windows 10 systems networked together using the C6300 and other devices.

When I use Google Chrome and go to http://192.168.0.1 I get the error:

This page isn’t working

192.168.0.1 sent an invalid response.

ERR_INVALID_HTTP_RESPONSE

When I use MS Edge and go to http://192.168.0.1 the page that was showing is just refreshed as if I never entered the new URL.

When I use Firefox I am able to access the Netgear Router page for my device.

[antinode]

   "Google Chrome Browser" is not a very detailed description of
anything.  I seldom use Chrome on my Macs, so I know nothing, but around
here:

      Version 71.0.3578.98 (Official Build) (64-bit) worked.
      Version 72.0.3626.96 (Official Build) (64-bit) fails.

   I have "Automatic updates are turned on", so additional testing would
involve actual effort.

[baget]

I'm having the same issue, after upgrading the firmware.

[gbensonii]

@antinode - The version I am using that fails is Google Chrome Version 72.0.3626.96 (Official Build) (32-bit) with autoupdates turned on.

[Retired_Member]

Chromium developers have already determined which version of Chrome introduced the problem, see comment #5 here https://bugs.chromium.org/p/chromium/issues/detail?id=927364

(thats the issue my issue on chromium.org was merged with, see comment #14)

[myusrn]

I'm having this issue on my c6300|ac1750 cable modem / router / wifi device and detailed it in the duplicate issue post https://community.netgear.com/t5/Cable-Modems-Routers/chrome-cannot-access-192-168-0-1-routerlogin-c...

As noted in that duplicate issue post i've got spectrum [  / time warner cable ] deployed firmware version V2.01.26 and am running windows 10 october 2018 update [ version 1809 / 17763.292 ] with current chrome 72.0.3626.92 install and the out of the box edge and internet explorer browsers work.

Is the state of this problem that we are not waiting for a netgear firmware update, that spectrum [ / time warner cable ] pushes out, or an updated chrome browser drop?

[herexf]

Thank you

I assumed my router got some issue, then I tried reset and re-flashed the firmware via tftp.

Spent 3 hours....

Because I'm using android phone, so whatever my laptop or mobile, both cannot connect to 192.168.0.1....

[Rafe_C]

Same error

Loaded new firmware - doesn't change it

Cannot use Chrome to access the router - other browsers and Genie ok (Except genie is unusable because it is tiny on my 4k screen).

... Ralph

[Lluke]

I've tried to reply twice with an excerpt of Chromes NetLog output that shows the null bytes in the header and both have been quarantined. 

So I won't post it again, but I can confirm that when connecting to the admin page of my D7000 (current firmware 1.0.1.70) null bytes are included in the http header response and Chrome 72 (and 73 beta) will refuse to connect with a ERR_INVALID_HTTP_RESPONSE message.

[Tiberious4691]

I am experiencing exactly the same issue

This page isn’t working

192.168.100.104 sent an invalid response.

ERR_INVALID_HTTP_RESPONSE.

I have been working in IT and supporting networks for 20 years so I have a bit of an idea of what is supposed to happen, Netgear have been caught short again by not following significant changes in browser development. Google will not change or compromise the security of their world dominating browser so perhaps Netgear should get on board and provide updated firmware as quickly as possible to solve this issue. A quick inspection of the HTTP div frame and body being returned displayed far too many NULLS against numerous settings nearly 100 of them! If you use firefox like other members have done, it is a work around for now, Firefox are likey to follow suit as will Microsoft Edge, what Google does today the others will do tomorrow. In essence if Netgear do not release an update soon to fix this problem none of us will be able to access the routers admin pages!! This would render the router useless when a problem occurs as it often does. £165 for the D7000 I expected this to be better supported. I will assess the next router I buy with a little more caution. The problem only exists currently for Google Chrome users using the current version 72 or later. The issue does not exist on earlier versions.

[blanchg]

Same issue here, good job finding the root cause, now we just need an update to fix this