GITBOOK-169: change request with no subject merged in GitBook

bitcoin/blockchain-explorer.md

@@ -310,7 +310,7 @@ $ journalctl -f -u btcrpcexplorer
 
 ## Run
 
-To keep an eye on the software movements, [start your SSH program](../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "admin". Commands for the **second session** start with the prompt `$2` (which must not be entered).
+To keep an eye on the software movements, [start your SSH program](../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "admin". Commands for the **second session** start with the prompt **`$2` (which must not be entered).**
 
 * Start the service
 
@@ -385,8 +385,17 @@ $ sudo ss -tulpn | grep LISTEN | grep node | grep 3002
 
 Expected output:
 
+<pre><code><strong>> tcp   LISTEN 0   511   127.0.0.1:3002   0.0.0.0:*   users:(("node",pid=140461,fd=20))
+</strong></code></pre>
+
+* And the HTTPS `4000` port
+
+```bash
+$ sudo ss -tulpn | grep LISTEN | grep node | grep 4000
+```
+
 ```
-tcp   LISTEN 0   511   127.0.0.1:3002   0.0.0.0:*   users:(("node",pid=140461,fd=20))
+> tcp   LISTEN 0      511          0.0.0.0:4000       0.0.0.0:*    users:(("nginx",pid=876,fd=7),("nginx",pid=875,fd=7),("nginx",pid=874,fd=7),("nginx",pid=873,fd=7),("nginx",pid=872,fd=7))
 ```
 
 {% hint style="success" %}

bitcoin/electrum-server.md

@@ -82,6 +82,17 @@ zmqpubhashblock=tcp://127.0.0.1:8433
 $ sudo systemctl restart bitcoind
 ```
 
+* Check Bitcoin Core is enabled `zmqpubhashblock` on the `8433` port
+
+```bash
+$ sudo ss -tulpn | grep LISTEN | grep bitcoind | grep 8433
+```
+
+Expected output:
+
+<pre><code>> tcp   LISTEN 0      100        127.0.0.1:<a data-footnote-ref href="#user-content-fn-1">8433</a>       0.0.0.0:*    users:(("bitcoind",pid=773834,fd=18))
+</code></pre>
+
 ## Installation
 
 ### Download and set up Fulcrum
@@ -171,7 +182,7 @@ $ sha256sum --check Fulcrum-$VERSION-sha256sums.txt
 Fulcrum-1.9.4-arm64-linux.tar.gz: FAILED open or read
 sha256sum: Fulcrum-1.9.4-x86_64-linux-ub16.tar.gz: No such file or directory
 Fulcrum-1.9.4-x86_64-linux-ub16.tar.gz: FAILED open or read
-<strong><a data-footnote-ref href="#user-content-fn-1">Fulcrum-1.9.4-x86_64-linux.tar.gz: OK</a>
+<strong><a data-footnote-ref href="#user-content-fn-2">Fulcrum-1.9.4-x86_64-linux.tar.gz: OK</a>
 </strong>sha256sum: Fulcrum-1.9.4-win64.zip: No such file or directory
 Fulcrum-1.9.4-win64.zip: FAILED open or read
 sha256sum: WARNING: 3 listed files could not be read
@@ -278,7 +289,7 @@ drwxr-xr-x 6 root    root    4096 Jul 15 07:56 ..
 -rw------- 1 fulcrum fulcrum   24 Jul 15 07:59 .bash_history
 -rw-r--r-- 1 fulcrum fulcrum  220 Jul 15 07:56 .bash_logout
 -rw-r--r-- 1 fulcrum fulcrum 3771 Jul 15 07:56 .bashrc
-lrwxrwxrwx 1 fulcrum fulcrum   13 Jul 15 07:59 <a data-footnote-ref href="#user-content-fn-2">.fulcrum -> /data/fulcrum</a>
+lrwxrwxrwx 1 fulcrum fulcrum   13 Jul 15 07:59 <a data-footnote-ref href="#user-content-fn-3">.fulcrum -> /data/fulcrum</a>
 -rw-r--r-- 1 fulcrum fulcrum  807 Jul 15 07:56 .profile
 </code></pre>
 
@@ -403,7 +414,9 @@ $ journalctl -f -u fulcrum
 
 ## Run
 
-To keep an eye on the software movements, [start your SSH program](../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "admin". Commands for the **second session** start with the prompt `$2` (which must not be entered)
+To keep an eye on the software movements, [start your SSH program](../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "admin". Commands for the **second session** start with the prompt **`$2` (which must not be entered).**
+
+* Start the service
 
 ```sh
 $2 sudo systemctl start fulcrum
@@ -445,7 +458,7 @@ DO NOT REBOOT OR STOP THE SERVICE DURING THE DB CREATION PROCESS. YOU MAY CORRUP
 
 <figure><img src="../.gitbook/assets/fulcrum-index-finished.PNG" alt=""><figcaption></figcaption></figure>
 
-* Ensure the service is working and listening at the default `50002` & `50001` ports
+* Ensure the service is working and listening at the default `50002` & `50001` ports and the `8000` admin port
 
 ```sh
 $2 sudo ss -tulpn | grep LISTEN | grep Fulcrum
@@ -743,6 +756,8 @@ Filename            Type                Size           Used    Priority
 /var/swap           file                 102396         0       -2
 ```
 
-[^1]: That's it!
+[^1]: zmqpubhashblock port
+
+[^2]: That's it!
 
-[^2]: Symbolic link
+[^3]: Symbolic link

bonus-guides/bitcoin/btcpay-server.md

@@ -94,7 +94,7 @@ We need to set up settings in the Bitcoin Core configuration file - add new line
 $ sudo nano /data/bitcoin/bitcoin.conf
 ```
 
-<pre><code><strong># NBXplorer dependency
+<pre><code><strong># NBXplorer requeriment
 </strong><strong>whitelist=127.0.0.1
 </strong></code></pre>
 
@@ -794,9 +794,20 @@ $ sudo ss -tulpn | grep LISTEN | grep 23000
 Expected output:
 
 ```
-> tcp   LISTEN 0   512   127.0.0.1:23000   0.0.0.0:*    users:(("dotnet",pid=2811744,fd=320))
+> tcp   LISTEN 0   512        127.0.0.1:23000   0.0.0.0:*    users:(("dotnet",pid=2811744,fd=320))
 ```
 
+* And the `HTTP` Ngnix listening on the port `230001`
+
+```bash
+$ sudo ss -tulpn | grep LISTEN | grep 23001
+```
+
+Expected output:
+
+<pre><code><strong>> tcp   LISTEN 0      511      0.0.0.0:23001      0.0.0.0:*    users:(("nginx",pid=876,fd=6),("nginx",pid=875,fd=6),("nginx",pid=874,fd=6),("nginx",pid=873,fd=6),("nginx",pid=872,fd=6))
+</strong></code></pre>
+
 Now point your browser to the secure access point provided by the NGINX web proxy, for example, `"https://minibolt.local:23001"` (or your node IP address) like `"https://192.168.0.20:23001"`.
 
 Your browser will display a warning because we use a self-signed SSL certificate. We can do nothing about that because we would need a proper domain name (e.g., https://yournode.com) to get an official certificate that browsers recognize. Click on "Advanced" and proceed to the BTCPay Server web interface. On the login page, you should see the registration process.
@@ -851,22 +862,50 @@ $ sudo cat /var/lib/tor/hidden_service_btcpay/hostname
 
 ### Connect to your LND internal node
 
-* With user `admin`, change to the `lnd` user
+#### Configure LND
+
+* Stay logged as `admin` user, and configure LND to allow LND REST from anywhere editing the `lnd.conf` file
 
 ```bash
-$ sudo su - lnd
+$ sudo nano /data/lnd/lnd.conf
+```
+
+* Add the next line under the `[Application Options]` section. Save and exit
+
+```
+# Specify all ipv4 interfaces to listen on for REST connections
+restlisten=0.0.0.0:8080
+```
+
+* Restart LND to apply changes
+
+```bash
+$ sudo systemctl restart lnd
+```
+
+* Ensure the REST port is now binding to the `0.0.0.0`  host instead of `127.0.0.1`
+
+```bash
+$ sudo ss -tulpn | grep LISTEN | grep lnd | grep 8080
 ```
 
-* Go to the `lnd` folder
+Expected output:
+
+<pre><code><strong>> tcp   LISTEN 0      4096         0.0.0.0:8080       0.0.0.0:*    users:(("lnd",pid=774047,fd=32))
+</strong></code></pre>
+
+#### Generate the `tls.cert` fingerprint of LND
+
+* With user `admin`, change to the `lnd` user
 
 ```bash
-$ cd /data/lnd
+$ sudo su - lnd
 ```
 
 * Get the LND's certificate fingerprint
 
 ```bash
-$ openssl x509 -noout -fingerprint -sha256 -inform pem -in tls.cert
+$ openssl x509 -noout -fingerprint -sha256 -inform pem -in /data/lnd/tls.cert
 ```
 
 **Example** of expected output:
@@ -903,7 +942,7 @@ $ sudo cp /data/lnd/data/chain/bitcoin/mainnet/admin.macaroon /home/btcpay/admin
 $ sudo chown btcpay:btcpay /home/btcpay/admin.macaroon
 ```
 
-* Stop BTCpay
+* Stop BTCPay Server before making changes
 
 ```bash
 $ sudo systemctl stop btcpay
@@ -915,22 +954,16 @@ $ sudo systemctl stop btcpay
 $ sudo su - btcpay
 ```
 
-* Go to the `.btcpayserver` folder
-
-```bash
-$ cd ~/.btcpayserver/Main
-```
-
 * Edit the `settings.config` file
 
 ```bash
-$ nano settings.config
+$ nano /.btcpayserver/Main/settings.config
 ```
 
 * Add the next content to the end of the file, replacing `<fingerprint>` with your own obtained earlier. Save and exit
 
 ```
-# Lightning
+# Lightning internal node connection
 BTC.lightning=type=lnd-rest;server=https://127.0.0.1:8080/;macaroonfilepath=/home/btcpay/admin.macaroon;certthumbprint=<fingerprint>
 ```
 
@@ -940,7 +973,7 @@ BTC.lightning=type=lnd-rest;server=https://127.0.0.1:8080/;macaroonfilepath=/hom
 $ exit
 ```
 
-* Start BTCpay again. Monitor logs with `$ sudo journalctl -f -u btcpay` to ensure that all is running well
+* Start BTCpay again. Monitor logs with `$ journalctl -f -u btcpay` to ensure that all is running well
 
 ```bash
 $ sudo systemctl start btcpay

bonus-guides/bitcoin/nostr-relay.md

@@ -379,7 +379,7 @@ Jul 31 19:11:59 minibolt nostr-rs-relay[35593]: 2023-07-31T19:11:59.275842Z  INF
 
 </details>
 
-* Ensure the service is working and listening at the default **8880** port
+* Ensure the service is working and listening at the default `8880` port
 
 ```bash
 $ sudo ss -tulpn | grep LISTEN | grep nostr-rs-relay

bonus-guides/system/cloudflare-tunnel.md

@@ -364,7 +364,9 @@ Keep **this terminal open,** you'll need to come back here on the next step to m
 
 ## Run <a href="#6-run-the-tunnel" id="6-run-the-tunnel"></a>
 
-To keep an eye on the software movements, [start your SSH program](../../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as `admin`. Commands for the **second session** start with the prompt `$2` (which must not be entered). Run the tunnel to proxy incoming traffic from the tunnel to any number of services running locally on your origin.
+To keep an eye on the software movements, [start your SSH program](../../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as `admin`. Commands for the **second session** start with the prompt **`$2` (which must not be entered)**. Run the tunnel to proxy incoming traffic from the tunnel to any number of services running locally on your origin.
+
+* Start the service
 
 ```bash
 $2 sudo systemctl start cloudflared

bonus-guides/system/nym-mixnet.md

@@ -270,7 +270,7 @@ $ journalctl -f -u nym-network-requester
 
 ### Running network requester
 
-To keep an eye on the software movements, [start your SSH program](../../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "admin". Commands for the **second session** start with the prompt `$2` (which must not be entered).
+To keep an eye on the software movements, [start your SSH program](../../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "admin". Commands for the **second session** start with the prompt **`$2` (which must not be entered).**
 
 * Start the nym network requester service
 
@@ -454,7 +454,7 @@ $ journalctl -f -u nym-socks5-client
 
 ### Running socks5 client
 
-To keep an eye on the software movements, [start your SSH program](../../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "admin". Commands for the **second session** start with the prompt `$2` (which must not be entered).
+To keep an eye on the software movements, [start your SSH program](../../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "admin". Commands for the **second session** start with the prompt **`$2` (which must not be entered).**
 
 * Start the nym socks5 client service
 
@@ -528,7 +528,7 @@ $ sudo nano /home/bitcoin/.bitcoin/bitcoin.conf
 ```
 
 ```
-# Proxy clearnet (ipv4) outbound connection using NYM SOCKS5 proxy
+# Connect to clearnet using NYM SOCKS5 proxy
 proxy=127.0.0.1:1080
 ```
 
@@ -559,7 +559,7 @@ Expected output:
 ```
 
 {% hint style="info" %}
-If you have installed the NYM socks5 client in another machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. 192.168.1.94:1080
+If you have installed the NYM socks5 client installed in a machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. `192.168.1.94:1080`
 {% endhint %}
 
 ### NYM connect
@@ -602,7 +602,7 @@ Or directly on the interface; on the top menu, go to **Tools** --> **Network** -
 
 <figure><img src="../../.gitbook/assets/electrum-nym-proxy.PNG" alt=""><figcaption><p>Electrum SOCKS5 proxy configuration</p></figcaption></figure>
 
-
+ 
 
 <figure><img src="../../.gitbook/assets/electrum-nym-proxy-nodes.webp" alt=""><figcaption><p>Electrum servers connected using NYM mixnet</p></figcaption></figure>
 
@@ -621,7 +621,7 @@ $ ./electrum-4.4.5-x86_64.AppImage -1 -s 192.168.1.147:50002:s -p socks5:localho
 <figure><img src="../../.gitbook/assets/nym-one-server-proxy-nym.PNG" alt="" width="377"><figcaption></figcaption></figure>
 
 {% hint style="info" %}
-If you have installed the NYM socks5 client in another machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. 192.168.1.94:1080
+If you have installed the NYM socks5 client installed in a machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. `192.168.1.94:1080`
 {% endhint %}
 
 #### Sparrow desktop
@@ -647,7 +647,7 @@ Follow the [Desktop wallet: Sparrow Wallet](../../bitcoin/desktop-wallet.md) unt
 <figure><img src="../../.gitbook/assets/sparrow-private-server-proxy-nym.PNG" alt="" width="563"><figcaption></figcaption></figure>
 
 {% hint style="info" %}
-If you have installed the NYM socks5 client in another machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. 192.168.1.94:1080
+If you have installed the NYM socks5 client installed in a machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. `192.168.1.94:1080`
 {% endhint %}
 
 #### Sparrow server
@@ -687,7 +687,7 @@ You have Sparrow server configured to proxy public Electrum servers and third pa
 {% endhint %}
 
 {% hint style="info" %}
-If you have installed the NYM socks5 client in another machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. 192.168.1.94:1080
+If you have installed the NYM socks5 client installed in a machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. `192.168.1.94:1080`
 {% endhint %}
 
 #### Blockstream Green
@@ -718,7 +718,7 @@ Go to "Connect your own full node" --> Check the pre-setted Electrum servers Bit
 <figure><img src="../../.gitbook/assets/bitbox-app-nym-proxy-check.PNG" alt="" width="563"><figcaption></figcaption></figure>
 
 {% hint style="info" %}
-If you have installed the NYM socks5 client in another machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. 192.168.1.94:1080
+If you have installed the NYM socks5 client installed in a machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. `192.168.1.94:1080`
 {% endhint %}
 
 #### Nunchuk desktop
@@ -731,14 +731,14 @@ Go to **Settings** --> **Network Settings** --> **Enable Tor proxy,** check **"E
 
 <figure><img src="../../.gitbook/assets/nunckuk_nym_settings.PNG" alt=""><figcaption></figcaption></figure>
 
-
+ 
 
 <figure><img src="../../.gitbook/assets/nunckuk_nym.PNG" alt="" width="375"><figcaption></figcaption></figure>
 
 </div>
 
 {% hint style="info" %}
-If you have installed the NYM socks5 client in another machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. 192.168.1.94:1080
+If you have installed the NYM socks5 client installed in a machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. `192.168.1.94:1080`
 {% endhint %}
 
 ### Proxying other services
@@ -760,7 +760,7 @@ Go to **Settings** --> **Advanced -->** Navigate to **"Proxy settings",** and ch
 {% endhint %}
 
 {% hint style="info" %}
-If you have installed the NYM socks5 client in another machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. 192.168.1.94:1080
+If you have installed the NYM socks5 client installed in a machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. `192.168.1.94:1080`
 {% endhint %}
 
 #### Telegram Desktop
@@ -776,7 +776,7 @@ Save and close all banners to go back to the running app
 {% endhint %}
 
 {% hint style="info" %}
-If you have installed the NYM socks5 client in another machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. 192.168.1.94:1080
+If you have installed the NYM socks5 client installed in a machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. `192.168.1.94:1080`
 {% endhint %}
 
 #### Browser (Firefox-based browsers)
@@ -794,7 +794,7 @@ Press OK and start the navigation
 {% endhint %}
 
 {% hint style="info" %}
-If you have installed the NYM socks5 client in another machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. 192.168.1.94:1080
+If you have installed the NYM socks5 client installed in a machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. `192.168.1.94:1080`
 {% endhint %}
 
 ### NYM Android
@@ -825,7 +825,7 @@ Save, switch "Use proxy" again
 
 <figure><img src="../../.gitbook/assets/telegram-app-nym-proxy-available.jpg" alt=""><figcaption></figcaption></figure>
 
-
+ 
 
 <figure><img src="../../.gitbook/assets/telegram-app-nym-proxy-connected.jpg" alt=""><figcaption></figcaption></figure>
 
@@ -836,7 +836,7 @@ Save, switch "Use proxy" again
 {% endhint %}
 
 {% hint style="info" %}
-If you have installed the NYM socks5 client in another machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. 192.168.1.94:1080
+If you have installed the NYM socks5 client installed in a machine inside of your local network, you can point the service to its IP address **instead of localhost** (127.0.0.1), e.g. `192.168.1.94:1080`
 {% endhint %}
 
 ### Other NYM tools

bonus-guides/system/rustup-+-cargo.md

@@ -87,7 +87,7 @@ Current installation options:
 </details>
 
 {% hint style="info" %}
-When the prompt asks you to choose an option, type "`1`" and press enter to "Proceed with installation"
+When the prompt asks you to choose an option, type **"`1`"** and press **enter** to "Proceed with installation"
 {% endhint %}
 
 <details>