You are not reading the latest stable version of this documentation. If you want up-to-date information, please have a look at master.

Common Issues

Sometimes things don’t go as planned. Check here for solutions to common problems with your Embassy.

Embassy will not boot

If the device will not power on at all (no lights whatsoever), then the only issues could be that the Pi is not getting the power it needs, or it is completely dead (extremely rare). If you sourced your own parts, please ensure that the power supply meets the minimum required specifications in the DIY Guide. If you received your device from us and it will not power up at all, please Contact us for assistance.

Embassy boots into “Diagnostic Mode”

Diagnostic Mode is a new UI that will launch in the event that no drive, or an incorrect drive (such as one from another Embassy) has been plugged into Embassy. Simply plug your external drive in and reboot (power off and on again).

During initial setup, I am unable to connect to “embassy.local”.

  • Confirm that your Embassy is plugged into both power and Ethernet.

  • Confirm the Embassy emitted two sounds when powering on: a bep and a chime.

  • Confirm your phone is not connected to a “Guest” network

  • Confirm your phone is not using a VPN.

If you still cannot connect, try logging into your router (the directions for which can be found with a simple web search for your router model and ‘how to log in’). Once you are in your router, find the device labeled ‘Embassy,’ and visit it’s associated IP address, which will look something like:

I am unable to reach Embassy via it’s embassy-xxxxxxxx.local (LAN) address

Make sure you have successfully followed the LAN Setup instructions for your device. If you still cannot connect, try all the solutions listed under initial setup.

I am unable to reach Embassy via it’s xxxxxxxxxxxxxxxxxx.onion (Tor) address

  1. Test - Try connecting to your Embassy using the preferred Tor Browser.

    1. If Tor Browser works - It means the issue is either with the Tor daemon on your device or with the browser settings.

      1. Solutions
        1. If you are not yet running a Tor daemon on your device, follow these instructions. If you are already running a Tor daemon, restart it, or in the case of Android, restart your phone.

        2. If you are using Firefox, ensure it has been properly configured to work with .onion URLs.

    2. If Tor Browser does not work - It means there is an issue with your Embassy or with the Tor network.

      1. Test - Try visiting your Embassy over LAN from a non-Tor browser such as Firefox, Chrome, or Safari.

        1. If LAN works - it means the issue is an issue your Embassy’s Tor connection.

          1. Solutions
            1. Check if there are any ongoing network-wide service issues with Tor at the Tor Project status page

            2. Wait an hour or so to allow Tor on your Embassy to fix itself.

            3. Restart your Embassy through the UI (Embassy -> Restart).

        2. If LAN does not work - It means your Embassy is experiencing general networking issues.

          1. Solutions - Power cycle your Embassy by unplugging it and plugging it back in, then wait a few minutes before trying to connect again.

I’m having an issue with a particular Service

If a Service is crashing or acting up in some way, check the Documentation and FAQ for that particular Service. You can also check the “Logs” (on the service page), which might tell you what the problem is. If that is not helpful, try to restart the service to see if that clears up the issue. If you are still having issues, please reach out in one of our Community Channels for immediate assistance, or email for help during business hours.