Genesis

I check my WordPress Websites periodically, sometimes with longer intervals than I really like, but I do check as regularly as I can, being reminded what a security risk a Website can pose for a server, if it is not regularly updated.  I do all of the updates in the WordPress dashboard and save a backup at the end of all of the updates and new posts.

With gigagenesis.net that is being hosted by Binil, it is usually quick and easy.  I rarely need to go into cPanel and only need to work with the WordPress Dashboard. This time round however it was a great surprise to find gigagenesis down.  It was the very first time since Binil had been hosting us that I found the Website down so I automatically thought WordPress issues.  It had to be something technical with the database.

It was wonderful to navigate Binil’s cPanel again after a very long absence.  cPanel said the Gigagenesis.net database was OK.  Then little by little I found the reason that the Website was down was that the name servers were not working any longer.

So for me it was fun to try and troubleshoot this, as strictly speaking everything had been in great shape with the server.  cPanel was very current and up to date.  Accessing Binil’s discussion forum had been effortless as well.  There was no reason for the Website not to work once the DNS had been sorted out.

So  I was wondering whether I could use my domain name to register my own name servers using Binil’s cPanel IP.  I lucked out, as that worked. I was able to register name servers with Namecheap using Binil’s cPanel IP.  Took a few minutes, and then the Website was up and running again. Effortlessly.  Great learning experience, and also great to use cPanel again after all of this time.

Again, thank you Binil for still supporting us with excellent cPanel hosting after all of this time.   This is much appreciated.

I use the All-in-one WP Migration tool for making backups.  Very simple and easy to use and never a problem.  However this time round when I was updating my plugins it was coming up with a strange error message:

| Error: cURL error 28: Connection timed out after 10000 milliseconds

So WordPress Techs came up with the following suggestion that solved the problem.  I thought I’d post it here for future reference as it worked.  The error message did come back, but I had no issue with making a backup:

https://wordpress.org/support/topic/error-curl-error-28-connection-timed-out-after-10001-milliseconds-http_reques/

Hi @kirkofthefleet ,
The error detail “http_request_failed” is missleading you. Either for https or https the error will be the same.

The problem here could be simply a performance issue. As the error message says, the loopback request is aborting after 10 seconds without receiving a response.
So, the first thing that I’d try is to extend the timeout limit to something longer than 10 seconds.
If you are comfortable with some basic coding, you can achieve this by placing the following snippet into your theme functions.php file:

function __extend_http_request_timeout( $timeout ) {
    return 60; // seconds
}
add_filter( 'http_request_timeout', '__extend_http_request_timeout' );

(if it is third party theme, you will want to create a child theme to avoid lossing your changes, or put this into a custom plugin).

If you still get a timeout after 60 seconds, then there is definitely something failing in your API endpoint.

Cheers

So three months on after Gigarocket stopped to provide shared hosting, and the hosting provided by Binil is still excellent.  Today I updated my WordPress site.  Checked up on cpanel, and everything is still as great as it was in December when this hosting was provided the first time.

Thanks to Binil for continuing to provide this free hosting.