-
Notifications
You must be signed in to change notification settings - Fork 325
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
[v2.1.3] Unable to connect to Redis Resource in Azure #425
Comments
I got the same probleme here ! |
Btw it was actually broken before as they were evaluated at the wrong time in the wrong way. So you may have inadvertently been using this feature 'wrong' but accidentally made it work that way. If either of you can provide a bit more insight on how you configured things we can nail this down quickly hopefully. |
I tried to look into it without success. I will definitely need more information from @javiermadueno and/or @monsieurchico (stack trace, config, etc.). |
Hello @B-Galati, this is the Exceptiontion trace: (I've replaced the redis URL for
|
@javiermadueno Thank you, could you also give us your config? And how Without that it's gonna be quite hard to help. thanks again. |
@monsieurchico Could you also provide more information please ? |
Hello, I have the same problem in v2.1.3, my configuration is the following :
I got the same error than javierdansmuero and it diseapear if I reverted the package back to v2.1.2 |
I reproduced the issue and it looks like the previous behavior was a bug. Anyway it's a BC break so I guess we should fix it. The quick fix I identified is the following: given @Kalliser's example, |
My bad. It looks like a bug on Predis project looks quite dead these days so I guess we should do a fix on our side no ? |
fix snc#425 - Always use PredisParametersFactory to build connection options so that it creates consistency between env/non-env based config
fix snc#425 - Always use PredisParametersFactory to build connection options so that it creates consistency between env/non-env based config - Use RedisDsn to parse redis DSN instead of \Predis\Connection\Parameters::parse(). It creates consistence between phpredis and predis behavior.
fix snc#425 - Always use PredisParametersFactory to build connection options so that it creates consistency between env/non-env based config - Use RedisDsn to parse redis DSN instead of \Predis\Connection\Parameters::parse(). It creates consistence between phpredis and predis behavior.
fix snc#425 - Always use PredisParametersFactory to build connection options so that it creates consistency between env/non-env based config - Use RedisDsn to parse redis DSN instead of \Predis\Connection\Parameters::parse(). It creates consistence between phpredis and predis behavior.
fix #425 - Always use PredisParametersFactory to build connection options so that it creates consistency between env/non-env based config - Use RedisDsn to parse redis DSN instead of \Predis\Connection\Parameters::parse(). It creates consistence between phpredis and predis behavior.
This should be fixed in 2.1.4, can you confirm? |
If anyone should stumble upon this issue... I sure hope this will help someone save time. I had the same problem today and I was going nuts. Then, I used the secondary key just to be sure I tried everything, and it worked! object(Snc\RedisBundle\DependencyInjection\Configuration\RedisDsn)[1762]
protected 'dsn' => string 'rediss://redacted+key=@cache:6380' (length=83)
protected 'password' => string 'redacted key=' (length=44)
protected 'host' => string 'cache' (length=5)
protected 'port' => int 6380
protected 'socket' => null
protected 'tls' => boolean true
protected 'database' => null
protected 'weight' => null
protected 'alias' => null |
What about adding this to the docs ? |
Has been there since 2016 actually 😉 |
Well, yeah... 🤣 Thanks @curry684 |
Yeah I know, it's one of those classic "oh DUH" moments that I'm not sure we can do anything to alleviate. Best thing I could think of indeed was doing the Symfony DX thing and extend the access denied exception with some remarks about this. Theoretically we could even only do it when auth is denied and |
nice idea 👍 |
Hello,
Yesterday I updated the Bundle in my Azure webapp and it seems there is a problem with the last version changes. It's unable to connect to the Redis Resource in Azure showing this message:
predis SELECT failed: NOAUTH Authentication required.
The
REDIS_URL
is well defined and installing the version2.1.2
it works properly.Kind regards.
The text was updated successfully, but these errors were encountered: