Project

General

Profile

Actions

Bug #13632

open

tailscale does not survive reboot on pfsense with ram disk in use

Added by Bill Flood 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Category:
Tailscale
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.6.0
Affected Plus Version:
Affected Architecture:
All

Description

pfSense-pkg-Tailscale 0.1.0_1pfSense package Tailscale 1.26.2
pfsense 2.6.0-RELEASE (amd64)

With a properly configured and connected Tailscale configuration setup the authentication with Tailscale fails after reboot when using a Ram disk on pfsense. Keys are set to not expire. When the Ram disk is disabled (assuming a new key is used after a failure) the connection succeeds after every reboot. Expectation is that a configuration can survive a reboot/crash as configuration and keys should be stored in non-volatile locations like any other service.

The status log on failure shows:

Error executing command (/usr/local/bin/tailscale status)
  1. Health check:
  2. - not logged in, last login error=invalid key: API key [key id shown here] not valid

Logged out.

Actions #1

Updated by Bill Flood 3 months ago

The ram disk is configured in pfsense->System->Advanced->Miscellaneous and backup parameters are populated.

Actions

Also available in: Atom PDF