Start9/documentation
2
0
Fork 0
mirror of https://github.com/Start9Labs/documentation.git synced 2026-03-26 02:11:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix a typo and string in a command (#393)

Browse Source
This commit is contained in:
remiroz
2023-05-26 18:49:56 +01:00
committed by GitHub
parent 189bd79553
commit 25a45c582c
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
site/source/support/faq/faq-troubleshooting.rst
View File

@@ -18,7 +18,7 @@ After plugging into power and your router, you will hear 2 distinct sounds: firs
My server is really hot! Is this normal?
-----------------------------------------
On early devices, yes. These cases are 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.
On early devices, yes. These cases are actually doing 'double duty' as a heat sink. 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.
You can check the chip temperature of your device under "System -> Metrics".

2
site/source/user-manual/ssh.rst
View File

@@ -95,7 +95,7 @@ Connecting via CLI
ssh start9@SERVER-HOSTNAME
Replacing ``<LAN URL>`` with your server's LAN (``<custom-address>.local``) address
Replacing ``<SERVER-HOSTNAME>`` with your server's LAN (``<custom-address>.local``) address
.. note:: If you get a scary looking warning that says something like "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" - fear not! This is most likely happening because you have recently reflashed or did an update from pre-v0.3.3, which would cause a change in the key for your device's hostname (e.g. `xxxxxxxx.local`) or IP address (e.g. `192.168.1.x`). The solution is to delete the existing entry from your `known_hosts` file, which is typically located at `~/.ssh/known_hosts`. This will be specified in the warning, along with a helpful line number (in case your file is lengthy).