Troubleshooting
Separate dashboard state, relay propagation, network delivery, and application consumption when diagnosing the feed.
Dashboard states
| Dashboard state | Meaning |
|---|---|
| Not configured | No private ShredStream destination has been prepared for this server. |
| Preparing | The control plane is attaching or reconciling the private interface. |
| Off | The private address is reserved, but relay discovery excludes the server. |
| On | The server is included in discovery; allow up to 60 seconds for relay refresh. |
| Unavailable | The server could not receive a ShredStream interface during provisioning. |
| Setup failed | The latest interface setup job failed; the displayed error contains the reason. |
No packets arrive
- Confirm the subscription and server provisioning state are active.
- Confirm the dashboard row shows
On, then wait a full 60 seconds. - Confirm the private 10.250.0.x address exists inside the selected server.
- Use a bounded packet capture before debugging the application listener.
- If packets appear in tcpdump but not in the application, check its bind address, UDP port, receive buffer, and local firewall.
# Private address expected on an enabled serverip -4 -br addr | grep '10.250.0.' # Bounded packet capture: five packets or a 15-second timeoutsudo timeout 15 tcpdump -ni any 'udp and dst port 20001' -c 5 # Confirm your application owns the UDP socketss -lunp | grep ':20001'The listener is running but receives nothing
Verify that the process is bound to UDP, not TCP, and to port 20001. Binding to 0.0.0.0:20001 accepts traffic arriving on the private interface. If the process binds a specific address, use the assigned 10.250.0.xaddress rather than the server's public IP.
Setup asks to reboot
This applies to legacy servers that were created before the private interface was included during provisioning. The customer flow performs one graceful stop and restart only after confirmation. If downtime is unacceptable, contact support for a no-reboot reconciliation attempt. That attempt will fail rather than alter the server's power state when the interface is not already usable.
Bare metal has no destination
Bare metal does not use the automated VMM interface workflow. Contact support if its row saysNot configured; support must prepare the isolated network path and assign the private destination before you can enable delivery.
API key errors
There is no ShredStream API key to place in your application. OpenInfra project keys authenticate RPC, WebSocket, gRPC, and data-stream services, but they are unrelated to this private UDP feed. Authorization is the server's enabled state in the project Solana page.
High CPU, packet loss, or storage growth
- Avoid printing every packet or continuously appending raw packets to a file.
- Use bounded captures with a packet count and timeout for diagnostics.
- Increase application receive buffers only after measuring kernel drops and consumer throughput.
- Disable delivery while repairing or replacing a consumer so the relay stops sending to it.