Signature Field Widget

Dear customer, we checked your message carefully.

Reading it makes me quite uncomfortable as we can't see any attachement/image provided in your message.

Also the link https://store.suitecrm.com/api/v1/key/validate?public_key=xxxxxxxxxxxxxxxxxxxxxx&key=my_license_key is coming from which admin page ?

To enable your key, please go to the admin panel first as staged in our install documentation : https://store.suitecrm.com/docs/signature-field-widget/installation-guide

Your key is still indicated as valid by SuiteCRM store. To me it sounds that you try to manually validate the plugin using a link that might has been provided by another plugin reseller ? But you can't enter this URL in your browser and except it to work as the answer from SuiteCRM servers will not be stored then in your CRM database (this kind of URL must be called by SuiteCRM server directly not by the admin user)

This is a technical tasks and problem. I think you should ask your suiteCRM administrator some help to double check the actual configuration (config table in MYSQL that contains also the current state of the plugin validation)

If you need some assistance from our side, please provide us a way to connect to your CRM instance (administrator) + way to connect to Mysql database.

You can reach us using : info.idevit@gmail.com

Thank you

Now the Signature addons is correctly validated. There was a misconfigured DNS in the server hosting the SuiteCRM appliance. Thank you for all your support.

This code maybe usefull for others in trouble

curl -i -H "Accept: application/json" "https://store.suitecrm.com/api/v1/key/validate?public_key=yourpublickey&key=yourkey"

HTTP/1.1 200 OK
Date: Tue, 19 Nov 2019 08:14:08 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Powered-By: PHP/5.5.9-1ubuntu4.9
Content-Length: 18
Content-Type: application/json
{"validated":true}

Thanks for your help and posting the missing CURL sample. This is extreme case when the customer DNS is not efficiently answering the DNS resolution calls to licence servers !

Main point is that the module is now working as expected ! I am closing the case. $If you need any other assistance, don't hesitate to reach us.

May I also ask you to give us a little review of the module to help other users see how it is working with your specific version ?