Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to access Redb instance using Redis Insights ( OpenShift) #244

Open
ajaykanse opened this issue Sep 29, 2022 · 2 comments
Open

Unable to access Redb instance using Redis Insights ( OpenShift) #244

ajaykanse opened this issue Sep 29, 2022 · 2 comments

Comments

@ajaykanse
Copy link

I have 1 node Redis Enterprise Cluster with 1 database. I have redis ui up using route and database is showing up there. Developers have a requirement to connect to the database using local instance of Redis insight. I tried multiple ways i.e using hostname as route, port as 6443, user default and password from database secret, Enabled SNI and tried to use proxy certificate from Redis UI console. Nothing worked. Database route is secured as passthrough and insecure traffic as none.
Not sure what is going on? The cluster is running on AWS.

Expected outcome - Redis Insight should be able to connect to Redb Database running in OpenShift.
Thanks

@laurentdroin
Copy link
Contributor

Hi,

The hostname will need to be a name that resolves to the IP address of the external load balancer in front of your ingress controller. Since you're using Openshift, the hostname in the route will typically be the value to use.
The port will be 443.
You will need to use SNI, and the SNI value (server name) to use will be the hostname in the route.
Also, you need to make sure TLS is enabled on the database.

If this does not help, kindly open a support ticket with Redis.

Laurent.

@ajaykanse
Copy link
Author

Thanks I have done all mentioned above. I'll open ticket with Redis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants