Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- faq_1:synology [2026/08/17 05:30] – 192.168.111.134
+++ faq_1:synology [2026/08/18 05:53] (aktuell) – 192.168.111.134
@@ Zeile 7: / Zeile 7: @@
 **Example:**
- %% tailscale up </nowiki&gt%%;
+<nowiki> tailscale up </nowiki></nowiki>; '' ''
-'' ''
 authorization failed: device with nodekey already exists; please log out explicitly and try logging in again
-Kopieren
 A common cause is that the device’s previous Tailscale state still holds a valid node key, so the server refuses to register it again. This can happen after reinstallations, migrations, or when node keys expire and are regenerated.
 To fix this, first log out from Tailscale on the affected device:
+<code bash>
 sudo tailscale logout
+</code>
-Kopieren
 Then log back in:
+<code bash>
 sudo tailscale up
+</code>
-Kopieren
 If logout fails or the state is corrupted, stop the Tailscale service and remove its local state files before restarting:
+<code bash>
 sudo systemctl stop tailscaled
+</code>
+<code bash>
 sudo rm -rf /var/lib/tailscale /var/cache/tailscale
+</code>
+<code bash>
 sudo systemctl start tailscaled
+</code>
+<code bash>
 sudo tailscale up
+</code>
-Kopieren
 On Windows, stop the Tailscale service, delete //C:\ProgramData\Tailscale// and //%LocalAppData%\Tailscale//, then restart and log in again. On macOS, remove ///Library/Tailscale// and related cache directories after stopping the service.