• Resolved Nick

    (@nickbrowne)


    Hello, I have just installed the ‘Freshmail for WordPress’ plugin on a localhost site following the creation of a new Freshmail account. Version 1.5.4.

    When trying to Connect using the supplied API and API Secret key I receive a message saying ‘ Invalid json response!’.

    I have re-tried generating the API Secret key but this has made no difference.

    Could you please let me know what causes this and how it can be fixed.

    Many thanks.

    https://www.ads-software.com/plugins/freshmail-newsletter/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author FreshMail.com

    (@freshmailcom)

    The most common reason for such a problem is a blocked port 443, which is done by the server administrator. If the port is in fact open, please write to the creators of the plugin at https://www.borbis.pl or, if that fails, to us.

    Thread Starter Nick

    (@nickbrowne)

    This has now been fixed by version 1.5.5 of the plugin. It would appear that the plugin cannot be used from a local host site using a ‘self signed’ certificate.

    Problem is further resolved by setting up a test website on our hosting platform which has a valid certificate associated with it.

    Likewise, a separate Freshmail account has been created for testing with to avoid cross over with the production set up.

    Plugin Author FreshMail.com

    (@freshmailcom)

    Hello,
    I think that it is probably issue of the lack of the update. If are these are problems with certificates one should bring it up to date openssl’a, curl’a and everything else what is by you used for connections

    Thread Starter Nick

    (@nickbrowne)

    Agreed. The upgrade only became available after the problem was reported.

    As such, the upgrade did not fix my original requirement (to use the plugin on a localhost site), it just gave a better error message and confirmed that testing can only be carried out on an externally hosted site.

    Earlier points about opening port 443, updating OpenSSL etc. on the host are no doubt also valid checks to make if ‘Connect’ problems occur.

    Anyway, grateful that a way forward was found. Thanks.

    Plugin Author FreshMail.com

    (@freshmailcom)

    Glad to help – let us know if we can do anything else for you.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Invalid JSON response ! from Connect API Keys’ is closed to new replies.