login/pwd issue

[TJarriault]

Hi, When i try to start "docker-compose up" with environment variable, the login not works.

• HTTP_USER=login
• HTTP_PASSWORD=password

The web IHM always ask login and pasword.

Regards

[sseide]

For us its working without problem on kubernetes. Setting "env" variables at kubernetes container spec for "HTTP_USER" and "HTTP_PASSWORD".

Accessing it the first time the web asks for user/password, I enter the one set via the environment variables and get access. We are using Firefox and Chromium-based Browsers.

Is working with all the last versions from github for us.

[sseide]

How do you installed redis-commander? github? npm?

[TJarriault]

Hi,

I use the guide line : https://hub.docker.com/r/rediscommander/redis-commander/

When I try to authenticate, the authentication window reappears in a loop

[cid:image001.png@01D4559E.33758300]

I launch the solution througth docker-compose.yml file like this : version: '3' services: redis-commander: container_name: redis-commander hostname: redis-commander image: rediscommander/redis-commander:latest

build: .

restart: always
environment:
- REDIS_HOSTS=local:redis:6379
- HTTP_USER=test
- HTTP_PASSWORD=test
ports:
- "8081:8081"

Regards,

Tony

De : sseide notifications@github.com Envoyé : mercredi 26 septembre 2018 11:12 À : joeferner/redis-commander Cc : JARRIAULT, Tony; Author Objet : Re: [joeferner/redis-commander] login/pwd issue (#290)

How do you installed redis-commander? github? npm?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/joeferner/redis-commander/issues/290#issuecomment-424643594, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHWDhi4O0u1EMYz1wuAIVoV90S7qTD6nks5ue0THgaJpZM4W3a4n. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

[sseide]

works for me - started via docker-compose up, docker downloaded latest image and started it.

Recreating redis_redis-commander_1
Attaching to redis-commander
redis-commander    | Creating custom redis-commander config.
redis-commander    | Configuration:
redis-commander    |     {
redis-commander    |     "sidebarWidth":250,
redis-commander    |     "locked":false,
redis-commander    |     "CLIHeight":50,
redis-commander    |     "CLIOpen":false,
redis-commander    |     "default_connections": [
redis-commander    |         {
redis-commander    |             "label":"local",
redis-commander    |             "host":"127.0.0.1",
redis-commander    |             "port":"6379",
redis-commander    |             "password":"",
redis-commander    |             "dbIndex":0
redis-commander    |         }
redis-commander    |         ]
redis-commander    |     }
redis-commander    | node ./bin/redis-commander --http-u test --http-p test
redis-commander    | No Save: false
redis-commander    | listening on  0.0.0.0 : 8081
redis-commander    | Redis Connection 127.0.0.1:6379 Using Redis DB #0

Now opened browser (chromium) and logged in with test / test...

redis-commander    | Login success for user test from remote ip 127.0.0.1
redis-commander    | loading keys by prefix ""
redis-commander    | found 28 keys for ""

After starting - does redis commander show a success on connection to redis? "Redis Connection..."?

Do you use an old image? Try deleting the current one from docker.

[TJarriault]

Hi, I delete all images and container, before my tests. I’ve got the same authentication issue.

You can find bellow some traces and screen shot. The operating system on the server : Linux serverless2 3.13.0-107-generic #154-Ubuntu SMP Tue Dec 20 09:57:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[cid:image002.png@01D455AD.B591EE50]

[cid:image012.jpg@01D455AD.D5511130]

Cordialement,

Tony Jarriault

[Prosodie-signature]http://www.prosodie.com/

Tony JARRIAULT – Service & Operations / Industrial Management PROSODIE - Division Front Office Platform Tél. : +33 (0)1.34.49.06.43 / +33 (0)6.23.05.02.22 Fax : +33 (0)1.34.49.06.79 tjarriault@prosodie.commailto:tjarriault@prosodie.com

8, rue Grange Dame Rose - 78457 Velizy-Villacoublay Cedex P afin de contribuer au respect de l'environnement, merci de n'imprimer ce mail qu'en cas de nécessité

---

Connect with Prosodie : [cid:image002.gif@01CFDEF6.5E892100]https://twitter.com/ProsodieCap [cid:image003.gif@01CFDCA5.6607B750] https://www.linkedin.com/company/prosodie?report.success=6vo3TCkCS1-Q3MQSXyAa5EmbyooXt_JHF4gI-SlS5O9Glwt8CaN1ZzdSFMOjqCEC4tgoZJl1pOO90MRDlW9NQp [cid:image004.gif@01CFDEF6.5E892100] https://www.youtube.com/user/ProsodieSA [cid:image005.gif@01CFDEF6.5E892100] https://www.facebook.com/pages/Prosodie/171904106158263?notif_t=page_user_activity [cid:image006.gif@01CFDEF6.5E892100] http://fr.slideshare.net/Prosodie-Capgemini?utm_campaign=profiletracking&utm_medium=sssite&utm_source=ssusersearch&qid=fd27adae-f2f8-4656-969d-b416c23d089f&v=default&b=&from_search=2 [cid:image007.gif@01CFDEF6.5E892100] http://www.prosodie.fr/blog/ [cid:image009.png@01CFDEFA.8C37C850] https://plus.google.com/107107861875955781503/posts

[signature mail Gartner FR]https://www.prosodie.com/fr/gartner-magic-quadrant-etude-contact-center-service-ccaas/

De : sseide notifications@github.com Envoyé : mercredi 26 septembre 2018 15:02 À : joeferner/redis-commander Cc : JARRIAULT, Tony; Author Objet : Re: [joeferner/redis-commander] login/pwd issue (#290)

works for me - started via docker-compose up, docker downloaded latest image and started it.

Recreating redis_redis-commander_1

Attaching to redis-commander

redis-commander | Creating custom redis-commander config.

redis-commander | Configuration:

redis-commander | {

redis-commander | "sidebarWidth":250,

redis-commander | "locked":false,

redis-commander | "CLIHeight":50,

redis-commander | "CLIOpen":false,

redis-commander | "default_connections": [

redis-commander | {

redis-commander | "label":"local",

redis-commander | "host":"127.0.0.1",

redis-commander | "port":"6379",

redis-commander | "password":"",

redis-commander | "dbIndex":0

redis-commander | }

redis-commander | ]

redis-commander | }

redis-commander | node ./bin/redis-commander --http-u test --http-p test

redis-commander | No Save: false

redis-commander | listening on 0.0.0.0 : 8081

redis-commander | Redis Connection 127.0.0.1:6379 Using Redis DB #0

Now opened browser (chromium) and logged in with test / test...

redis-commander | Login success for user test from remote ip 127.0.0.1

redis-commander | loading keys by prefix ""

redis-commander | found 28 keys for ""

After starting - does redis commander show a success on connection to redis? "Redis Connection..."?

Do you use an old image? Try deleting the current one from docker.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/joeferner/redis-commander/issues/290#issuecomment-424706450, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHWDhoDikIjj02wF9yLHGgsyVa35L6hnks5ue3rRgaJpZM4W3a4n. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

root@serverless2:/appli/github/aws-tools-DEV4/templates/ac-05-bo# docker logs -f c47b0502bfcb 1:C 26 Sep 13:10:40.961 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1:C 26 Sep 13:10:40.961 # Redis version=4.0.11, bits=64, commit=00000000, modified=0, pid=1, just started 1:C 26 Sep 13:10:40.961 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf 1:M 26 Sep 13:10:40.962 Running mode=standalone, port=6379. 1:M 26 Sep 13:10:40.962 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128. 1:M 26 Sep 13:10:40.962 # Server initialized 1:M 26 Sep 13:10:40.962 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. 1:M 26 Sep 13:10:40.962 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled. 1:M 26 Sep 13:10:40.962 Ready to accept connections 1:signal-handler (1537967576) Received SIGTERM scheduling shutdown... 1:M 26 Sep 13:12:56.216 # User requested shutdown... 1:M 26 Sep 13:12:56.216 Saving the final RDB snapshot before exiting. 1:M 26 Sep 13:12:56.218 DB saved on disk 1:M 26 Sep 13:12:56.218 # Redis is now ready to exit, bye bye... 1:C 26 Sep 13:13:15.365 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1:C 26 Sep 13:13:15.369 # Redis version=4.0.11, bits=64, commit=00000000, modified=0, pid=1, just started 1:C 26 Sep 13:13:15.369 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf 1:M 26 Sep 13:13:15.370 Running mode=standalone, port=6379. 1:M 26 Sep 13:13:15.370 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128. 1:M 26 Sep 13:13:15.370 # Server initialized 1:M 26 Sep 13:13:15.370 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. 1:M 26 Sep 13:13:15.370 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled. 1:M 26 Sep 13:13:15.370 DB loaded from disk: 0.000 seconds 1:M 26 Sep 13:13:15.370 * Ready to accept connections

[sseide]

Github removed all images from your mail...

[TJarriault]

docker-compose.yml.txt

](url) traces.txt

[sseide]

used your docker-compose yml and started booth container (redis-db + redis-commander) - login with test / test works for me without problem. Output does not show any problems. Seems to be an client (read: browser) problem than.

The traces.txt only contains output from redis database, not redis commander.

[sseide]

found something with windows based browsers - seem to behave a little bit different. Can you please retry with latest docker image?

[sseide]

This problem should be fixed in current version. If you think its not feel free to reopen issue with updated informations based on latest version.