Selfhosted Github Runner Goes Offline After Starting Tailscale | Tailscale Community | Page 1

hybrid sedge Sep 16, 2025, 6:29 PM

#

OS: AlmaLinux 10.0 (Purple Lion)
Runner: linux-x64-2.328.0
Tailscale: 1.86.2
tailscale commit: c47caa10d6268583103fd4363792f577a584492c
long version: 1.86.2-tc47caa10d-gf5d087d04
other commit: f5d087d0447069b01b0b15ce03b54419a210d405
go version: go1.24.4

hybrid sedge Sep 21, 2025, 9:43 AM

#

Okay.. so no help

manic lion Sep 21, 2025, 2:01 PM

#

I think instead of using up

#

you should use

tailscale set instead

rotund fjord Sep 21, 2025, 4:34 PM

#

you have not provided enough information to get help here.

What does "go down" mean?
Can you get onto the box to debug if you still have network access?
if you run without accept-routes what happens?

hybrid sedge Sep 23, 2025, 11:27 AM

#

Thanks for the reply.

Without using --accept-routes, Github runner works just fine. But I need those routes in order to access the other clients and it's network devices.

#

When using --accept-routes, GitHub runner goes offline. Most of the GitHub servers/services becomes unreachable

rotund fjord Sep 23, 2025, 1:21 PM

#

that would indicate to me that its likely that accepting routes is breaking the route table. You'd need local access to the box during setup to debug, can you get a console?

#Selfhosted Github Runner Goes Offline After Starting Tailscale