Well it’s happened again of course. Blog error #400 and my blog won’t publish at all tonight. I struggled with Tuesday night’s blog but finally with a lot of patience it finally did publish. But not tonight. So, I’m dead in the water with no immediate solution……………………
I have also been having fits with the internet down south here in Rockport Tx.
ReplyDeleteSo sorry, Al. Thanks for letting us know. Good luck. Hope y'all get it figured out. Hope all else is good.
ReplyDeleteCalling Kelly... Kelly to the Blog Platform, please...
ReplyDeleteSo sorry to hear this news. You have been on such a great roll lately with great posts and photos. Hope you are able to get it going again.
ReplyDeleteClear your "cookies", delete them for this website only, reboot your computer, then it should work.
ReplyDeleteAnd ... log out and log back into Blogger
DeleteIt seems to be a wide spread problem Steve. Probably something to do with a Google change again.
DeleteNot fun with that, good luck. In the meantime keep enjoying the desert.
ReplyDeleteI'm having the same problem. So frustrating.
ReplyDeleteI had the blogger "Error 400 Bad Request" a couple years ago using Google's Blogger service. I did a blog on what worked for me: https://ruffinitwithrufus.blogspot.com/2017/03/open-live-writererror-400-bad-request.html
ReplyDeleteThanks for the response Jeff. We tried this fix Wednesday night but to no avail although it has worked well in the past. We understand Google did an update on January 15th and that may have kicked the #400 error off for a number of Open Live Writer users. Kelly sent a 'Tweet' to the main GitHub guy but we haven't heard back yet. He helped us out with something last year as I recall.
DeleteThe GitHub guy responded and forwarded Kelly's Tweet. (we hope to the Tech guy at GitHub) Thurs 9 a.m. Jan 17
DeleteWill you please share if you get some good advice? I wish I had a Kelly but no such luck.
DeleteYes we will do that.
DeleteThanks for the information Al. Good luck with the issue. With Kelly on top of it I'm sure you'll be up and running again in no time.
ReplyDeleteShoot the computer and get a new one (grin).
ReplyDeleteYes, please do share. I'm getting the same error. It's so aggravating, I have things to say!
ReplyDeletePeter had the same error response to day, Jan 17. :(
ReplyDeleteO damn well as long as your ok
ReplyDeleteHi Al take your laptop to a library and use free internet if there is one nearby. That is what I end up doing when I'm on the road. Enjoying all your blogs!
ReplyDeleteMissed your posts here in Costa Rica.
ReplyDelete