Updating Plugin From 2.9.10 Creates API Error 999

Hey @adaptablewebsites,

Thank you for reaching out to us for assistance. I can see how this issue could pop up here. The 999 error is related to an encrypted Access Token (account connection) that is required by Instagram. We encrypt this and save it in your database. Should the salts & keys for your site change (located in wp-config.php), the plugin can no longer decrypt the token for API calls.

The first thing to test here is to update the plugin and under Instagram Feed > Settings > Sources reconnect the source with the issue. This will re-add the account with ‘fresh’ encryption. If you have further issues let me know, as you may need to add a specific salt & key for our plugin to use in your wp-config.php file.

Best regards.

Hi,
Followed the instruction.
Reconnect pops up a “Redirecting to connect.smashballon.com”
This just hangs in perpetuity and does not reconnect … or even stop trying for that fact! One has to reload the page. So, that intiative fails and doesn’t end cleanly.
Interestingly, there is a snippet of text next to “source invalid” that states Used in 2 feeds. Why two feeds? I never created two feeds … I created one feed … that is used once on one page. On further inspection I see the following shortcodes for the two feeds …
[instagram-feed feed=1]
[instagram-feed feed=2]
These shortcodes are not used in the page …. This is:
[instagram-feed]
This doesn’t look right. It’s confounded by an interface change so it is difficult to compare a “before” and “after”. It’s now cost me around an hour of time so I don’t have the inclination to troubleshoot … I mean it takes 10mins to write this support advisory.
Quick, “Let’s restore yesterday’s backup” I scream. Another few mins … Aah … there you go … back and working beautifully on version 2.9.10
Hope this helps … does the feed thing look a bit weird?
Many Thanks
Mark

Hey @adaptablewebsites,

There may be other issues related such as if you have a security type plugin (such as Wordfence) that may be blocking the redirects/requests. The error (999) is related to encryption as mentioned and this actually exists already in version 2.9.10, so you should be able to get this working again on the latest version.

If you do want further assistance from us you can reach out to us using our support form found here, sending the System Info from the plugin’s ‘Help’ menu found in the top right of the settings page. If you also send there temporary access to the WordPress Dashboard as well as an Access Token (generated with our tool) we would be happy to help get you fully set up.

Best regards.

Hi,
Thanks for coming back to me.
Please consider …
I have your free plugin on 6 sites
They all have identical configs.
I have the same WordPress version, same version of Divi, same plugins … and only a few plugins to keep probs to a minimum.
One security plugin SG Security as am using Siteground.
3 sites are fine with updates and are working nicely on latest Smash Balloon
3 sites show API 999 error
So, there is an inconsistency … I would have expected to see it with all six … strange.
Tried disabling SG Security plugin .. and updating plugin and recoonecting feed … still hangs … so diagnostically it is not the Security plugin.
I don’t have the time at the moment so I will have to leave the 3 sites on 2.9.10 for now as they work.
Thanks for your help.
Anyone else have the same problem? Are you aware of this issue with anyone else
Thanks Mark

Hey @adaptablewebsites,

Thanks for chiming in here. It may be that the sites do not update salts and keys in your wp-config.php at the same time. Please see our guide on setting your own keys and salts manually, this should help no matter which security plugin is used or host. After these changes however you will need to reconnect one more time. If issues persist, let me know!

Link to Error 999 Guide

Best regards.