Failscale keeps stops after a few hours

[Eyegraphic-be]

Hi,

I have a problem with Tailscale on HA (Raspberry 3B+).
When I press 'Start', the software starts running and I can connect to HA from outside of my network.
But after a few hours Tailscale stops working.

That's very annoying.

I've set the DNS and HTTPS settings inside of Tailscale and HA.
I assume all the settings are correct because it works correctly (for a while...)

Can somebody help me out please?

I've added some relevant log files:

2025/01/31 16:12:58 onPortUpdate(port=57122, network=udp6)
2025/01/31 16:12:58 onPortUpdate(port=54209, network=udp4)
2025/01/31 16:12:58 magicsock: disco key = d:773e581fcbad0f0e
2025/01/31 16:12:58 Creating WireGuard device...
2025/01/31 16:12:58 Bringing WireGuard device up...
2025/01/31 16:12:58 Bringing router up...
2025/01/31 16:12:58 Clearing router settings...
2025/01/31 16:12:58 Starting network monitor...
2025/01/31 16:12:58 Engine created.
2025/01/31 16:12:59 pm: using backend prefs for "profile-fa19": Prefs{ra=true dns=true want=true routes=[0.0.0.0/0 ::/0 192.168.0.0/24] snat=true statefulFiltering=false nf=on host="homeassistant" update=check appconnector=advertise Persist{lm=, o=, n=[yy8nA] u="dj.ghesa@gmail.com"}}
2025/01/31 16:12:59 envknob: TS_NO_LOGS_NO_SUPPORT="true"
2025/01/31 16:12:59 logpolicy: using system state directory "/var/lib/tailscale"
2025/01/31 16:12:59 got LocalBackend in 285ms
2025/01/31 16:12:59 Start
2025/01/31 16:12:59 Backend: logs: be:8cc94fbbd6e08c67d9b8f0b1d7a43ac1b7869fd1fa167175d3a2ba9d05b1aca8 fe:
2025/01/31 16:12:59 control: client.Login(0)
2025/01/31 16:12:59 health(warnable=warming-up): error: Tailscale is starting. Please wait.
[16:13:00] ERROR: Tailscale's HTTPS support is disabled
2025/01/31 16:12:59 control: doLogin(regen=false, hasUrl=false)
2025/01/31 16:13:00 control: control server key from [https://controlplane.tailscale.com](https://l.facebook.com/l.php?u=https%3A%2F%2Fcontrolplane.tailscale.com%2F%3Ffbclid%3DIwZXh0bgNhZW0CMTAAAR1pXX96UB4hHvpS2jhGlkMB0B0qy4mPlIxL_s6o7-nAHSJl05UZWek87EQ_aem_Q8_N17S9Y7gy2dtLGIl2uA&h=AT08e7jMGjbjpVOvbF3rEGmmcfTJA7ifuuhZqfDUYku0Re_fqt4X67z12WrmYxgFKWLP4wArFeCvLWYrw1-nhC7UIn_RYgR5qWAK73tWj0wPtqKqgg2Em3Phs3EQUaOTmpI-Itc&__tn__=-UK-R&c[0]=AT2eP7wpdHqeT7bLGsR6zmUrT7KF_memUj7bS1mDlDpYmxEjUj6Xs1L9wMeeXwdFoU3l0NojrRhAqrJfPlHd8jszup4A1mNM3JcJUf0Re9pkBsQijVybGkpSawMngcP4pIAvv7oI_0DgYXHN2dt0VAdxWuv9Vdqivj99NM6h): ts2021=[fSeS+], legacy=[nlFWp]
[16:13:00] INFO: Service serve exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service taildrop: stopping
s6-rc: info: service serve: stopping
s6-rc: info: service nginx: stopping
s6-rc: info: service serve successfully stopped
[16:13:01] INFO: Service taildrop exited with code 256 (by signal 15)
s6-rc: info: service taildrop successfully stopped
s6-rc: info: service post-tailscaled: stopping
s6-rc: info: service post-tailscaled successfully stopped
s6-rc: info: service tailscaled: stopping
[16:13:01] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service web: stopping
s6-rc: info: service init-nginx successfully stopped
[16:13:01] INFO: Service tailscaled exited with code 256 (by signal 15)
s6-rc: info: service tailscaled successfully stopped
[16:13:01] INFO: Service Tailscale web exited with code 256 (by signal 15)
s6-rc: info: service web successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
Add-on: Tailscale
Zero config VPN for building secure networks
Add-on version: 0.24.0
You are running the latest version of this add-on.
System: Home Assistant OS 14.2 (aarch64 / raspberrypi3-64)
Home Assistant Core: 2025.1.4
Home Assistant Supervisor: 2024.12.3
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service web: starting
s6-rc: info: service tailscaled: starting
s6-rc: info: service web successfully started
s6-rc: info: service tailscaled successfully started
s6-rc: info: service post-tailscaled: starting
[21:32:51] INFO: Starting Tailscale web...
[21:32:51] INFO: Starting Tailscale...
[21:32:51] NOTICE: Tailscale logs will be suppressed after 200 lines, set add-on's configuration option 'log_level' to 'debug' to see further logs
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started

[lmagyar]

ERROR: Tailscale's HTTPS support is disabled

Means you try to use serve(proxy) or funnel, and HTTPS is not enabled. See the DOCS.

But after a few hours Tailscale stops working.

This is during startup, not after hours.

[Eyegraphic-be]

Hi,

Thank you for your answer, those lines of code were already in my config file.

Below the log files of the latest start.
Only 7 minutes later, Tailscale already stopped working:

-----------------------------------------------------------
 Add-on: Tailscale
 Zero config VPN for building secure networks
-----------------------------------------------------------
 Add-on version: 0.24.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.2  (aarch64 / raspberrypi3-64)
 Home Assistant Core: 2025.1.4
 Home Assistant Supervisor: 2024.12.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service web: starting
s6-rc: info: service tailscaled: starting
s6-rc: info: service web successfully started
s6-rc: info: service tailscaled successfully started
s6-rc: info: service post-tailscaled: starting
[18:47:49] INFO: Starting Tailscale web...
[18:47:49] INFO: Starting Tailscale...
[18:47:49] NOTICE: Tailscale logs will be suppressed after 200 lines, set add-on's configuration option 'log_level' to 'debug' to see further logs
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
2025/02/03 18:47:52 You have disabled logging. Tailscale will not be able to provide support.
2025/02/03 18:47:52 logtail started
2025/02/03 18:47:52 Program starting: v1.78.1-t8903926f7-gc4163954e, Go 1.23.3: []string{"/opt/tailscaled", "--state=/data/tailscaled.state", "--statedir=/data/state", "--no-logs-no-support", "--tun=userspace-networking"}
2025/02/03 18:47:52 LogID: 015cfb65afd4f92b0d209aa896107867cc66279f49c5d6ed10d5fae8ebfae8e9
2025/02/03 18:47:52 logpolicy: using system state directory "/var/lib/tailscale"
logpolicy.ConfigFromFile /var/lib/tailscale/tailscaled.log.conf: open /var/lib/tailscale/tailscaled.log.conf: no such file or directory
logpolicy.Config.Validate for /var/lib/tailscale/tailscaled.log.conf: config is nil
2025/02/03 18:47:52 dns: [resolved-ping=yes rc=unknown ret=direct]
2025/02/03 18:47:52 dns: using "direct" mode
2025/02/03 18:47:52 dns: using *dns.directManager
2025/02/03 18:47:52 dns: inotify addwatch: context canceled
2025/02/03 18:47:52 wgengine.NewUserspaceEngine(tun "userspace-networking") ...
2025/02/03 18:47:52 dns: using dns.noopManager
2025/02/03 18:47:52 link state: interfaces.State{defaultRoute=enu1u1u1 ifs={docker0:[172.30.232.1/23 llu6] enu1u1u1:[192.168.0.47/24 llu6] hassio:[172.30.32.1/23 llu6]} v4=true v6=false}
2025/02/03 18:47:52 onPortUpdate(port=46816, network=udp6)
2025/02/03 18:47:52 onPortUpdate(port=54417, network=udp4)
2025/02/03 18:47:52 magicsock: disco key = d:60a18ac4dbcd2e9a
2025/02/03 18:47:52 Creating WireGuard device...
2025/02/03 18:47:52 Bringing WireGuard device up...
2025/02/03 18:47:52 Bringing router up...
2025/02/03 18:47:52 Clearing router settings...
2025/02/03 18:47:52 Starting network monitor...
2025/02/03 18:47:52 Engine created.
2025/02/03 18:47:52 pm: using backend prefs for "profile-fa19": Prefs{ra=true dns=true want=true routes=[0.0.0.0/0 ::/0 192.168.0.0/24] snat=true statefulFiltering=false nf=on host="homeassistant" update=check appconnector=advertise Persist{lm=, o=, n=[yy8nA] u="dj.ghesa@gmail.com"}}
2025/02/03 18:47:52 envknob: TS_NO_LOGS_NO_SUPPORT="true"
2025/02/03 18:47:52 logpolicy: using system state directory "/var/lib/tailscale"
2025/02/03 18:47:52 got LocalBackend in 110ms
2025/02/03 18:47:52 Start
2025/02/03 18:47:52 Backend: logs: be:015cfb65afd4f92b0d209aa896107867cc66279f49c5d6ed10d5fae8ebfae8e9 fe:
2025/02/03 18:47:52 control: client.Login(0)
2025/02/03 18:47:52 health(warnable=warming-up): error: Tailscale is starting. Please wait.
2025/02/03 18:47:52 web server running on: http://127.0.0.1:25899
[18:47:52] INFO: Starting NGinx...
2025/02/03 18:47:52 control: doLogin(regen=false, hasUrl=false)
2025/02/03 18:47:53 control: control server key from https://controlplane.tailscale.com: ts2021=[fSeS+], legacy=[nlFWp]
2025/02/03 18:47:53 control: RegisterReq: onode= node=[yy8nA] fup=false nks=false
2025/02/03 18:47:53 control: RegisterReq: got response; nodeKeyExpired=false, machineAuthorized=true; authURL=false
2025/02/03 18:47:53 health(warnable=not-in-map-poll): ok
2025/02/03 18:47:53 control: netmap: got new dial plan from control
2025/02/03 18:47:53 active login: dj.ghesa@gmail.com
2025/02/03 18:47:53 Switching ipn state NoState -> Starting (WantRunning=true, nm=true)
2025/02/03 18:47:53 appc: handling domains: [] and wildcards: []
2025/02/03 18:47:53 monitor: gateway and self IP changed: gw=192.168.0.1 self=192.168.0.47
2025/02/03 18:47:53 magicsock: SetPrivateKey called (init)
2025/02/03 18:47:53 wgengine: Reconfig: configuring userspace WireGuard config (with 0/3 peers)
2025/02/03 18:47:53 wgengine: Reconfig: configuring router
2025/02/03 18:47:53 wgengine: Reconfig: configuring DNS
2025/02/03 18:47:53 dns: Set: {DefaultResolvers:[] Routes:{platy-spica.ts.net.:[] ts.net.:[199.247.155.53 2620:111:8007::53]}+65arpa SearchDomains:[platy-spica.ts.net.] Hosts:4}
2025/02/03 18:47:53 health(warnable=dns-read-os-config-failed): error: Tailscale failed to fetch the DNS configuration of your device: getting OS base config is not supported
2025/02/03 18:47:53 health(warnable=dns): error: getting OS base config is not supported
2025/02/03 18:47:53 peerapi: serving on http://100.69.57.68:40458
2025/02/03 18:47:53 peerapi: serving on http://[fd7a:115c:a1e0::8801:3944]:40458
2025/02/03 18:47:53 appc: handling domains: [] and wildcards: []
2025/02/03 18:47:54 magicsock: home DERP changing from derp-0 [0ms] to derp-14 [18ms]
2025/02/03 18:47:54 magicsock: home is now derp-14 (ams)
2025/02/03 18:47:54 magicsock: adding connection to derp-14 for home-keep-alive
2025/02/03 18:47:54 magicsock: 1 active derp conns: derp-14=cr0s,wr0s
2025/02/03 18:47:54 Switching ipn state Starting -> Running (WantRunning=true, nm=true)
2025/02/03 18:47:54 derphttp.Client.Connect: connecting to derp-14 (ams)
2025/02/03 18:47:54 control: NetInfo: NetInfo{varies=false hairpin= ipv6=false ipv6os=true udp=true icmpv4=false derp=#14 portmap= link="" firewallmode=""}
2025/02/03 18:47:54 health(warnable=warming-up): ok
2025/02/03 18:47:54 health(warnable=no-derp-connection): ok
2025/02/03 18:47:54 magicsock: endpoints changed: 178.51.20.56:17234 (stun), 172.30.32.1:54417 (local), 172.30.232.1:54417 (local), 192.168.0.47:54417 (local)
2025/02/03 18:47:54 health(warnable=no-derp-connection): ok
2025/02/03 18:47:54 health(warnable=no-derp-connection): ok
2025/02/03 18:47:54 [RATELIMIT] format("health(warnable=%s): ok")
[18:47:55] INFO: Tailscale is running
[18:47:55] WARNING: The connection's key will expire on: 2025-07-29T17:40:47Z
[18:47:55] WARNING: Consider disabling key expiry to avoid losing connection to your Home Assistant device.
[18:47:55] WARNING: Please check your configuration based on the add-on's documentation under "Configuration"
[18:47:55] NOTICE: The add-on uses userspace networking mode.
[18:47:55] NOTICE: If you need to access other clients on your tailnet from your Home Assistant instance,
[18:47:55] NOTICE: disable userspace networking mode, that will create a "tailscale0" network interface on your host.
[18:47:55] NOTICE: Please check your configuration based on the add-on's documentation under "Option: userspace_networking"
s6-rc: info: service post-tailscaled successfully started
s6-rc: info: service taildrop: starting
s6-rc: info: service serve: starting
s6-rc: info: service serve successfully started
s6-rc: info: service taildrop successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2025/02/03 18:47:54 magicsock: derp-14 connected; connGen=1
Available within your tailnet:
https://homeassistant.platy-spica.ts.net/
|-- proxy http://127.0.0.1:8123
Press Ctrl+C to exit.
2025/02/03 18:47:57 serve: creating a new proxy handler for http://127.0.0.1:8123
2025/02/03 18:48:36 wgengine: idle peer [e3t+e] now active, reconfiguring WireGuard
2025/02/03 18:48:36 wgengine: Reconfig: configuring userspace WireGuard config (with 1/3 peers)
./run: line 45:   219 Killed                  /opt/tailscaled "${options[@]}" 2>&1
       223 Done                    | stdbuf -i0 -oL -eL sed -n -e '1,200p' -e "201c[further tailscaled logs suppressed, set add-on's configuration option 'log_level' to 'debug' to see further tailscaled logs]"
unexpected EOF
2025/02/03 18:48:37 magicsock: disco: node [e3t+e] d:7f8bd68540e6909e now using 192.168.0.22:39861 mtu=1360 tx=9e60f5f13976
moved 0/0 files
getting WaitingFiles: Get "http://local-tailscaled.sock/localapi/v0/files/?waitsec=0": EOF
[18:53:35] INFO: Service tailscaled exited with code 137 (by signal 0)
[18:53:35] INFO: Service serve exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service taildrop: stopping
s6-rc: info: service serve: stopping
s6-rc: info: service nginx: stopping
s6-rc: info: service serve successfully stopped
[18:53:35] INFO: Service taildrop exited with code 256 (by signal 15)
s6-rc: info: service taildrop successfully stopped
s6-rc: info: service post-tailscaled: stopping
s6-rc: info: service post-tailscaled successfully stopped
[18:53:35] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service tailscaled: stopping
s6-rc: info: service tailscaled successfully stopped
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service web: stopping
s6-rc: info: service init-nginx successfully stopped
[18:53:41] INFO: Service Tailscale web exited with code 256 (by signal 15)
s6-rc: info: service web successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

[lmagyar]

./run: line 45:   219 Killed                  /opt/tailscaled "${options[@]}" 2>&1
       223 Done                    | stdbuf -i0 -oL -eL sed -n -e '1,200p' -e "201c[further tailscaled logs suppressed, set add-on's configuration option 'log_level' to 'debug' to see further tailscaled logs]"
unexpected EOF
...
[18:53:35] INFO: Service tailscaled exited with code 137 (by signal 0)

You've sent kill -9 to tailscaled, and it stopped, what else do you expect?

[Eyegraphic-be]

I just followed the steps to install and configure Tailscale from this tutorial: https://tailscale.com/blog/remotely-access-home-assistant

I stopped at configuring the own domain because I don't need that.

What could be triggering the kill command on HA?

[lmagyar]

Forget any video, uninstall the add-on, reinstall the add-on, read the add-on docs (!!!), it works (with basic functionality) out of the box without any config. After it works, start to configure it step by step.

Github is for issues with the add-on, this is clearly not an add-on related problem, please read the docs and visit the forum or discord for help on how to configure it or Tailscale. Though if you find an error in the add-on docs, we are happy to fix that.

[luizfeliperc]

I have the same problem, here it stops working after some time and I had to activate Watchdog for it to start working automatically again after stopping.

What I have been receiving is an out of memory error in the console related to Tailscale.

s6-rc: info: service post-tailscaled successfully started
s6-rc: info: service taildrop: starting
s6-rc: info: service taildrop successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2025/02/25 21:42:28 magicsock: disco: node [oC8MM] d:a76d0934878b81d5 now using 192.168.0.29:56253 mtu=1360 tx=aeb7cf395bfc
2025/02/25 21:42:31 wgengine: idle peer [uKzd0] now active, reconfiguring WireGuard
2025/02/25 21:42:31 wgengine: Reconfig: configuring userspace WireGuard config (with 3/3 peers)
2025/02/25 21:42:31 magicsock: disco: node [uKzd0] d:7ac79cb2b53c732c now using [2804:14d:5ca5:4ff2:d4ed:c837:6c13:e7f5]:52675 mtu=1360 tx=9c4f70d578b8
2025/02/25 21:42:31 netstack: decrementing connsInFlightByClient[100.101.49.77] because the packet was not handled; new value is 0
2025/02/25 21:42:31 netstack: decrementing connsInFlightByClient[100.101.49.77] because the packet was not handled; new value is 0
2025/02/25 21:42:31 netstack: decrementing connsInFlightByClient[100.101.49.77] because the packet was not handled; new value is 0
2025/02/25 21:42:31 [RATELIMIT] format("netstack: decrementing connsInFlightByClient[%v] because the packet was not handled; new value is %d")
2025/02/25 21:42:31 magicsock: disabled UDP GSO on [::]:32913, NIC(s) may not support checksum offload
2025/02/25 21:43:31 magicsock: disco: node [uKzd0] d:7ac79cb2b53c732c now using 192.168.0.35:43535 mtu=1360 tx=8bad40c94751
2025/02/25 21:44:36 CreateEndpoint error for 100.127.187.123:58235 -> 192.168.0.30:8009: operation timed out
2025/02/25 21:47:04 netstack: could not connect to local backend server at 192.168.0.1:49152: dial tcp 192.168.0.1:49152: connect: connection timed out
2025/02/25 21:47:05 magicsock: disco: node [oC8MM] d:a76d0934878b81d5 now using [2804:14d:5ca5:4ff2:8163:8b1a:4e09:64c0]:38876 mtu=1360 tx=ac7bd4a480f5
2025/02/25 21:47:33 netcheck: DetectCaptivePortal(found=false)
2025/02/25 21:48:05 magicsock: disco: node [oC8MM] d:a76d0934878b81d5 now using 192.168.0.29:56253 mtu=1360 tx=5ac80d5c056e
2025/02/25 21:49:57 netstack: could not bind local port 63609: listen udp [::]:63609: bind: address already in use, trying again with random port
./run: line 45: 232 Killed /opt/tailscaled "${options[@]}" 2>&1
233 Done | stdbuf -i0 -oL -eL sed -n -e '1,200p' -e "201c[further tailscaled logs suppressed, set add-on's configuration option 'log_level' to 'debug' to see further tailscaled logs]"
moved 0/0 files
getting WaitingFiles: Get "http://local-tailscaled.sock/localapi/v0/files/?waitsec=0": EOF
[21:50:20] INFO: Service tailscaled exited with code 137 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service taildrop: stopping
s6-rc: info: service nginx: stopping
[21:50:22] INFO: Service NGINX exited with code 0 (by signal 0)
[21:50:22] INFO: Service taildrop exited with code 256 (by signal 15)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service web: stopping

[lmagyar]

Can be related: #440

Temporarily stop some other add-ons and see whether it helps (ie. more free memory). In case out of mem error, you should stop/delete some of the unused add-ons.

[luizfeliperc]

Can be related: #440

Temporarily stop some other add-ons and see whether it helps (ie. more free memory). In case out of mem error, you should stop/delete some of the unused add-ons.

I've already done this, I thought it could actually be a problem with lack of memory, and if it's a 1GB Pi3 it would even be plausible.
The problem is that only Tailscale stops working and restarts automatically (when Watchdog) is activated.

I only have 3 add-ons besides Tailscale (HACS, Yerminal and File editor) and the problem does not occur because of them.

In fact, there is an error in Tailscale and it is closed and started again, even with the out of memory error.

[lmagyar]

Do you transfer large files during that hour? That can cause out-of-memory kill, it's seems to be a knows TS issue, caused by WireGuard. Just a quick search result (I didn't read them): tailscale/tailscale#11382 WireGuard/wireguard-go#69 tailscale/tailscale#7571 tailscale/tailscale#7272 tailscale/tailscale#3745

[luizfeliperc]

Do you transfer large files during that hour? That can cause out-of-memory kill, it's seems to be a knows TS issue, caused by WireGuard. Just a quick search result (I didn't read them): tailscale/tailscale#11382 WireGuard/wireguard-go#69 tailscale/tailscale#7571 tailscale/tailscale#7272 tailscale/tailscale#3745

