A 418 is 100% a DreamHost thing. We use it for a number of things, but basically it’s our way to know weird stuff is happening. We incorporated it into our pre-flight check so that before we try to update someone’s site, we know for sure that it’s up, it’s working, and it’s WodPress.
The 418 there means it cannot successfully CURL your site to get headers etc.
But… if this is always happening when iThemes is active, it means that something iThemes is doing is blocking that CURL check, and preventing the command from seeing your site.
It very much could be a combo of this plugin (or rather a specific setting in this plugin) that is causing the error and, since DreamHost makes use of the teapot, it’s only showing up here.
Are there any options in iThemes that would block a call like this:
// parse URL.
$parsed_url = wp_parse_url( $url );
$timeout = 10;
$ch = curl_init();
curl_setopt( $ch, CURLOPT_URL, $url );
if ( false !== $ip ) {
curl_setopt( $ch, CURLOPT_RESOLVE, array( $ip ) );
curl_setopt(
$ch,
CURLOPT_RESOLVE,
array(
'www.' . $parsed_url['host'] . ':443:' . $ip,
$parsed_url['host'] . ':443:' . $ip,
'www.' . $parsed_url['host'] . ':80:' . $ip,
$parsed_url['host'] . ':80:' . $ip,
)
);
}
curl_setopt( $ch, CURLOPT_RETURNTRANSFER, 1 );
curl_setopt( $ch, CURLOPT_TIMEOUT, $timeout );
$http_respond = curl_exec( $ch );
$http_respond = trim( strip_tags( $http_respond ) );
$http_code = curl_getinfo( $ch, CURLINFO_RESPONSE_CODE );
if ( in_array( $http_code, array( '200', '302' ) ) ) {
return true;
} else {
return false;
}
curl_close( $ch );
And yeah, I know straight up curl is bad and I’d rather use wp_remote_get, but weirdly we needed it to be able to run when that won’t, thanks to some services.
$ip is passed from the command as the IP of the server, so it’s just asking itself. This gets us around situations where someone has a firewall like Cloudflare that makes the lookups chancy.
$url is literally the domain – we just pass it around a lot.
