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

Possible solution for redis connection issues... #6

Closed
vkynchev opened this issue Aug 12, 2017 · 4 comments
Closed

Possible solution for redis connection issues... #6

vkynchev opened this issue Aug 12, 2017 · 4 comments

Comments

@vkynchev
Copy link

Possible fix for people having connection problems with redis is to change Providers/Redis/RedisProvider.cs:62
from Client = new RedisClient(_config.Host, _config.Port, _config.Password, "version=2.6");
to Client = new RedisClient(_config.Host, _config.Port, _config.Password, "version=2.6,abortConnect=false,ssl=false");

@vkynchev vkynchev changed the title Possible solution for redis connection... Possible solution for redis connection... label:fix Aug 12, 2017
@vkynchev vkynchev changed the title Possible solution for redis connection... label:fix Possible solution for redis connection... Aug 12, 2017
@vkynchev vkynchev changed the title Possible solution for redis connection... Possible solution for redis connection issues... Aug 12, 2017
@vagabondan
Copy link
Owner

Hi!
What kind of redis connection issues do you expect to resolve by such changes?

@vkynchev
Copy link
Author

vkynchev commented Aug 13, 2017

I am hosting everything in docker containers and they are linked between each other with virtual network. Their IPs are dynamic, so the only way to access them is by hostname (which is set in docker-compose.yaml)...
The issue happens when I try to connect to redis' hostname(redis:6379), but if I setup port-forwarding to the main host and connect to the host IP (192.168.1.xxx:6379) it is connecting...
This is the error: It was not possible to connect to the redis server(s); to create a disconnected multiplexer, disable AbortOnConnectFail. Nothing else, no timeout or so...

BTW: I'm using latest redis image which is 4.0

@vagabondan
Copy link
Owner

Ok, thank you. I'll try it on my stand and commit then.

@vagabondan
Copy link
Owner

According to #4 (comment) the reason was bug in StackExchange v1.2.5-1.2.6.
The changes proposed do not really help to resolve the issue: they expect to get connection on multiplexer object instantiation.

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