After the laravel project is deployed to the server and the database is imported successfully
Background login error:
The reason is laravel’s app_Key and encrypt() functions( Encrypt() is a helper function of laravel, which is equivalent to the short form of crypt:: encrypt()
Once used php artisan key:generate App regenerated_Key, the MAC is invalid exception will be reported when decrypting the desrypt() function, which is due to app_The change of key leads to the change of MAC information, and the decrypt() decryption reports an exception
Solution:
Method 1. Re encrypt with encrypt() and log in again in the background. OK
Method 2. Encrypt () encryption is not conducive to project migration and deployment. Adopt the suggestions of this blog post and temporarily use hash encryption
Similar Posts:
- [Solved] Error-Javascript: Uncaught Error: Malformed UTF-8 data at Object.stringify (crypto-js.js:478) at W…
- mcrypt_ module_ The successful solution of open abandoned by php7.1
- [Solved] exception is java.lang.NoClassDefFoundError: com.sun.crypto.provider.SunJCE
- When using jasypt encryption configuration, an error is reported: decryptionexception: unable to decrypt
- Kingbasees supports column encryption
- Caused by: java.lang.SecurityException: Jurisdiction policy files are not signed by trusted sign…
- Solutions to typeerror: expected string or bytes like object error
- [Solved] MYSQL ERROR 2059 (HY000): Authentication plugin ‘caching_sha2_password’ cannot be loaded: /usr/lib64/mysql/plugin/caching_sha2_password.so: cannot open shared object file: No such file or directory
- PHP: How to Solve Laravel rules preg_match(): No ending delimiter ‘/’ found
- EntityFramework Enable-Migrations report exceptions “No context type was found in the assembly”