![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/RGDOCKER5-1024x387.png\")
<\/figure>\n\n\n\n- \n
- Check if plugin is here <\/li>\n<\/ul>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/RGDOCKER6-1024x397.png\")
<\/figure>\n\n\n\n- \n
- As you see, plugin is here and installed<\/li>\n<\/ul>\n\n\n\n
- \n
- Check the plugin version ( in case you are not able to debug it it may be useful for Redis support team )<\/li>\n<\/ul>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/RGDOCKER7-1024x460.png\")
<\/figure>\n\n\n\nNow you have the plugin version and also its compatibility with the Grafana version<\/p>\n\n\n\n
( in our example it is compatible with Grafana versions > +8.0.0 )<\/p>\n\n\n\n
If all is fine at this level, we can now focus on the different error messages related to Redis instance.<\/p>\n\n\n\n
Fix getInstance error: connection refused<\/h2>\n\n\n\n
When you connect to Grafana, you have to define the Redis database:<\/p>\n\n\n\n
- \n
- Go to Home Connections=>Data sources<\/li>\n<\/ul>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/RGDOCKER12-1024x369.png\")
<\/figure>\n\n\n\n- \n
- When adding all your database details and you click on “save and test” button, your can face the famous issue<\/li>\n<\/ul>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/RGDOCKER_1st_issue_ip-1024x439.png\")
<\/figure>\n\n\n\nFor this specific case it can simply due to the fact that your Redis database is not up!<\/p>\n\n\n\n
So check that in priority.<\/p>\n\n\n\n
- \n
- If it is not UP, then start it and retry the “Save and test” option<\/li>\n<\/ul>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/RGDOCKER20debugredisstart-1024x496.png\")
<\/figure>\n\n\n\n- \n
- Use the redis-server command or start the Redis service using systemd on your Redis server:<\/li>\n<\/ul>\n\n\n\n
nso@DBI-LT-NSO:~> redis-server<\/code><\/pre>\n\n\n\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/image-6-1024x556.png\")
<\/figure>\n\n\n\nExample on Linux:<\/span><\/p>\n\n\n\n
sudo systemctl start redis.service<\/code><\/pre>\n\n\n\n- \n
- If you are in that specific case it should work fine now \ud83d\ude42<\/li>\n<\/ul>\n\n\n\n
- \n
- The second case can be because your address is not correctly set or not recognized<\/li>\n<\/ul>\n\n\n\n
Below my local host name didn’t worked:<\/p>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/image-7.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/image-8-1024x370.png\")
<\/figure>\n\n\n\n- \n
- So for those using a Docker image like me we must add the docker host IP address instead.<\/li>\n<\/ul>\n\n\n\n
Get the docker host IP Address <\/h2>\n\n\n\n
To get the docker ip address use the following commands:<\/p>\n\n\n\n
docker inspect <containerNameOrId><\/code><\/pre>\n\n\n\nExample:<\/span><\/p>\n\n\n\n
C:\\WINDOWS\\system32>docker inspect <\/code><\/pre>\n\n\n\n8c6c36853ab0490ecca607a6aa28bd158f8f798fd221c24f973faf33be7dfb23<\/code><\/pre>\n\n\n\nYou can then pick the Docker ip address<\/p>\n\n\n\n
Here in my example it is 172.17.0.2<\/p>\n\n\n\n
“Usually, the default docker ip range is
172.17.0.0\/16<\/code>. <\/p>\n\n\n\nYour host should be
172.17.0.1<\/code> and your first container should be172.17.0.2<\/code> if everything is normal and you didn’t specify any special network options.”<\/p>\n\n\n\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/image-9-1024x182.png\")
<\/figure>\n\n\n\n- \n
- Let’s try now:<\/li>\n<\/ul>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/image-10-1024x452.png\")
<\/figure>\n\n\n\n- \n
- If it is still not working with Docker IP address you picked by using the docker inspect command, use the following syntax:<\/li>\n<\/ul>\n\n\n\n
host.docker.internal: <your_Redis_port><\/code><\/pre>\n\n\n\nExample:<\/span><\/p>\n\n\n\n
host.docker.internal: 6379<\/code><\/pre>\n\n\n\n![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/image-12-1024x410.png\")
<\/figure>\n\n\n\nIt should work now!<\/p>\n\n\n\n
Fix getInstance error : ERR AUTH<\/h2>\n\n\n\n
This “error” message will display when you have not configured the default password user.<\/p>\n\n\n\n
- \n
- So you know what to do as the error message is explicit ( check your configuration )<\/li>\n<\/ul>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/image-3-1024x417.png\")
<\/figure>\n\n\n\n- \n
- Anyway, If you let the password part empty (click reset and remove the password) you can test with success<\/li>\n<\/ul>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/image-4-1024x189.png\")
<\/figure>\n\n\n\nFix getInstance error : DENIED<\/h2>\n\n\n\n
- \n
- This specific message is more verbose,it propose you solution to fix it such as:<\/li>\n<\/ul>\n\n\n\n
a)disable the protected mode by many ways<\/p>\n\n\n\n
b)setup a bind address or authentication by password<\/p>\n\n\n\n
- \n
- Here are the different ways to disable the protected mode:<\/li>\n<\/ul>\n\n\n\n
“DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions:<\/p>\n\n\n\n
1) Just disable protected mode sending the command “CONFIG SET protected-mode no” from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent.<\/p>\n\n\n\n
2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to ‘no’, and then restarting the server.<\/p>\n\n\n\n
Go to your redis.cfg file and update the below line and set it to “no”<\/p>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/image-5.png\")
<\/figure>\n\n\n\n3) If you started the server manually just for testing, restart it with the ‘–protected-mode no<\/strong>‘ option.<\/p>\n\n\n\n
4) Setup a bind address or an authentication password.<\/p>\n\n\n\n
Of course : You only need to do one of the above things<\/strong> in order for the server to start accepting connections from the outside.<\/p>\n\n\n\n
From Redis site<\/em><\/p>\n\n\n\n
Example:<\/span><\/p>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/RGDOCKER9-1024x463.png\")
<\/figure>\n\n\n\n- \n
- For our case we will disable protected mode as it is only for test purpose.<\/li>\n<\/ul>\n\n\n\n
- \n
- Use the below command on your Redis instance: <\/li>\n<\/ul>\n\n\n\n
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2023\/11\/RGDOCKER10.png\")
<\/figure>\n\n\n\n- \n
- Now you can use the save and test option it should work<\/li>\n<\/ul>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
Now you know how to fix the main issues when defining your Redis instance in Grafana.<\/p>\n\n\n\n
If you are still stuck, you can also check on Grafana official site<\/a> database you can find some useful info.<\/p>\n\n\n\n
- Now you can use the save and test option it should work<\/li>\n<\/ul>\n\n\n\n
- Use the below command on your Redis instance: <\/li>\n<\/ul>\n\n\n\n
- For our case we will disable protected mode as it is only for test purpose.<\/li>\n<\/ul>\n\n\n\n
- Here are the different ways to disable the protected mode:<\/li>\n<\/ul>\n\n\n\n
- This specific message is more verbose,it propose you solution to fix it such as:<\/li>\n<\/ul>\n\n\n\n
- Anyway, If you let the password part empty (click reset and remove the password) you can test with success<\/li>\n<\/ul>\n\n\n\n
- So you know what to do as the error message is explicit ( check your configuration )<\/li>\n<\/ul>\n\n\n\n
- If it is still not working with Docker IP address you picked by using the docker inspect command, use the following syntax:<\/li>\n<\/ul>\n\n\n\n
- Let’s try now:<\/li>\n<\/ul>\n\n\n\n
- So for those using a Docker image like me we must add the docker host IP address instead.<\/li>\n<\/ul>\n\n\n\n
- The second case can be because your address is not correctly set or not recognized<\/li>\n<\/ul>\n\n\n\n
- If you are in that specific case it should work fine now \ud83d\ude42<\/li>\n<\/ul>\n\n\n\n
- Use the redis-server command or start the Redis service using systemd on your Redis server:<\/li>\n<\/ul>\n\n\n\n
- If it is not UP, then start it and retry the “Save and test” option<\/li>\n<\/ul>\n\n\n\n
- When adding all your database details and you click on “save and test” button, your can face the famous issue<\/li>\n<\/ul>\n\n\n\n
- Go to Home Connections=>Data sources<\/li>\n<\/ul>\n\n\n\n
- Check the plugin version ( in case you are not able to debug it it may be useful for Redis support team )<\/li>\n<\/ul>\n\n\n\n
- As you see, plugin is here and installed<\/li>\n<\/ul>\n\n\n\n