mirror of
https://github.com/Start9Labs/documentation.git
synced 2026-03-26 02:11:55 +00:00
change embassyOS to StartOS & nuance (#357)
* change embassyOS to StartOS & nuance * Update conf.py * Update manifest.rst * say start9 instead of embassy in two links * progress * scrubbed faqs - basic-use, lightning, service-packaging, services, startos * add a few fixes * more * more 'embassy' cleanup * more * the last of embassy (aside from sdk and cli commands, links, etc) * some fixes * update icon, logo, and theme * Update site/source/user-manual/upgrade-hardware/upgrade-pro.rst * Update site/source/developer-docs/packaging.rst * Update site/source/developer-docs/specification/config-spec.rst * Update site/source/learn/concepts/networks.rst * Update site/source/learn/concepts/networks.rst * Update site/source/user-manual/customize.rst * Update site/source/support/faq/faq-basic-use.rst * Update site/source/user-manual/upgrade-hardware/naspi-upgrade.rst * Update site/source/user-manual/upgrade-hardware/upgrade-pro.rst * Update site/source/support/faq/faq-bitcoin.rst * Update site/source/support/faq/faq-bitcoin.rst * Update site/source/support/faq/faq-general.rst * Update site/source/support/faq/faq-general.rst * Update site/source/support/faq/faq-general.rst * Update site/source/support/faq/faq-general.rst * Update site/source/support/faq/faq-services.rst * Update site/source/support/faq/faq-general.rst * Update site/source/support/faq/faq-startos.rst * Update site/source/support/faq/faq-troubleshooting.rst * Update site/source/support/faq/faq-startos.rst * Minor fixes * Fix build errors, ready to roll * Add Beethoven * More fixes * More nother fix * More nother fixes agin * Remove sentence * cards instead --------- Co-authored-by: Matt Hill <matthewonthemoon@gmail.com> Co-authored-by: Shadowy Super Coder <musashidisciple@proton.me> Co-authored-by: Lucy Cifferello <12953208+elvece@users.noreply.github.com> Co-authored-by: kn0wmad <39687477+kn0wmad@users.noreply.github.com> Co-authored-by: agent <kn0wmad@protonmail.com>
This commit is contained in:
BitcoinMechanic
@@ -8,42 +8,42 @@ Common Issues
|
||||
:depth: 2
|
||||
:local:
|
||||
|
||||
Sometimes things don't go as planned. Check here for solutions to common problems with your Embassy.
|
||||
Sometimes things don't go as planned. Check here for solutions to common problems with StartOS.
|
||||
|
||||
Embassy will not boot
|
||||
StartOS 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 :ref:`DIY Guide<diy>`. If you received your device from us and it will not power up at all, please :ref:`Contact us<contact>` for assistance.
|
||||
|
||||
Embassy boots into "Diagnostic Mode"
|
||||
StartOS 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).
|
||||
Diagnostic Mode is a new UI that will launch in the event that no drive, or an incorrect drive (such as one from another StartOS server) has been plugged into your server. Simply plug your external drive in and reboot (power off and on again).
|
||||
|
||||
.. _setup-troubleshoot:
|
||||
|
||||
During initial setup, I am unable to connect to "embassy.local".
|
||||
During initial setup, I am unable to connect to "start.local".
|
||||
----------------------------------------------------------------
|
||||
|
||||
* Confirm that your Embassy is plugged into both power and Ethernet.
|
||||
* Confirm that the server is plugged into both power and Ethernet.
|
||||
|
||||
* Confirm the Embassy emitted two :ref:`sounds<sounds>` when powering on: a bep and a chime.
|
||||
* Confirm the the server emitted two :ref:`sounds<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: ``192.168.1.9``
|
||||
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 ``start``, and visit it's associated IP address, which will look something like: ``192.168.1.9``
|
||||
|
||||
I am unable to reach Embassy via it's embassy-xxxxxxxx.local (LAN) address
|
||||
I am unable to reach my server via its *<custom-address>.local* (LAN) address
|
||||
------------------------------------------------------------------------------
|
||||
|
||||
Make sure you have successfully followed the :ref:`LAN Setup<connecting-lan>` instructions for your device. If you are using Windows, your problem is almost certainly with Bonjour - follow the directions to reinstall, even if you have already done so. If you still cannot connect, try all the solutions listed under :ref:`initial setup <setup-troubleshoot>`.
|
||||
|
||||
I am unable to reach Embassy via it's xxxxxxxxxxxxxxxxxx.onion (Tor) address
|
||||
I am unable to reach my server via its xxxxxxxxxxxxxxxxxx.onion (Tor) address
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
#. **Test** - Try connecting to your Embassy using the preferred :ref:`Tor Browser <tor-browser>`.
|
||||
#. **Test** - Try connecting to your server using the preferred :ref:`Tor Browser <tor-browser>`.
|
||||
|
||||
#. **If Tor Browser works** - It means the issue is either with the Tor daemon on your device or with the browser settings.
|
||||
|
||||
@@ -51,19 +51,19 @@ I am unable to reach Embassy via it's xxxxxxxxxxxxxxxxxx.onion (Tor) address
|
||||
#. If you are not yet running a Tor daemon on your device, follow :ref:`these instructions <tor-os>`. If you are already running a Tor daemon, restart it, or in the case of Android, restart your phone.
|
||||
#. If you are using Firefox, ensure it has been :ref:`properly configured <tor-firefox>` to work with .onion URLs.
|
||||
|
||||
#. **If Tor Browser does not work** - It means there is an issue with your Embassy or with the Tor network.
|
||||
#. **If Tor Browser does not work** - It means there is an issue with your server or with the Tor network.
|
||||
|
||||
#. **Test** - Try visiting your Embassy over :ref:`LAN<connecting-lan>` from a non-Tor browser such as Firefox, Chrome, or Safari.
|
||||
#. **Test** - Try visiting your server over :ref:`LAN<connecting-lan>` from a non-Tor browser such as Firefox, Chrome, or Safari.
|
||||
|
||||
#. **If LAN works** - it means the issue is an issue your Embassy's Tor connection.
|
||||
#. **If LAN works** - it means the issue is an issue your server's Tor connection.
|
||||
|
||||
#. **Solutions**
|
||||
#. Check if there are any ongoing network-wide service issues with Tor at `the Tor Project status page <https://status.torproject.org/issues/>`_
|
||||
#. Wait an hour or so to allow Tor on your Embassy to fix itself.
|
||||
#. Restart your Embassy through the UI (Embassy -> Restart).
|
||||
#. **If LAN does not work** - It means your Embassy is experiencing general networking issues.
|
||||
#. Wait an hour or so to allow Tor on your server to fix itself.
|
||||
#. Restart your server through the UI (System -> Restart).
|
||||
#. **If LAN does not work** - It means your server is experiencing general networking issues.
|
||||
|
||||
#. **Solutions** - Power cycle your Embassy by unplugging it and plugging it back in, then wait a few minutes before trying to connect again.
|
||||
#. **Solutions** - Power cycle your server 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
|
||||
---------------------------------------------
|
||||
|
||||
Reference in New Issue
Block a user