Make Git ignore Mode changes

Sometimes I get tons of changes when doing git diff – even though I haven’t changed any of those files. This is then causing merges and issues when pulling new commits.

Solution that always works for me is to ignore change to file modes. E.g. permission changes.

git config core.fileMode false

Insightly CRM API can’t add a new TAG

If you are one of the unlucky ones in need of working with Insightly API, you have probably noticed there’s no way to create a TAG under Contact endpoint.

If you follow the documentation, you probably do a CURL request similar to this:


        $username = 'xxxxx'; // api key
        $ch = curl_init('https://api.insightly.com/v3.0/Contacts/');

        curl_setopt($ch, CURLOPT_HTTPHEADER, [
            'Content-Type: application/json',
            'Authorization: Basic '. base64_encode($username)
        ]);

        $dataString = json_encode(array(
            'FIRST_NAME' => 'First',
            'LAST_NAME' => 'Last',
            'EMAIL_ADDRESS' => 'test@test.sk',
            "TAGS" => array(
                array("TAG_NAME" => "TEST")
            )
        ));

        curl_setopt($ch, CURLOPT_POST, 1);
        curl_setopt($ch, CURLOPT_POSTFIELDS, $dataString);
        curl_setopt($ch , CURLOPT_HEADER, 1);
        curl_setopt($ch , CURLOPT_TIMEOUT, 30);
        curl_setopt($ch , CURLOPT_RETURNTRANSFER, TRUE);
        $return = curl_exec($ch );

        $header_size = curl_getinfo($ch, CURLINFO_HEADER_SIZE);
        $header = substr($return, 0, $header_size);
        $body = substr($return, $header_size);

And all you get in return is 400 Bad Request!
Even if you try to update existing Contact using https://api.insightly.com/v3.0/Contacts/{ID}/Tags endoing you won’t have any more luck.

The solution is simple – go back to 2.3 endpoints – the exact same post data works on 2.3!

Insightly has done a really poor job on their API ..

Bottom line – change https://api.insightly.com/v3.0/Contacts/ to https://api.insight.ly/v2.3/Contacts/

Can’t install Let’s Encrypt certificate through Plesk after update

If you have just updated Plesk and server to latest packages, you might find yourself having issues with Let’s Encrypt. If you get following error while installing certificate from Plesk

Could not obtain directory: cURL error 6: Could not resolve host: acme-v01.api.letsencrypt.org 2; Name or service not known (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)

Your openssl has probably been updated as well.

Simply restart of sw-engine and sw-cp-server should do the trick.

systemctl restart sw-engine
systemctl restart sw-cp-server

It’s best to restart php-fpm and nginx as well at this point. But might not be needed.