p12 migration - Import p12
Now that we have secured our p12 on the new VPS, our installation will continue.
When asked if we are migrating over an existing p12 private key, we will enter y.
nodectl will warn you that we need to upload your existing p12 file; however, we should have already done this via the instructions from how to upload your p12 section of this documentation.
Have not uploaded p12
If you have not uploaded your p12 key store file, enter y here 👇 to exit the installation.
Upload your existing p12 to your VPS and repeat the previous steps to return to this point in the documentation.
Have uploaded p12
Otherwise if we have already uploaded our p12 key store file, we can hit the n key.
If this Node will be using an existing p12 private key, the installation should be exited and the existing p12 private key uploaded to a known secure local directory on this server. Alternatively, you can simply pause here and upload the p12 private key file, and then continue.
Please see the Constellation Doc Hub Validator section for instructions on how to do this.
Later in the installation, the Node Operator will be given the opportunity to migrate over the existing p12 private key. At the necessary time, a request for the p12 name and directory location will be given. Once nodectl understands where the p12 file is located and necessary credentials, it will then be migrated by the installation to the proper location.
Exit now to upload existing p12? [n]: n
The next step is to return to the new installation instructions. Continue to follow the instructions, step by step, until you reach the next blue box to return here.