Published app works internally but external redirect loop persists
Scenario
An app works internally, but external users are caught in repeated redirects when browsing through the firewall or proxy.
Static route added but traceroute still follows default path
Scenario
An admin adds a static route for a new subnet, yet client traffic continues using the default route.
Geo block enabled but approved vendor traffic also blocked
Scenario
A geo-blocking policy reduced noise, but it also broke a vendor integration that legitimately originates from blocked regions.
Application publish rule works by IP not FQDN
Scenario
External access to a published application succeeds with the public IP, but fails when users browse the normal hostname.
- Read more about Application publish rule works by IP not FQDN
- Log in to post comments
New ISP circuit installed but outbound policy still uses old WAN
Scenario
A second internet circuit is live, but business traffic never takes the expected path after cutover.
Firewall HA pair syncs config but not session state
Scenario
A failover cluster shows synchronized configuration, but active sessions drop whenever a failover occurs.
Site to site tunnel up but only one subnet passes traffic
Scenario
A site-to-site VPN reports healthy, but devices on one subnet cannot communicate while others work.
Router rebooted and static routes disappeared
Scenario
After a power event or manual reboot, traffic between sites fails because manually added routes are gone.
- Read more about Router rebooted and static routes disappeared
- Log in to post comments
Firewall rules present but traffic still blocked
Scenario
Rules exist on the firewall, but app traffic still fails between two networks.