Community
Custom Server Security with Host behind HTTP proxy
Links used in this discussion
Links used in this discussion
- https://www.remoteutilities.com/support/forums/forum1/1899-custom-server-security-authentication-error
- https://www.remoteutilities.com/support/docs/setting-up-relay-server/#Additional_protection_with_a_PIN_code
- https://www.remoteutilities.com/support/docs/setting-up-auth-server/#Step_1_Create_users_and_groups
- https://www.remoteutilities.com/download/
- https://www.remoteutilities.com/support/docs/registering-the-program/#Register_RU_Server
Edmond So,
User (Posts: 4)
Jan 19, 2022 5:32:34 am EST
Support level: Starter
We are able to use our self-hosted RU server for custom server security.
However, some of our hosts at our customer's site are behind a HTTP proxy. We are able to connect to them from our viewers through our self-hosted server, when security is set to single password, so the relay function is functioning properly.
When we change the security to custom server security, the viewer gives a "Custom Server Security Authentication Error" message.
The host log shows "Error TMyOpenSSLSocket.ReadStream. (EMyOpenSSLException)。"
Symptoms are similar to this post in the forum
Also, on the host, when we bring up the "Settings for Host" window, and click on "Users and access control" under the Authentication tab, it is not able to connect to our self-hosted server.
Is this configuration supported?
We have tried the latest host and viewer version (v7.1.2.0)
However, some of our hosts at our customer's site are behind a HTTP proxy. We are able to connect to them from our viewers through our self-hosted server, when security is set to single password, so the relay function is functioning properly.
When we change the security to custom server security, the viewer gives a "Custom Server Security Authentication Error" message.
The host log shows "Error TMyOpenSSLSocket.ReadStream. (EMyOpenSSLException)。"
Symptoms are similar to this post in the forum
Also, on the host, when we bring up the "Settings for Host" window, and click on "Users and access control" under the Authentication tab, it is not able to connect to our self-hosted server.
Is this configuration supported?
We have tried the latest host and viewer version (v7.1.2.0)
Pauline,
Support (Posts: 2870)
Jan 19, 2022 9:46:36 am EST
Hello Edmond,
Thank you for your message.
Could you please double-check the following:
1. Do you have the PIN code feature enabled in the RU Server's Configuration window -> Communication tab?
2. Does the user you use to sign in to the Server have the Active checkbox enabled in the user's settings on the Server side?
3. Do you have the Force custom server security checkbox enabled in the user's settings on the Server side?
4. In addition, please make sure that your RU Server is updated to the latest version 3.2.1.0 which is available for download on this page and is registered with the corresponding license key as described here.
Please let us know if the issue persists.
Thank you for your message.
Could you please double-check the following:
1. Do you have the PIN code feature enabled in the RU Server's Configuration window -> Communication tab?
2. Does the user you use to sign in to the Server have the Active checkbox enabled in the user's settings on the Server side?
3. Do you have the Force custom server security checkbox enabled in the user's settings on the Server side?
4. In addition, please make sure that your RU Server is updated to the latest version 3.2.1.0 which is available for download on this page and is registered with the corresponding license key as described here.
Please let us know if the issue persists.
* Website time zone: America/New_York (UTC -5)