I read something about running this command to generate the key and yet it says its set but where, its not in .env and the website still doesn’t come up.
[librenms@servername ~]$ php artisan key:generate
Application key set successfully.
I’m sure its probably something stupid but would really love to get my LibreNMS back up and running.
To get the APP_KEY back what I did was edit .env and add the first line as APP_KEY= and save .env then I ran
[librenms@servername ~]$ php artisan key:generate
Application key set successfully.
[OK] Composer Version: 2.1.12
[OK] Dependencies up-to-date.
[FAIL] APP_KEY does not match key used to encrypt data. APP_KEY must be the same on all nodes.
[FIX]:
If you rotated APP_KEY, run lnms key:rotate to resolve.
[OK] Database connection successful
[OK] Database schema correct
[FAIL] fping location is incorrect or bin not installed.
[FIX]:
Install fping or manually set the path to fping by placing the following in config.php: $config[‘fping’] = ‘/path/to/fping’;
[WARN] Unable to locate git. This should probably be installed.
So now I’m stuck.. any ideas? Does this help at all?
[OK] Composer Version: 2.1.12
[OK] Dependencies up-to-date.
[FAIL] APP_KEY does not match key used to encrypt data. APP_KEY must be the same on all nodes.
[FIX]:
If you rotated APP_KEY, run lnms key:rotate to resolve.
[OK] Database connection successful
[OK] Database schema correct
[FAIL] fping location is incorrect or bin not installed.
[FIX]:
Install fping or manually set the path to fping by placing the following in config.php: $config[‘fping’] = ‘/path/to/fping’;
[librenms@servername ~]$ ./lnms key:rotate
Either old key or --generate-new-key is required.
[librenms@servername ~]$ ./lnms key:rotate --generate-new-key
Config was cached, cleared cache to make sure APP_KEY is correct. Please re-run lnms key:rotate
[librenms@servername ~]$ ./lnms key:rotate
Either old key or --generate-new-key is required.
So not any closer and just not sure what else I can do on my side. I really need some input from someone who may have run across this before. Anyone? Bueller? 
[OK] Composer Version: 2.1.12
[OK] Dependencies up-to-date.
[FAIL] APP_KEY does not match key used to encrypt data. APP_KEY must be the same on all nodes.
[FIX]:
If you rotated APP_KEY, run lnms key:rotate to resolve.
[OK] Database connection successful
[OK] Database schema correct
Following suggestion…
[librenms@servername ~]$ lnms key:rotate
Either old key or --generate-new-key is required.
[librenms@servername~]$ ./lnms key:generate
Application In Production! *
[OK] Composer Version: 2.1.12
[OK] Dependencies up-to-date.
[FAIL] APP_KEY does not match key used to encrypt data. APP_KEY must be the same on all nodes.
[FIX]:
If you rotated APP_KEY, run lnms key:rotate to resolve.
[OK] Database connection successful
[OK] Database schema correct
Still broke so try another way since the old key is just gone (no idea)
try another approach
[librenms@servername ~]$ ./lnms key:rotate --generate-new-key
Old key: base64:9RXZ2YhNFn6WjTqiifVG9Fv70EQviI3tQRQlOsVXIKw=
New key: base64:xCnwtPd31kaS7vlkzMvcfmxADc3CAmNY/I6ktiKbAtI=
Document BOTH keys! In case something goes wrong set the new key in .env and use the old key as an argument to this command
This command could cause irreversible loss of data and will invalidate all browser sessions. Make sure you have backups.
I have backups and want to continue (yes/no) [no]:
Failed to decrypt validation.encryption.test, skipping
Old key: base64:9RXZ2YhNFn6WjTqiifVG9Fv70EQviI3tQRQlOsVXIKw=
New key: base64:xCnwtPd31kaS7vlkzMvcfmxADc3CAmNY/I6ktiKbAtI=
Failed to decrypt item(s). Set new key as APP_KEY and run this again with the old key as an argument.
NOTE: I know not to share key but this is just temp plus I’m restoring from an old backup since I just can’t seem to figure it out… everyone that has a working LibreNMS should copy that APP_KEY from .env and save it in a safe place because without it you can not decrypt the data.
