-
Troubleshooting and Debugging Bridge Issues 0 hr 10 min
-
Share your feedback
This video is still being processed. Please check back later and refresh the page.
Uh oh! Something went wrong, please try again.
Troubleshooting and Debugging Bridge Issues
Master JFrog Bridge diagnostics to reduce downtime. Learn to isolate faults, validate tunnel health, and design resilient HA pipelines — no support ticket required.
Course Level: Intermediate
Description: Downtime in a hybrid SaaS-to-Self-Managed pipeline is costly and hard to diagnose fast.
In this course, you will learn how to distinguish Bridge issues from standard network failures, use self-service debug tools and log files to validate tunnel health, and implement High Availability architecture to prevent single points of failure.
By the end, you'll be able to resolve the most common Bridge incidents confidently and keep your global builds running without interruption.
Prerequisites:
- Completion of Getting Started with JFrog Bridge (Course 1)
- Basic understanding of hybrid JFrog Platform deployments
Topics Covered:
- Understanding the Debugging Landscape: Learn the direction filter — the Bridge only handles SaaS-to-Self-Managed traffic — and how to use that to isolate faults fast and reduce MTTR.
- Tools, Endpoints & Log Files: Use the three diagnostic layers (Platform UI, debug API endpoints, and K8s/infrastructure probes) and map the right log file (
bridge-client-service.log,bridge-client-request.log,<Service>-request.log) to each question. - Common Troubleshooting Scenarios: Walk through real on-call scenarios: a new Bridge that won't come online (firewall), TLS handshake failures (custom CA), and an ISP disconnect panic (data integrity and auto-resume).
- High Availability Architecture: Deploy multiple Bridge Clients under one Bridge ID to create a self-healing HA mesh with automatic failover — no DNS changes, no manual intervention.
- Data Integrity & Virtual Routing: Understand why disconnects only pause sync, never lose data, and why
localhost:8046in your logs is expected behavior, not a misconfiguration.
Target Audience:
- DevOps Engineers, SREs, and Platform Engineers managing JFrog hybrid environments
- Infrastructure teams responsible for JFrog SaaS-to-Self-Managed connectivity and uptime