You may have noticed two negatives about the blog: slow loading and 502 errors. I’ve also been experiencing them. Often:<\/p>\n
\nERROR 502 – BAD GATEWAY
\nWhy am I seeing this page?<\/strong><\/p>\nThe server that your request has reached is acting as a gateway or proxy to fulfil (sic) the request made by your client.<\/p>\n
Web Browser => Web Front-End => Web Back-End<\/p>\n
This server (Web Front-End) received an invalid response from an upstream (Web Back-End) server it accessed to fulfil the request.<\/p>\n
In most cases this will not mean that the upstream server is down, but rather that the upstream server and the gateway\/proxy do not agree on the protocol for exchanging data.<\/p>\n
This problem is most commonly caused when there is a problem with IP communications between the Web Front and Back-Ends. Before you attempt to resolve this problem you should clear your browser cache completely.<\/p>\n
Our support staff will be happy to assist you in resolving this issue. Please contact our Live Support or reply to any Tickets you may have received from our technicians for further assistance.<\/p><\/blockquote>\n
Those capital-T (support) Tickets they mention in the last paragraph don’t exist and haven’t since the Borg took over JustHost. However, I did reach a chat-line agent today, who assured me in her best boilerplate that the 502 errors are entirely due to<\/a> the giant SQL databases we’re not running, the DDoS attacks we’re not under, or the poorly coded PHP scripts we don’t have. Barring that, the errors are completely the fault of our WP theme or plugins. In no way is it even remotely possible that either the errors or the slowness are in any way a problem of the hosting company.<\/p>\n
Never mind that the identical errors and identical slowness we were having as we developed the member-site-to-be last week went away the instant we moved the soon-to-be site from JustHost to HawkHost.<\/p>\n
And if you happen to notice that the link above is for BlueHost, it’s because the chat agent forgot which of the Borg’s hosts ClaireWolfe.com resides on. She even tried to have me log in at a hosting service I’ve never done business with. <\/p>\n
I do believe the company that acquired JustHost aspires to be a government someday. They have already achieved that level of efficiency, quality, and regard for their customers. Now all they need is guns to force us to use their services.<\/p>\n
I apologize for any troubles you’ve been having. We will eventually — as soon as feasible — move the blog away from the disastrously awful JustHost. But that has to wait until the member site-to-be is up and running. Then we’ll be out of here — and swiftly, too. You have my word.<\/p>\n
Meantime, please enjoy the content and thank you for your support and participation. And if you run into a PITA, remember this, too, shall pass.<\/p>\n","protected":false},"excerpt":{"rendered":"
You may have noticed two negatives about the blog: slow loading and 502 errors. I’ve also been experiencing them. Often: ERROR 502 – BAD GATEWAY Why am I seeing this page? The server that your request has reached is acting as a gateway or proxy to fulfil (sic) the request made by your client. Web Browser => Web Front-End => Web Back-End This server (Web Front-End) received an invalid response from an upstream (Web Back-End) server it accessed to fulfil the request. In most cases this will not mean that the upstream server is down, but rather that the upstream…<\/p>\n