A week or more after a major disruption in our hosting service, Bacon’s Rebellion continues to experience technical difficulties. I am hearing from many of you that when you call up the blog, you land on an out-of-date page and can find no way to find the current posts. The solution is simple: Click on the “Home” button.
In the meantime, we will continue to try to get to the root of the problem.
— JAB
(comments below)
(comments below)
This is happening not only on Windows machines but also chomebooks and android phones.
It’s happening on machines that have never accessed BR before.
nope – here’s what you get:
Bad Request
Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.
Apache/2.4.43 (Ubuntu) Server at 127.0.0.1 Port 80
That error leads me to believe it’s being generated on the device you used to access this site. Two reasons: (1)ubuntu is often used as a desktop operating system (2) 127.0.0.1 is the loopback address and that message indicates that the request came in on 127.0.0.1 — not possible for a request that came over the internet.
5 different computers …. some Win10 and some Chromebooks and one is an android phone – all have the same problem.
Do they still exhibit the problem if you use them on Wi-Fi that is not your own?
Well the phone does on the cellular network also…
I’ll take one of the chrombooks down to a local wi fi and see.
Do you have a content filter on your network?
Hint – Remove your obsolete and syntactically challenged “There are currently no comments highlighted.” See if that helps.
a what?
This just started…. a couple weeks ago… prior to that – for YEARS – no problem except when BR had some occasional issues… but then it got back to normal.
A content filter, aka “net nanny”…some people use them to filter objectionable content that they may not want their kids to see. Many businesses use them to filter objectionable content they don’t want their employees seeing at work.
2 separate Wi FIs and 2 separate cellular networks – same problem.
And I do not have this problem on other WordPress blogs like Power to the People.
I’m not seeing the problem here.
What happens if on a Windows 10 box that’s having the problem you go to a command prompt and run this:
nslookup baconsrebellion.com
I get the following:
C:\Users\Brian>nslookup baconsrebellion.com
Server: router.lan
Address: 10.10.10.1
Non-authoritative answer:
Name: baconsrebellion.com
Addresses: 2606:4700:20::ac43:4af6
2606:4700:20::681a:cca
2606:4700:20::681a:dca
104.26.12.202
104.26.13.202
172.67.74.246
Server: Wireless_Broadband_Router.home
Address: 192.168.1.1
Non-authoritative answer:
Name: baconsrellion.com
Address: 92.242.140.21
when I key baconsrebellion.com
I get the web page but it’s an older post on budgeting
when I copy the link of the header “baconsrebellion.com”
I get this
https://www.baconsrebellion.com/
and if I click this, I get:
Bad Request
nslookup baconsrebellion.com/wp
Server: Wireless_Broadband_Router.home
Address: 192.168.1.1
Non-authoritative answer:
Name: https://www.baconsrebellion.com/
Address: 92.242.140.21
Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.
Apache/2.4.43 (Ubuntu) Server at 127.0.0.1 Port 80
PM me …. for anything more….
Your problem is with your router, or Verizon, or both.
See:
Get with Cox exactly as described. Winders problem, IOS no problem.
I just noticed a typo you made.
please do this:
nslookup baconsrebellion.com
and only that and let me know what the results are.
If you can give me an email, I’ll continue offline… or get Jim B to send it to me … but not comfortable doing this online
Leave a Reply
You must be logged in to post a comment.