You are not reading the latest stable version of this documentation. If you want up-to-date information, please have a look at master.
I’m trying to migrate my old Embassy data, but the device won’t boot. What do I do?
I cannot reach embassy.local after hearing the start-up sounds from Embassy. What do I do?
Do I need to take any additional security precautions with my device, for example with my router/modem?
What if I have an unique network issue, for example, with a firewall?
Can I use my Embassy from behind a VPN, for example, if my router has a built-in VPN?
Is it true that my device has some limited functionality in regard to Embassy?
Please check out the Initial Setup page, and follow the instructions.
After plugging into power and your router, you will hear 2 distinct sounds: first, a “bep” ‐ indicating the device is powering on, and second, a “chime” ‐ indicating the device is ready for setup. You can hear these sounds on the Initial Setup page.
Yes, the Embassy’s case is actually doing ‘double duty’ as a heat sync. This means that the metal of the case is actually touching the chips on the circuit board and drawing their heat out and away. This is known as “passive cooling,” as no fan (and therefore no noise) is required to cool the system.
Remove the external drive and sd card adapter if they are plugged in. Boot the device with just the new (32GB) sd card inserted. After you hear the start-up sounds, you may plug in the external drive and old (128GB) sd card.
Ensure that you are on the same network as your Embassy. Check that it is not a “Guest” network in your router
Your browser might try to force https://embassy.local, delete the https:// prefix and try again with just embassy.local or http://embassy.local
Try a different browser, and note that Tor Browser cannot handle .local addresses
Turn off your VPN if you are using one (you may turn it back on after setup)
If none of the above work, check your network setup, including your router settings if they are non-standard
A major use-case of Bonjour is wireless printing over the LAN, but your Windows machine can also use Bonjour to discover and connect with other devices on the Local Network. In this case your Embassy. If Windows were to add support for reaching
.local addresses, as is done in Linux and Mac, this would no longer be necessary.
Recent updates to Windows 10 (and possibly 11) may obviate the need for Bonjour, but so far results are mixed.
This is most likely a transient networking issue that will correct itself in a few minutes to an hour. If it does not, there are few things you can try:
On Android/Orbot, the most common solution is to restart your Android device.
Access your Embassy over LAN, and restart it from the “Embassy” menu. (Restart by removing power if you cannot access via LAN)
Restart your router.
Nothing special is required, however, it is best practice to use good passwords, i.e. for your WiFi and your Embassy. Here’s a comic explaining how to make strong passwords, simply.
Embassy is designed to work as simply as possible, for as many as possible, while providing the ability to self-host in a private manner. If you have an agressive or custom firewall, or other custom network settings, there is a good chance that addtional configuration may be necessary. We will continue to learn about custom networking issues, update our docs with resources, and help in the Community Channels to the best of our ability.
While this is possible, it adds complexity, which may lead to problems. You will need to understand the setup of your router/VPN and how it supports (or doesn’t support) Tor/LAN connections.
If you are having trouble with this, you might consider letting Embassy out “in the clear,” since all services are accessible over the Tor network, offering a high level of privacy.
The short answer is maybe, but there are workarounds for most limitations. Please see the Limitations page for details on your device.