No logs arriving

Work from the sender response toward Live Tail. Do not rotate credentials or recreate a receiver before you know which step failed.

1. Confirm the receiver

• The receiver is active.
• The sender uses the exact URL, hostname, port, transport, and TLS rules shown by Fluxtail.
• The receiver routes to the stream you are viewing.

2. Confirm authentication

For shared receivers, the Bearer token must be active and bound to the same receiver. For dedicated receivers, the sender’s public IPv4 must match an allowed IPv4 or CIDR rule.

Sender fields such as host, tag, stream ID, or GELF host do not authenticate the sender.

3. Read the sender result

Result	Check
401	Missing, invalid, or wrong receiver token.
403	Protocol, receiver, or source policy mismatch.
404	Wrong path or receiver ID.
413	Payload or batch too large.
415	Wrong content type, encoding, or protocol version.
429	Account or receiver event budget reached.
503	Temporary authentication, rate-limit, or queue dependency failure. Retry with backoff.
Timeout	DNS, firewall, transport, or TLS path.

Dedicated UDP senders do not receive an acknowledgement. Verify their hostname, port, public source IPv4, and outbound firewall directly.

4. Clear read filters

Open the configured stream in Live Tail, clear message, service, severity, label, Kubernetes, and time filters, then send a unique new message.

Older logs load only when you scroll near the top. A narrow time filter can hide a correctly stored event.

5. Run one known test

Use the test command from the matching receiver guide. Search its exact message in Live Tail.

If the sender is accepted but the known event remains missing, keep the timestamp, receiver ID, HTTP status or client error, and public source IPv4 for support. Never send the token value.