Connecting Users receive Error, "Connection Refused" after Enabling HTTP Redirect in SGD Gateway
(Doc ID 2437384.1)
Last updated on FEBRUARY 12, 2025
Applies to:
Oracle Secure Global Desktop - Version 5.4 and laterInformation in this document applies to any platform.
Symptoms
After successful configuration and testing of a Secure Global Desktop Gateway environment, the SGD Administrator may elect to enable the optional HTTP redirect feature. This functionality is intended to automatically redirect users connecting on a non-secure port (80) to a secure, HTTPS connection on (443).
Though the 'gateway config enable --routes-http-redirect' command ran successfully and the SGD Gateway was restarted as instructed, the SGD Administrator reported that users attempting a connection on the standard HTTP port were presented with a variation of a "Connection Refused" message.
Note: Content of this message may vary, depending on the browser, or Proxies that are involved in the test attempt.
There are no records of the failed connection attempt written to the SGD Gateway or SGD Server logs.
Changes
The SGD Administrator enabled HTTP Redirection using the procedure documented in the SGD Gateway Admin guide, using the following command:
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Troubleshooting |
Solution |