Domino

Hello,

similar issue here, we have run some tests and the following procedure seems to work, but without official guidance, it should be used with caution.

First we remove the associated API Key in Network Brute Force (if present)
Features -> Firewall -> Network Brute Force -> API Key -> Reset API Key

Next go to the DB, table wp_options.
Navigate to “itsec-storage” option_name and backup it’s content (or save the entire row).
Edit the option_value as shown in the example, paying attention to the serialized data.
We blank url and key.

Before:
a:0:{}s:16:"registered_sites";a:1:{i:1;a:2:{s:3:"url";s:23:"https://www.example.com";s:3:"key";s:205:"v2.local.31babf9815b1413739a7cdf2ca43f8875d8c7fc92ad03f7a24f8fff2953037b1-690ed4cb9540c503eb381d2478f8d5c4d3752d84fa537f01324e44c341824250-350ae7dbaf1617ed1127bb9bfb77e6cad8d36ca77b7646067973e55609864646-j";}}}

After:
a:0:{}s:16:"registered_sites";a:1:{i:1;a:2:{s:3:"url";s:0:"";s:3:"key";s:0:"";}}}

Then go to “Site Scans” and start a new scan.

Verify in the DB that the url and key has been updated.

Request a new API Key if needed.

With this procedure, at the moment subsequent scans will no longer show the old URL.

• This reply was modified 1 day, 1 hour ago by Domino. Reason: letter
• This reply was modified 1 day, 1 hour ago by Domino. Reason: syntax