mirror of
https://github.com/mynodebtc/mynode.git
synced 2024-12-25 22:18:07 +00:00
Update system notes
This commit is contained in:
parent
f7d41729ca
commit
2e6c904d1a
|
@ -2,6 +2,14 @@
|
||||||
|
|
||||||
Various restrictions and behaviors of myNode and the various applications are documented below.
|
Various restrictions and behaviors of myNode and the various applications are documented below.
|
||||||
|
|
||||||
|
## General
|
||||||
|
- Not all applications can be enabled at once on most hardware. It will overload the system resources and cause unstable
|
||||||
|
behavior. If this happens, try disabling some applications. Some examples of this are:
|
||||||
|
-- Applications crashing, especially Bitcoin, and it will appear like blocks are lost and need to be re-synced
|
||||||
|
-- The Bitcoin log may show numerous "RPC Work Queue" errors
|
||||||
|
-- Electrum may stop syncing at a specific block until the device is rebooted.
|
||||||
|
|
||||||
|
|
||||||
## Thunderhub
|
## Thunderhub
|
||||||
|
|
||||||
- When Thunderhub is first installed, logging in will be disabled. You must either change your password or log out and log back in of the the myNode UI before using Thunderhub. At that point, Thunderhub will use the same password as myNode.
|
- When Thunderhub is first installed, logging in will be disabled. You must either change your password or log out and log back in of the the myNode UI before using Thunderhub. At that point, Thunderhub will use the same password as myNode.
|
||||||
|
@ -21,4 +29,13 @@ Various restrictions and behaviors of myNode and the various applications are do
|
||||||
|
|
||||||
## Sphinx Relay
|
## Sphinx Relay
|
||||||
|
|
||||||
- Connection strings may only work a single time but are re-generated on each reboot. Since myNode does not know which string was used to successfully connect, they continue to be displayed in the UI, even though they may no longer be valid.
|
- Connection strings may only work a single time but are re-generated on each reboot. Since myNode does not know which string was used to successfully connect, they continue to be displayed in the UI, even though they may no longer be valid.
|
||||||
|
|
||||||
|
## Mempool
|
||||||
|
|
||||||
|
- Mempool can be resource intensive on some hardware. If the device runs slowly, try disabling some applications.
|
||||||
|
|
||||||
|
## Specter
|
||||||
|
|
||||||
|
- Specter authentication is off by default, but it will store and use its own password.
|
||||||
|
- It is highly recommended to enable authentication.
|
||||||
|
|
|
@ -56,16 +56,12 @@
|
||||||
<div class="app_title">Mempool</div>
|
<div class="app_title">Mempool</div>
|
||||||
<div class="app_status" id="mempoolspace_status">{{ mempoolspace_status }}</div>
|
<div class="app_status" id="mempoolspace_status">{{ mempoolspace_status }}</div>
|
||||||
<div class="app_contents">
|
<div class="app_contents">
|
||||||
{% if product_key_skipped %}
|
{% if not is_installing_docker_images %}
|
||||||
Premium Feature
|
{% if mempoolspace_enabled %}
|
||||||
{% else %}
|
<a class="ui-button ui-widget ui-corner-all mynode_button" href="#" id="mempoolspace">View</a>
|
||||||
{% if not is_installing_docker_images %}
|
<a class="ui-button ui-widget ui-corner-all mynode_button" href="#" id="toggle-mempoolspace">Disable</a>
|
||||||
{% if mempoolspace_enabled %}
|
{% else %}
|
||||||
<a class="ui-button ui-widget ui-corner-all mynode_button" href="#" id="mempoolspace">View</a>
|
<a class="ui-button ui-widget ui-corner-all mynode_button" href="#" id="toggle-mempoolspace">Enable</a>
|
||||||
<a class="ui-button ui-widget ui-corner-all mynode_button" href="#" id="toggle-mempoolspace">Disable</a>
|
|
||||||
{% else %}
|
|
||||||
<a class="ui-button ui-widget ui-corner-all mynode_button" href="#" id="toggle-mempoolspace">Enable</a>
|
|
||||||
{% endif %}
|
|
||||||
{% endif %}
|
{% endif %}
|
||||||
{% endif %}
|
{% endif %}
|
||||||
</div>
|
</div>
|
||||||
|
|
Loading…
Reference in New Issue
Block a user