-
-
Notifications
You must be signed in to change notification settings - Fork 285
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
ssl_cert_reqs seems to not work #674
Comments
This is a pretty urgent issue for heroku deployments. I was able to get it working by throwing a whole lot of guesses together, not sure which of these things in particular fixed the issue, but it was urgent, so I tried a whole lot at once.
Altogether it looks something like this:
I'm not sure the last 2 are required you probably just need to use the REDIS_TLS_URL, but I thought I'd throw them in just to see if they would stick as this was urgent for us. I also wanted to make sure that I posted this in case you or anyone else is still having this issue. |
The documentation likely needs a small revision. We need to update the RQ_QUEUES setting in settings.py. The documentation suggests the addition of 'REDIS_CLIENT_KWARGS':
But actually, in version 2.10.2 the config key needed is "SSL_CERT_REQS":
resulting in:
On the published app, Heroku sets both the environment variables REDIS_TLS_URL and REDIS_URL to the same value, so no update to settings is immediately required there, though going forward it's likely best to ensure Heroku users see also: |
@onAutopylot thank you! |
I have:
I have checked:
>>> settings.RQ_QUEUES {'default': {'DEFAULT_TIMEOUT': 3600, 'URL': 'rediss://:secret@esecret:11640', 'REDIS_CLIENT_KWARGS': {'ssl_cert_reqs': None}}}
But when I try to queue an email I get a traceback:
I have my Django cache set up in the same way:
And I confirmed this is working properly:
The text was updated successfully, but these errors were encountered: