-
Notifications
You must be signed in to change notification settings - Fork 14
Troubleshooting
If you experience an issue running the plugin refer to this document to see if your issue is addressed. Please first open the developer console and note any errors in red. View instructions to open the console for various browsers.
As the data is sent to FS in the form of JavaScript it is helpful to inspect the payload sent. Normally this data is encrypted but by setting SCRIPT_DEBUG to true the payload will be sent unencrypted and debug information will be dumped to console. The payload itself can be inspected by looking for this line in the console: [FastSpring API] Input. One of these lines, when expanded, will have the secure object which is the payload sent to FS.
If the popup appears to open and close immediately it's often due to a payload-invalid error. You can open your developer console and look for errors. You may see something like this in red:
[FastSpring API] (!) Error: Error received: – 400 – "payload-invalid"
This is usually an indication that your settings in the plugin setup are incorrect. Specifically double check the following fields:
- Private Key
- Storefront
- Access Key
If any of these are invalid it will yield such an error. Ensure your storefront does not have a protocol (http://) or ending slashes/spaces.
This error stems from an invalid storefront path. Ensure this path is correct.
IF orders are not marked completed - possibly also issues with bad receipt URLs, then it's possible there is a webhook issue. Inspect the plugin status log to see if the webhook is called but may be failing. Sometimes FastSpring encounters issue creating a secure connection for webhooks and no information is logged on the WP side. If this occurs try changing your webhook URL from https to http. Additional information can also be obtained from the FS webhook activity logs found under the FS dashboard in Integrations > Webhooks > Recent Activity.
After making changes you can have FS retry by navigating the the Activity page of the FS dashboard, locating the desired oder then, under the Options menu on top right - resend webhook notifications.
If you are using an https secure webhook and encounter issues inspect your FS logs and look for "handshake_failure". This can occur when FS is unable to create a secure connection due to incompatibility with the SSL certificate in use. If you are using Let's Encrypt SSL this is a known issue. You will need to use a paid SSL certificate or use a non SSL webhook. You can confirm this by comparing the supported ciphers from FastSpring against the output of nmap --script ssl-enum-ciphers -p 443 YOURDOMAINHERE.COM