{"id":196,"date":"2020-03-20T12:49:23","date_gmt":"2020-03-20T11:49:23","guid":{"rendered":"https:\/\/blog.remyblom.nl\/?p=196"},"modified":"2021-05-26T16:08:54","modified_gmt":"2021-05-26T14:08:54","slug":"stop-wordpress-with-bitching-about-my-install","status":"publish","type":"post","link":"https:\/\/blog.remyblom.nl\/?p=196","title":{"rendered":"Stop WordPress with bitching about my install…"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

I recenlty moved my WordPress installation to another server; the one it was on was acting slow most of the time, which annoyed me in some cases. But now on the new server I get this bitching screen again when I run Tools > Site Health. <\/p>\n\n\n\n

I want a healthy site!<\/p>\n\n\n\n

One or more required modules are missing<\/h2>\n\n\n\n

The only required module seams to be gd<\/code>, so I install it, and the optional zip<\/code>. I don’t like imagick<\/code> so I skip that.<\/p>\n\n\n\n

$ doas pkg_add php-zip php-gd wget\n$ doas mv \/etc\/php-7.3.sample\/* \/etc\/php-7.3\/\n$ doas rcctl restart php73_fpm<\/code><\/pre>\n\n\n\n
The REST API encounted an error\/Could not reach WordPress.org\/Your site could not complete a loopback request<\/h2>\n\n\n\n
These three problems all have the same error message:<\/p>\n\n\n\n
Error: [] cURL error 6: Could not resolve host: [some domain]<\/em><\/p>\n\n\n\n
Looks like someone has trouble with dns resolving… Now the weirdest thing is that on my previous server, this was all working just superfine, but on the current server I just don’t get this error out of the way. Google (or any other search-engine) is not of any help. People fixing things with putting stuff in \/etc\/hosts<\/code>, or putting the Google DNS servers in \/etc\/resolv.conf<\/code> are not fixing problems, just mere circumventing them.<\/p>\n\n\n\n
I have done quite some research in this issue and as it turns out any php run thru my webserver is not able to resolve any hosts, functions like gethostbyname<\/code> or dns_get_record<\/code> return nothing on this new server (and work like a charm on my old one…. GRRRR!!!) <\/p>\n\n\n\n
Also interesting to know is that the functions above work perfectly fine when I run the php-scripts from the command-line:<\/p>\n\n\n\n
$ php -f test.php\nArray\n(\n    [0] => Array\n        (\n            [host] => akira.hku.nl\n            [class] => IN\n            [ttl] => 100\n            [type] => A\n            [ip] => 192.87.219.165\n        )\n\n)<\/code><\/pre>\n\n\n\n
Background updates are not working as expected<\/h2>\n\n\n\n
This one is easy to solve, just make sure that the files of WordPress are of the right owner:<\/p>\n\n\n\n
$ cd \/var\/www\/vhosts\/remyblom.nl\/blog\n$ doas chown -R www:www .<\/code><\/pre>\n\n\n\n
Temporary Conclusion<\/h2>\n\n\n\n
The problem with cURL seems pretty consistent, although my two servers and their installations are so very equal, it’s super-scary. But I will continue the search, other pointers might be:<\/p>\n\n\n\n