You are not reading the latest stable version of this documentation. If you want up-to-date information, please have a look at master.
This guide will cover how to upgrade from EmbassyOS version 0.2.x to version 0.3.0 with your own equipment.
Once you have all these you will need to download an 0.3.0 image from https://images.start9.com. This is free for all existing users. Anyone who is running 0.2.x who compiled it themselves will need to either compile 0.3.0 themselves or download an 0.3.0 image.
Once you have the image, flash it on to the 32GB SD card - the new one, NOT the one currently in your Embassy!
The flashing software we recommend is Balena Etcher
Begin by going into your Embassy, stopping all running services, and shutting down the device in the Embassy tab.
Once you’ve heard the power-off sound, wait a few more seconds and then safely unplug the Embassy.
Next, remove the SD card that is in your Embassy and place it into the SD card adaptor, and then connect the adaptor to a USB port on your Embassy.
Then take the new SD card with 0.3.0 on it and place it into the microSD card slot on your Embassy (not into the adaptor - that is for the old SD card!)
Next, plug the SSD into one of the USB 3.0 (blue) ports on your Embassy, then reconnect the Ethernet cable if not already connected.
Now the power cable can be connected and the Embassy powered up.
Embassy will power up and then initialize, a process of less than 5 minutes if you downloaded the image, or about 10-20 minutes if you built from source. Once complete you will hear a _bep_ to indicate it is initialized and then a _chime_ sound to indicate it is online.
On your computer, open up a browser and go to http://embassy.local
You will be asked to enter your product key. This can be located on the bottom of your Embassy if you purchased, or in the repository folder if you built from source.
Once entered, select “Recover” then select the microSD card - this will be labelled
On the next page you will be asked to select a storage device - here you should select your SSD.
If it does not show up, please power down Embassy, unplug it, plug it back in, and boot Embassy again
If this drive is not empty, you will see a warning first, indicating all data will be overwritten. If you are happy to proceed, click “Continue”.
You will now need to make a password for your Embassy. It needs to be a strong password. This password protects your Embassy. It can be the same one that you used prior to migration, or a new one. Either way, make it strong, and make a backup of it.
Embassy will now recover all your data from your old Embassy and once finished, you will hear a _bep_, followed by a _chime_.
Now you will be provided with both a Tor and LAN address with which you can access your Embassy. A file offered for download will contain this important information, which you should keep somewhere safe. It is also a good idea to make bookmarks on the devices that you will use to access your Embassy.
To use LAN safely, the SSL certificate will need to be added to whatever device you are using to access. This can be downloaded by clicking on “Download root CA” and installed by following the instructions.
You can now log in to your Embassy via Tor or LAN, and you will be given the option of recovering your data on a service-by-service basis.
You may remove your 0.2.x SD Card once you reach the success page. It is highly recommended to keep this card in a safe place for a few weeks to ensure your migrated Embassy is working smoothly. After this you may wipe and repurpose the card however you wish.
Do NOT use the old 0.2.x card again, unless instructed by a Start9 Support Tech, especially if you have funds on the Lightning Network, as it can lead to loss of funds!
Please note that some services, such as LND, will have new Tor interfaces, and so you will need to add your new credentials to your integrations, such as Zap and Zeus wallets.
For those recovering Bitwarden - it is now called Vaultwarden.
For those recovering Bitcoin and changing to a full archival node: You will need to “Disable Pruning” in the config, and run the “Reindex Blockchain” Action, then restart the service upon completion of the sync.