lxer.com times out on Nightly
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: nycitykpop, Unassigned)
Details
Attachments
(2 files)
lxer.com-down - Screenshot from 2021-02-05 04-36-14.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0
Steps to reproduce:
Open Firefox Nightly
Goto https://lxer.com
Actual results:
Lxer.com websites times out with no error message.
lxer.com loaded fine via web proxy (see attached screenshots)
Expected results:
The website should have loaded.
|
||
Comment 2•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
The non-https version of lxer.com is now loading with updated Nightly.
I don't know whether or not if the site has an SSL security certificate.
SSL version of https://lxer.com still doesn't load but just times out with no error message.
Even if the problem exists outside of nightly there should be some sort of error message indicating what is wrong i.e 404, etc...
Nightly just sits there doing nothing...
Finally, it says:
"The connection has timed out
The server at lxer.com is taking too long to respond.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Nightly is permitted to access the Web."
|
||
Comment 6•4 years ago
|
||
(In reply to Jeffrey G from comment #4)
SSL version of https://lxer.com still doesn't load but just times out with no error message.
Even if the problem exists outside of nightly there should be some sort of error message indicating what is wrong i.e 404, etc...
Nightly just sits there doing nothing...
I think it's nothing we can do here. Other browsers also can't connect to https://lxer.com.
Note that if we got 404 response, this means that we connected to the server correctly. In this case, the connection is not established successfully.
Description
•