feat: Tailcat peer card forward status + probe diagnostics - #6478
Merged
Conversation
Operators saw a green Tailcat Forwards "running" row while the matching federated peer card stayed offline with opaque probe failures. Linked forward status now lives on the peer card; the standalone panel keeps only orphans. Probes persist a classified lastProbe (local refuse vs tunnel dial vs health/details) for the UI and logs. Fixes #6477
CI failed lib/index.test.js — every non-test server/lib source must be barrel-exported.
Barrel index test also requires every lib source to have a README row.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Operators could see a Tailcat Forwards row green running (
127.0.0.1:15555 → :5555) while the matching federated peer card stayed offline with “Last seen: never” and consecutive probe failures — two surfaces disagreeing with no classified reason.This makes the peer card the primary source of truth for linked Tailcat forwards, and surfaces structured probe diagnostics so bind fail / tunnel fail / PortOS health probe fail are distinguishable.
Fixes #6477
Changes
transport === 'tailcat') embeds forward mapping, live/running/no-route/failed,tunnelError, Retry, and Forget via sharedTailcatForwardStatus.TailcatForwardsPaneldemoted to orphans / pre-peer failures only (nopeerId, or peer gone).POST /api/instances/peers/:id/probeand showslastProbe(class, message, HTTP status, latency, timestamp) plus next-probe timing.lastProbepersisted on probe; classifier inserver/lib/peerProbeDiagnostics.jsforlocal_refused/tunnel_dial/probe_http(etc.); logs include[class];GET /api/instances+ probe + socket broadcast attach redactedtailcatForward.docs/features/tailcat-peers.md.No Tailscale daemon / serve-all / exit-node changes. Default mapping remains 15555→5555. Full
tc…addresses stay redacted.Test plan
cd server && npx vitest run lib/peerProbeDiagnostics.test.js services/tailcatPeer.test.js services/instances.test.js(203 passed)cd client && npx vitest run src/components/instances/TailcatForwardsPanel.test.jsx src/pages/Instances.test.jsx(13 passed)no route/local_refused/tunnel_dialdistinctly after Health check