From 7811722f7d799ec66f00b678d90ebaaf0cc7db2b Mon Sep 17 00:00:00 2001 From: ViktarStarastsenka <99594890+ViktarStarastsenka@users.noreply.github.com> Date: Wed, 8 May 2024 14:09:42 +0200 Subject: [PATCH 1/3] Update troubleshooting.md --- .../ri/using-redisinsight/troubleshooting.md | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/content/ri/using-redisinsight/troubleshooting.md b/content/ri/using-redisinsight/troubleshooting.md index 38f00d9d507..3c5b6e53e99 100644 --- a/content/ri/using-redisinsight/troubleshooting.md +++ b/content/ri/using-redisinsight/troubleshooting.md @@ -1,35 +1,35 @@ --- -Title: Troubleshooting RedisInsight -date: 2019-10-31 10:49:29 +0000 +Title: Troubleshooting Redis Insight +date: 2024-05-08 10:49:29 +0000 weight: 200 categories: ["RI"] path: troubleshooting/ nextStep: - Title: Memory Analysis + Title: Troubleshooting href: /docs/features/troubleshooting/ --- -When RedisInsight doesn't behave as expected, use these steps to see what the problem is. +When Redis Insight doesn't behave as expected, use these steps to see what the problem is. For additional configuration options, such as changing the default port, go to: https://docs.redislabs.com/latest/ri/installing/configurations/ ## Logs -To get detailed information about errors in RedisInsight, you can review the log files with the `.log` extension in: +To get detailed information about errors in Redis Insight, you can review the log files with the `.log` extension in: - **Docker**: In the `/db/` directory *inside the container*. -- **Mac**: In the `/Users//.redisinsight` directory. -- **Windows**: In the `C:\Users\\.redisinsight` directory. -- **Linux**: In the `/home//.redisinsight` directory. +- **Mac**: In the `/Users//.redis-insight` directory. +- **Windows**: In the `C:\Users\\.redis-insight` directory. +- **Linux**: In the `/home//.redis-insight` directory. {{< note >}} -You can install RedisInsight on operating systems that are not officially supported, but it may not behave as expected. +You can install Redis Insight on operating systems that are not officially supported, but it may not behave as expected. {{< /note >}} -We are happy to receive your feedback at redisinsight@redis.com. +We are happy to receive your feedback in our repository - https://github.com/RedisInsight/RedisInsight/issues. ## Using behind a reverse proxy -When you configure RedisInsight to run behind a reverse proxy like NGINX: +When you configure Redis Insight to run behind a reverse proxy like NGINX: - Since some requests can be long-running, we recommend that the **request timeout is set to over 30 seconds** on the reverse proxy. -- Hosting RedisInsight behind a prefix path (path-rewriting) is not supported at this time. +- Hosting Redis Insight behind a prefix path (path-rewriting) is not supported at this time. From c310d395cc7da589c878cd77748ae3f1f114dacf Mon Sep 17 00:00:00 2001 From: ViktarStarastsenka <99594890+ViktarStarastsenka@users.noreply.github.com> Date: Wed, 8 May 2024 14:18:15 +0200 Subject: [PATCH 2/3] Update troubleshooting.md --- content/ri/using-redisinsight/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ri/using-redisinsight/troubleshooting.md b/content/ri/using-redisinsight/troubleshooting.md index 3c5b6e53e99..2643e65483b 100644 --- a/content/ri/using-redisinsight/troubleshooting.md +++ b/content/ri/using-redisinsight/troubleshooting.md @@ -16,7 +16,7 @@ For additional configuration options, such as changing the default port, go to: To get detailed information about errors in Redis Insight, you can review the log files with the `.log` extension in: -- **Docker**: In the `/db/` directory *inside the container*. +- **Docker**: In the `/data/logs` directory *inside the container*. - **Mac**: In the `/Users//.redis-insight` directory. - **Windows**: In the `C:\Users\\.redis-insight` directory. - **Linux**: In the `/home//.redis-insight` directory. From a2ad85a97704dc72d961e14c122e67701e80fae7 Mon Sep 17 00:00:00 2001 From: ViktarStarastsenka <99594890+ViktarStarastsenka@users.noreply.github.com> Date: Wed, 8 May 2024 14:20:54 +0200 Subject: [PATCH 3/3] Update troubleshooting.md --- content/ri/using-redisinsight/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ri/using-redisinsight/troubleshooting.md b/content/ri/using-redisinsight/troubleshooting.md index 2643e65483b..57622977932 100644 --- a/content/ri/using-redisinsight/troubleshooting.md +++ b/content/ri/using-redisinsight/troubleshooting.md @@ -31,5 +31,5 @@ We are happy to receive your feedback in our repository - https://github.com/Red When you configure Redis Insight to run behind a reverse proxy like NGINX: -- Since some requests can be long-running, we recommend that the **request timeout is set to over 30 seconds** on the reverse proxy. +- Since some requests can be long-running, we recommend that the **request timeout is set to over 30 seconds** on the reverse proxy. Redis Insight also allows to manage its connection timeout (30 seconds by default) on the form to manage the connection details, remember to change it accordingly. - Hosting Redis Insight behind a prefix path (path-rewriting) is not supported at this time.