What happened to our website? It is not what you think.
What happened to our website? It is not what you think. Three of the most important blogs we have ever posted were blocked from many of our readers. Ironically, this was not done by leftists. It was a complicated glitch. It was an issue of technology, not politics. However, we do believe the enemy was involved.
We believe we have solved the problem, and we want to encourage you to read the last three blogs, if you have not read them yet. Our site is safe and should be working perfectly, as it normally does.
We have asked Larry Rutledge, who handles a great deal of our technology, to explain what happened. –Mario Murillo Ministries
Here is Larry Rutledge:
“To fully explain what happened would require a lot of technical back story. In simplest terms, we were using a delivery network to ensure the site is always available around the world, in both accessibility and speed.
“The service we were using had a bug, and was being decommissioned. In that process, I moved the site to another similar service, CloudFlare. However, Cloudflare had some issues that impacted us and I needed to move to a secondary network in order to help share the load.
“The two primary things that went wrong in that process:
1) I did not properly disconnect us from the original network, and,
2) it required a couple of steps to fully disconnect from Cloudflare.
“The first issue, not properly disconnecting from the original network, is what caused the server to come to a crawl every time a new blog was posted, because it was trying to push the information to a disconnected network.
“The second issue, disconnecting from Cloudflare, required making some significant configuration changes that unfortunately required 24-48 hours to fully complete. In the interim, it can sometimes make the site appear to be offline, which is what we observed this morning.
“Both of these issues have been fully resolved and should not cause any further problems.
“In addition, I confirmed that our secure encryption is still in place and working correctly. I also replaced the security certificate to ensure it was not impacted by any of the changes.
“It was an unfortunate combination of issues that, on their own, would have caused minor hiccups. But because they occurred simultaneously, they made the site appear offline, unresponsive and potentially insecure.
“I apologize for the headaches this caused. And I will continue to monitor the site. But we should be back on track now.”
Thank you for your understanding! -Larry Rutledge
No comments:
Post a Comment