Operations
Bridge dashboard
Simulator inputs
Live multicast and forwarding activity
TAK link traffic
Application payload counters for this bridge process
- Connection target
- —
- TLS certificate name
- —
- TLS session
- —
- Forwarded CoT
- 0
- Heartbeats
- 0
- TX messages / bytes
- 0 / 0 B
- Last transmit
- —
- RX CoT / chunks / bytes
- 0 / 0 / 0 B
- Last receive
- —
Connected means TLS negotiation completed. Increasing TX counters confirms local socket writes, but neither result proves that TAK routed the CoT to clients. Use TEST Mode for an independent marker and confirm it on a TAK client.
Issues
Configuration and runtime findings
Next maintenance
Scheduled bridge-only restart
- Schedule
- Disabled
- Next restart
- —
- Last scheduled
- —
Configuration
Bridge setup
Changes are validated and stored under princetak-data/config.
TAK server
Mutual-TLS streaming connection
Simulators
Add one configuration for each PRINCE video/KLV source.
Security
Client certificates
Private material is stored only under princetak-data/certs.
PEM files
Install a certificate and matching private key.
PKCS#12 bundle
Import a P12 or PFX client package.
TAK automatic enrollment
Generates a local private key and sends only the CSR. Enrollment credentials are never saved.
Diagnostics
TEST Mode
Send a synthetic CoT marker without using PRINCE multicast, KLV, or the bridge worker.
Independent CoT marker
Uses a separate one-shot TCP/TLS connection so simulator input cannot affect the result.
Maintenance
Restart schedule
The WebUI stays online; only the bridge worker is restarted.
Diagnostics
Bridge logs
Persistent, rotated logs from the managed bridge worker.
No log output.
Management
System settings
Container liveness remains independent from bridge readiness.
WebUI listener
Changing the port restarts the management process.
Docker health
Safe liveness information for Docker and reverse proxies.
- Liveness
- Healthy
- Health endpoint
/api/health/live- Persistent root
princetak-data- Production network
- Linux host networking