Error 2001

Hi @hubmacfan,

The button you’re looking for is the “Disconnect” button under “Account and Actions”.
No extension data will be lost in this process, all you need to do is hit the “Go Free” button afterward and reactivate the extensions you’d like to use.

I changed the wording of the action buttons in 1.4, but I see I didn’t make that notice comply. I’ll update this is 1.5.1.

Cheers!

Background info:
This notice can pop up when your site’s security keys have changed, or when you’ve moved domains. It prevents third-party plugins hijacking the activation process, and it prevents sharing of unique connection keys which could otherwise lead to complications like data-leakage.

• This reply was modified 6 years, 10 months ago by Sybre Waaijer. Reason: Clarity

I’ve just released 1.5.1, so the wording should be a little better.
Plus, the interface now responds to this error, too. Making it a lot easier to comprehend.

As always, thanks for your input ??

Got the same error. I also have a free account only.
Disconnected, even if I wasn’t connected before. No changes. Extension keep deactivated and the error comes back every time I call the page.

Might be a problem with the salt shaker plugin ?? It changes the security codes on a regular basis.

Hi @ralfm,

The verbatim of “Disconnection” is a bit ambiguous, and it’s an umbrella term for achieving one thing. It is deleting the settings, and possibly automatically removing the site and all privacy-related data from your API account.
I’ll otherwise have to maintain two errors, four buttons, multiple POST/GET requests, etc.

What you’re experiencing is definitely an incompatibility with the Salt Shaker plugin. We require something unique that’s promised to be static (unless it’s found to be compromised and must change, which is a corner case), as stated above:

It prevents third-party plugins [from] hijacking the activation process, and it prevents sharing of unique connection keys which could otherwise lead to complications like data-leakage [and API abuse].

Thank you @cybr for confirming this fact. I will then only change the salt manually and immediately establish a new connection to the API. Maybe you will find a solution in a future version.
Thank you very much for this plugin! It is always a good thing to have a certain choice when it comes to a certain functionality.