Hey @osat99,
Thank you for reaching out to us for assistance. For us to be able to look into this properly, please send us a support request via our website, here. When doing so, please add the System Info found in the plugin’s Support tab. A support representative will then be able to get back to you about this as soon as possible.
Best regards.
Hello. I’m seeing the same issue.
Is it rectified in an update or could you share what the issue was?
Thanks in advance.
Hey @cwarrent,
Thank you for reaching out to us for assistance. We believe the issue is being caused by the encryption that is required by Instagram/Facebook in regards to access tokens. This encryption relies on the Salt hashes in the wp-config.php file. Can you add and define the following to the wp-config.php file for the site:
SBI_ENCRYPTION_KEY
SBI_ENCRYPTION_SALT
You would use the same format as the logged_in_salt and logged_in_key in that file (giving each their unique specific key). The important part is to make sure the values for the two SBI items above matches on both the local and production site if you use separate ones. Once they are set, do not change them. You will need to reconnect the Instagram account(s) to the plugin after this change but moving forward this should hopefully resolve the issue you are having.
Let me know if you run into any issues or have any additional questions. Hope you are having a great day!
Thanks for the update.
I don’t (currently) see it happening on all the sites where I run your plugin is there a reason for that. Maybe out of date versions of your plugin which I haven’t updated yet, won’t have this issue?
I’ll have a look at the WP Config site, I assume if I check over the default settings I can use that to then set the two values above?
Thanks in advance for your help.
Hey @cwarrent,
Yes, we recently implemented additional encryption and salting for the stored information in our plugin. This was just in a later version so older versions would not see this issue. This is required by Facebook/Instagram and we recommend updating all sites – at least after resolving it on one.
In some cases, it is due to having a Staging setup being pushed to a Live site. In that case, the keys and salts are usually mismatched and so the live site will not be able to decrypt the information correctly when making API calls. To fix this, you can manually set the above values to be the same on Staging and Live. In some cases, even if it is a single website, this will need to be set either way depending on the WordPress setup. In either case, you will need to reconnect the account in the plugin’s backend to refresh the connected account information so that it is properly encrypted in a way that can be used.
I am not sure what you mean by using the default setting, but we suggest generating a new key/salt pair to use specifically for the SBI values. As an example, values can be generated here (in this case, you can copy any of the keys to instead use with the SBI key/salt pair).
Best regards.
Sorry, I guess I was confused by the methods to update the WP Config file.
IF I update the plugins and re-authentication the Instagram accounts will this bypass the need to update the WP Config file?
Again thanks! 🙂