I have no file transfers.
My HA is very simple, I just have a few lamps, 2 IR receivers and a camera connected to it.

[sinclairpaul]

Your system is running out of memory, you can see that as the oom killer is terminating processes.

There is really only two ways to fix this, run less, or add more memory.

[luizfeliperc]

Your system is running out of memory, you can see that as the oom killer is terminating processes.

There is really only two ways to fix this, run less, or add more memory.

Yes, only with Tailscale.
The system is closing the process, but I don't see the HA going offline, only if connected to Tailscale.
As I said, everything is running smoothly, but Tailscale is constantly shutting down

2025/02/26 16:46:42 CreateEndpoint error for 100.101.49.77:60774 -> 100.103.60.38:8123: connection was refused
./run: line 45: 490 Killed /opt/tailscaled "${options[@]}" 2>&1
491 Done | stdbuf -i0 -oL -eL sed -n -e '1,200p' -e "201c[further tailscaled logs suppressed, set add-on's configuration option 'log_level' to 'debug' to see further tailscaled logs]"
moved 0/0 files
getting WaitingFiles: Failed to connect to local Tailscale daemon for /localapi/v0/files/; not running? Error: dial unix /var/run/tailscale/tailscaled.sock: connect: connection refused
[16:47:27] INFO: Service tailscaled exited with code 137 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service taildrop: stopping
s6-rc: info: service nginx: stopping
[16:47:29] INFO: Service taildrop exited with code 256 (by signal 15)
[16:47:29] INFO: Service NGINX exited with code 0 (by signal 0)
[16:47:29] INFO: Starting Tailscale...
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service web: stopping
s6-rc: info: service taildrop successfully stopped
s6-rc: info: service post-tailscaled: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service post-tailscaled successfully stopped
s6-rc: info: service tailscaled: stopping
[16:47:29] INFO: Service tailscaled exited with code 256 (by signal 15)
[16:47:29] INFO: Service Tailscale web exited with code 256 (by signal 15)
s6-rc: info: service tailscaled successfully stopped
s6-rc: info: service web successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped

[sinclairpaul]

Tailscale is the victim of the OOM process, not necessarily causing the issue, either way there isn't anything that can be done here.

[lmagyar]

86% mem usage is extremely high. In my experience, above 70% mem usage will cause issues. Not the 2 lamp entity eats up the mem, more likely other add-ons.

You should run less.