Replies: 1 comment
-
I honestly don't know. If the encryption in transit option that you enabled just means that the Redis server uses SSL, then you should be able to connect to it using a |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I use Flask-SocketIO in AWS inside of ECS/Fargate. I establish my connection with:
socketio = SocketIO(app, cors_allowed_origins=[], async_handlers=True, message_queue=redis_address, logger=True, engineio_logger=True)
socketio.init_app(app)
This works, however if I enable "Encryption in transit" on my redis instance (managed by AWS, no additional AUTH password was used in this instance), it fails silently. Any message emitted to the client after the connection has been established is never received by the client. There aren't any errors on the client or the server that I can find. "Encryption at rest" does work fine. I've tried using the redis address with both rediss:// and redis:// but have the same results.
Are there any configuration steps I need to set in order to tell Flask-SocketIO that my redis message queue uses SSL?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions