Trying to access http://192.168.1.1 the screen remains blank
Categories
(Core :: DOM: Networking, defect)
Tracking
()
People
(Reporter: hwb3, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
Tried to access my modem through Firefox (192.168.1.1)
Actual results:
Nothing happened. The dot next to "New Tab" moved back and forth as normal when trying to load a page, but the screen remained blank for several minutes until I gave up and closed it.
Expected results:
The login screen for my modem configuration should have appeared, and as I have that set as my home page at Firefox startup, I note that this issue began with the last update to Firefox (76.0.1, 64-bit, Windows 10).
|
||
Comment 1•5 years ago
|
||
192.168.1.1
Hi, that is not a complete URL. Please include the protocol and a provide a full URL.
Wondering if this might be related to bug 1567826 and bug 1630003.
|
Reporter | |
Comment 2•5 years ago
|
||
(In reply to Harry Barr from comment #0)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
Tried to access my modem through Firefox (192.168.1.1)
Actual results:
Nothing happened. The dot next to "New Tab" moved back and forth as normal when trying to load a page, but the screen remained blank for several minutes until I gave up and closed it.
Expected results:
The login screen for my modem configuration should have appeared, and as I have that set as my home page at Firefox startup, I note that this issue began with the last update to Firefox (76.0.1, 64-bit, Windows 10).
(In reply to Andre Klapper from comment #1)
192.168.1.1
Hi, that is not a complete URL. Please include the protocol and a provide a full URL.
Wondering if this might be related to bug 1567826 and bug 1630003.
192.168.1.1 is the private IP address for accessing my DSL modem firmware. The modem is connected to my desktop PC via Ethernet cable. I am not sure what the protocol would be. It has never been necessary to enter http: or https: to access this hardware.
Additional info: my router remains accessible using its IP address 192.168.11.1 with no problems.
|
|
||
Comment 3•5 years ago
|
||
I understood that. My question was what is the COMPLETE address, including the protocol, that you are trying to access. "192.168.1.1" is NOT a complete address. It lacks the protocol (which is likely either "http://" or "https://").
|
|
Reporter | |
Comment 4•5 years ago
|
||
(In reply to Andre Klapper from comment #3)
I understood that. My question was what is the COMPLETE address, including the protocol, that you are trying to access. "192.168.1.1" is NOT a complete address. It lacks the protocol (which is likely either "http://" or "https://").
Understood. What Firefox is trying to access is:
(cut and paste from Options/Homepage and new windows)
|
|
||
Comment 5•5 years ago
|
||
In that case you might be at bug 1630003 comment 3 now. :)
|
||
Comment 6•5 years ago
|
||
Hi,
Unfortunately I'm not able to reproduce this issue on Windows 10. Anyway I'm setting component to Core - DOM: Networking for someone to take a look at this issue.
Thanks.
|
||
Comment 7•5 years ago
|
||
Maybe let's get a log. Can you go to about:networking#logging and follow the steps on https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging to get a log, just over the span of time in which you try to navigate to the URL in question? You could also try enabling the network console with ctrl-shift-e and seeing what it says. Is the request getting a response at all?
|
|
Reporter | |
Comment 8•5 years ago
|
||
(In reply to Andy Grover [:grover] from comment #7)
Maybe let's get a log. Can you go to about:networking#logging and follow the steps on https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging to get a log, just over the span of time in which you try to navigate to the URL in question? You could also try enabling the network console with ctrl-shift-e and seeing what it says. Is the request getting a response at all?
Okay, I got the log but don't see any way to send an attachment. I opened the log.txt-main.11344.moz_log with Notepad and here is what was there:
-- (begin log)
[Parent 11344: Main Thread]: I/Logger Flushing old log files
-- (end log)
Action initiated by clicking on Home button on menu bar. Screen remained blank for 2 minutes at which time I terminated logging.
Network console reported 1 request, 0/0 B transferred, Finish: 0 ms
Looks like it's not doing anything at all.
|
||
Comment 9•5 years ago
|
||
(In reply to Harry Barr from comment #8)
(In reply to Andy Grover [:grover] from comment #7)
Maybe let's get a log. Can you go to about:networking#logging and follow the steps on https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging to get a log, just over the span of time in which you try to navigate to the URL in question? You could also try enabling the network console with ctrl-shift-e and seeing what it says. Is the request getting a response at all?
Okay, I got the log but don't see any way to send an attachment. I opened the log.txt-main.11344.moz_log with Notepad and here is what was there:
"Attach new file" on the section of Attachment on top.
-- (begin log)
[Parent 11344: Main Thread]: I/Logger Flushing old log files
-- (end log)Action initiated by clicking on Home button on menu bar. Screen remained blank for 2 minutes at which time I terminated logging.
Network console reported 1 request, 0/0 B transferred, Finish: 0 msLooks like it's not doing anything at all.
It's pretty weird. If there's anything network console can observe, at least we have logging for those requests.
Harry, You mentioned this issue occurs after some update, right?
Could you help us to use mozregression to move this forward?
https://mozilla.github.io/mozregression/quickstart.html
Thanks.
|
||
Comment 10•4 years ago
|
||
No updates for more than 1 year.
|
|
||
Updated•3 years ago
|
Description
•