close

April 2024 only! Join our Discord free of charge.

Slick­Stack
Lightning-fast WordPress on Nginx

Smash Balloon Instagram feed “Error 999: Access token could not be decrypted.”

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #3739 Reply
    Teresa
    Guest

    Why is this happening after running the ss-install script to reinstall SlickStack

    https://smashballoon.com/doc/instagram-api-error-message-reference/?instagram#999

    #3740 Reply
    Dylan
    Guest

    I think it’s because their plugin relies on the salt hashes in wp-config.php

    Error 999: Access token could not be decrypted.
    The issue is being caused by the encryption that Instagram/Facebook requires in regards to access tokens. This encryption relies on the Salt hashes in the wp-config.php file. To add these hashes to your config file, follow the step below.

    source:
    https://smashballoon.com/doc/error-999-access-token-could-not-be-decrypted/?instagram

    does SlickStack change the salts?

    #3744 Reply
    Zachary
    Guest

    does SlickStack change the salts?

    Yes SlickStack will regenerate all the salts anytime you reinstall, or anytime you reinstall the WordPress config only e.g.

    ss install wordpress config

    or

    sudo bash /var/www/ss-install-wordpress-config

    This is on purpose, so that teams can reset their salts anytime they need for stronger security, it also force logs-out all users from WordPress too.

    #3745 Reply
    Susan
    Guest

    TLDR

    Smash Balloon should not be relying on WP salts for their encryption…

    I remember Easy Digital Downloads used to have the same problem, but eventually they found a better solution that didn’t rely on salts.

    #4049 Reply
    Willie
    Guest

    thanks for this!

Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: Smash Balloon Instagram feed “Error 999: Access token could not be decrypted.”

Thanks to our generous sponsors for their support!