Closed hazi closed 4 years ago
I do not see where it switches to the TLS/SSL mode... (rediss is for encrypted communication). Also, the URL should be rediss://<user>:<token>@<hostname>:<port>/<db number>
where user is entirely optional, but token is quite important. Same for the redis scheme.
~~Sorry, but it was an inappropriate explanation. I'm using a Google translate, so it might be poorly explained.~~
~~The argument URL is passed as it is to Redis::Dump
.
The URL is also used for Redis.new, and Redis works because it supports rediss://
.
This change removed the process of disabling rediss://
.~~
The actual connection test is performed in this way.
$ bin/redis-dump -u "redis://:password@example.com:6379" -D
#1000000000.0000: redis_uri: redis://:password@example.com:6379 (0..15)
#1000000000.0000: Process: 21016; Memory: 20964
#1000000000.0000: CONNECT: redis://:password@example.com:6379/0
#1000000000.0000: CONNECT: redis://:password@example.com:6379/1
#1000000000.0000: CONNECT: redis://:password@example.com:6379/2
#1000000000.0000: CONNECT: redis://:password@example.com:6379/3
#1000000000.0000: CONNECT: redis://:password@example.com:6379/4
#1000000000.0000: CONNECT: redis://:password@example.com:6379/5
#1000000000.0000: CONNECT: redis://:password@example.com:6379/6
#1000000000.0000: CONNECT: redis://:password@example.com:6379/7
#1000000000.0000: CONNECT: redis://:password@example.com:6379/8
#1000000000.0000: CONNECT: redis://:password@example.com:6379/9
#1000000000.0000: CONNECT: redis://:password@example.com:6379/10
#1000000000.0000: CONNECT: redis://:password@example.com:6379/11
#1000000000.0000: CONNECT: redis://:password@example.com:6379/12
#1000000000.0000: CONNECT: redis://:password@example.com:6379/13
#1000000000.0000: CONNECT: redis://:password@example.com:6379/14
#1000000000.0000: CONNECT: redis://:password@example.com:6379/15
#1000000000.0000: filter
Connection timed out
$ bin/redis-dump -u "rediss://:password@example.com:6379" -D
#1000000000.0000: redis_uri: rediss://:password@example.com:6379 (0..15)
#1000000000.0000: Process: 21042; Memory: 20548
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/0
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/1
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/2
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/3
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/4
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/5
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/6
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/7
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/8
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/9
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/10
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/11
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/12
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/13
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/14
#1000000000.0000: CONNECT: rediss://:password@example.com:6379/15
#1000000000.0000: filter
#1000000000.0000: Memory after loading keys: 20000kb
#1000000000.0000: dumping 947 (947) from redis://example.com:6379/0
^C
Exiting...
excuse me.
I was misunderstanding.
This change was completely meaningless and originally corresponded to rediss://
.
Solve the error below