Tcp Proxy

Bidirectional TCP forwarding

Category: Setup-dependent integration
Task: Forward raw TCP connections

Prerequisites: Praxis runtime; A TCP backend reachable from the proxy; A TCP client for verification

Expected outcome: Bytes flow bidirectionally between the listener and configured backend.

Run it: Use ghcr.io/praxis-proxy/praxis:0.7.2 and follow the first reverse-proxy tutorial to mount and start the configuration.

This configuration comes from the selected release. The example has not been run here; external services are not bundled.

Download the source file.

# TCP Proxy (L4 Forwarding)
#
# Bidirectional TCP forwarding. No filter chains are configured
# here, so bytes flow between client and upstream unmodified.
# (TCP listeners can use filter chains; see tcp-access-log.yaml.)
# Useful for databases, message brokers, or any non-HTTP protocol.
#
#   Client ──TCP──► Praxis :5432 ──TCP──► PostgreSQL :5432
#
insecure_options:
  allow_private_upstreams: true

listeners:
  - name: postgres
    address: "127.0.0.1:5432"
    protocol: tcp
    upstream: "127.0.0.1:15432"