Source note · Troubleshooting Expressway Mobile and Remote Access
A 502 Next Hop Connection Failed on Expressway-E usually points to the connection to Expressway-C; check SSH tunnel status from Status > Unified Communications.
Checked 2026-10-01
- Vendor
- Cisco
- Product
- Cisco Expressway
- Subsystem
- ssh-tunnels
- Deployment
- on-premises
- Region
- not restricted
- Release range
- X15.2 documentation
- Checked
- 2026-10-01
Sources
- Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Troubleshooting — Cisco Systems · tier 2 current vendor documentation · Specific Issues > Expressway returns 502 Next hop connection failed
Cite this note
APA
WarmTransfer. (2026, October 1). Troubleshooting Expressway Mobile and Remote Access: source note expressway-mra-troubleshooting-next-hop-502-ssh. WarmTransfer. https://warmtransfer.net/knowledge/claims/expressway-mra-troubleshooting-next-hop-502-ssh
BibTeX
@misc{warmtransfer-claim-expressway-mra-troubleshooting-next-hop-502-ssh,
title = {Troubleshooting Expressway Mobile and Remote Access: source note expressway-mra-troubleshooting-next-hop-502-ssh},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/expressway-mra-troubleshooting-next-hop-502-ssh},
note = {Source note expressway-mra-troubleshooting-next-hop-502-ssh, checked 2026-10-01}
}