Unable to use outbound proxy configuration with Mirror on initial setup

Summary

If the primary server is configured to use an outbound connection via setenv.sh, then the user is unable to connect the Primary server.

Steps to Reproduce

1. Shutdown Primary server
2. Configure outbound proxy. (Use host or IP)
3. Start Primary server.
4. Install and configure Mirror.
5. Enter the Primary server URL on Mirror Setup screen

Expected Results

The Mirror will connect successfully to the Primary server.

Actual Results

Receives error message preventing the Mirror from connecting to the Primary.

• "Primary server does not appear to be a Bitbucket server."
• "SSLHandshakeException: General SSLEngine problem"

Additional Steps to Reproduce

1. Shutdown Mirror server
2. Configure outbound proxy. (Use host or IP)
3. Start Mirror server.
4. Approve Mirror on Primary server

Expected Results

The Mirror will connect successfully to the Primary server.

Actual Results

Receives error message preventing the Mirror from connecting to the Primary.

• "Primary server does not appear to be a Bitbucket server."
• "SSLHandshakeException: General SSLEngine problem"

Workaround

1. No workaround if additional steps are performed. The error seems to be cached. Even if you remove the setenv.sh settings for the Mirror and restart both nodes, the error persists.

Notes

-Dhttp.proxyHost=proxy.internal.marku.local -Dhttp.proxyPort=80 -Dhttps.proxyHost=proxy.internal.marku.local -Dhttps.proxyPort=80 -Dhttp.nonProxyHosts=localhost 

SSLHandshake error - Successful SSLPokes were performed between all nodes and F5.