Networking
Firewalls & Routing Troubleshooting
Browse issue-specific guidance for Firewalls & Routing.
- Application publish rule works by IP not FQDN
- Edge firewall firmware upgrade resets one custom application rule
- Firewall geo-block policy stops vendor access from approved country range
- Firewall HA pair stays synchronized but secondary fails takeover test
- Firewall HA pair syncs config but not session state
- Firewall rules present but traffic still blocked
- Firewalls & Routing alerts indicate success while end-user experience never changes
- Firewalls & Routing configuration survives testing but resets after restart or sync
- Firewalls & Routing connector health looks normal but data stops syncing
- Firewalls & Routing credential or certificate rotation breaks an existing integration
- Firewalls & Routing feature works in web app but fails in desktop client
- Firewalls & Routing healthy dashboard status masks a failing production workflow
- Firewalls & Routing logging shows delivery yet the target workflow never completes
- Firewalls & Routing new deployment works for pilot group but not for production rollout
- Firewalls & Routing policy change applies in admin console but target users never receive it
- Firewalls & Routing quarantine or protection action triggers but recovery workflow fails
- Firewalls & Routing workflow succeeds for one account but fails for shared or delegated access
- Geo block enabled but approved vendor traffic also blocked
- Inter-VLAN routing works for ping but not for HTTPS sessions
- New ISP circuit installed but outbound policy still uses old WAN
- Outbound SMTP relay blocked because egress policy matches wrong object group
- Port forward works externally but internal hairpin access fails
- Published app works internally but external redirect loop persists
- Route-based tunnel carries traffic one way only after ISP failover
- Router rebooted and static routes disappeared
- Site to site tunnel up but only one subnet passes traffic
- Site-to-site VPN tunnel shows up but traffic returns through wrong route
- Static NAT entry published correctly yet source IP logging shows proxy address
- Static route added but traceroute still follows default path
- Web filter category update blocks line-of-business app download endpoint