At least this will help you start the process again from a known position. Make sure to back up everything before you start this process. Otherwise, please get in contact with our support team so we can be available to help get you up and going. If you are confident with Octopus you can follow these steps to get back up and going. Sensitive values in your deployment targets, like the password for creating Offline Drops.Sensitive values in your deployment processes, like the password for a custom IIS App Pool user account.Sensitive variable values, wherever you have defined them.The Octopus Server X.509 certificate which is used for Octopus to Tentacle communication - this means your Tentacles won't trust your Octopus Server any more.Octopus encrypts important and sensitive data using a Master Key. The Master Key can only be decrypted by the machine where the config file came from. Simply having a copy of the config file is not enough. The Master Key is stored in the Octopus Server configuration file and encrypted using the machine's encryption key. The only way to recover the Master Key is to get the dead machine up and running again. The fastest and easiest way to get up and running is to recover the Master Key. If you are reading this page: please back up your Master Key Recover the Master Key The machine hosting Octopus Server dies irrecoverably, and you've discovered you don't have your Master Key! Whilst you cannot recover the data encrypted with your missing Master Key, this guide will help you get back up and running again. Sometimes the worst possible thing happens.
0 Comments
Leave a Reply. |