Firewalls & Routing Troubleshooting

Minimal guidance for messy support realities.
Networking

Firewalls & Routing Troubleshooting

Browse issue-specific guidance for Firewalls & Routing.

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