WHMCS cron job says ioncube not installed despite ioncube being installed

This issue drove me batty for an hour – after installing WHMCS with PHP’s Ioncube extension installed successfully the cronjob required by WHMCS would not run, complaining about Ioncube not being installed. Yet php -v showed that it was in fact installed.   What gives?   Turns out that Ioncube had been enabled for PHP-FPM in the following directory:  
  …but had not been enabled in this directory also:  
  …which is another directory that needs the same config file in. In my server’s case the config file was named 00-ioncube.ini and consisted of the following:  

zend_extension = “/usr/lib/php/20151012/ioncube_loader_lin_7.0.so”

  And with that, voila, cron job works. Can’t get that hour of my life back, though.   Update: For the php7.1 servers the zend_extension line read:  

zend_extension = “/usr/lib/php/20160303/ioncube_loader_lin_7.1.so”

PHP contact form returns 504 gateway error after moving to Digital Ocean

This one had me scratching my head for a while – using php7.0-fpm and the latest nginx on Debian 8 Jessie I was seeing our PHP contact form working correctly but returning a Gateway 504 error upon submission, which was resulting in a great deal of resubmitted forms and error notifications from users.   This only started occuring after we moved our site to Digital Ocean – it turns out that it was a IP priority issue and the following resolved it:  
vim /etc/gai.conf
  and uncommenting the following line:  
precedence ::ffff:0:0/96  100

Then a reboot. Voila, the contact form worked properly again.