Date: Fri, 29 Mar 2024 03:33:37 -0400 (EDT) Message-ID: <312165763.5069.1711697617974@docs.blesta.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5068_90842658.1711697617973" ------=_Part_5068_90842658.1711697617973 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
If you attempt to view data and it appears corrupt or simply won= 't decrypt, it's most likely that you've changed your Blesta.system= _key, stored in your blesta.php config file.= This can happen for the following reasons:
Any data encrypted since the Blesta.system_key value wa= s changed will become corrupt once you restore or replace the key. So you m= ay want to weigh the benefit of restoring or replacing the key before proce= eding.
Restore a backup of your blesta.php config file.
If you can't restore a backup, you will need to reconfigure Blesta. Saving settings with the pro= per information will save them using the Blesta.system_key= set in your blesta.php config file. You'll also need to reset the key pair for ea= ch of your companies.
Restore the previous Blesta.system_key value.
If you can't restore the Blesta.system_key value, see I deleted my blesta= .php config file.
See I deleted my blesta.php config file.