A 502 Bad Gateway error typically indicates a problem between a client and a server, frequently involving a reverse proxy. If the option below is helpful, please select it.
- Make sure your Exchange Server 2019 is healthy and operational.
- ARR Configuration - Correct the server address, ports, and other settings.
- Examine the IIS logs on your Exchange 2019 server for the requests that caused the 502 error.
- TLS/SSL Protocols and Cypher Suites - Examine the TLS/SSL protocols and cipher suites configured in ARR and Exchange 2019. Maintain compatibility and consistency.
- Check the application pool settings for Exchange in IIS. Make sure it's using the correct .NET version and other settings.