[BUG] ASGI server incorrect handle of Redis connection

[AleksaMCode]

Is there an existing issue for this?

• [X] I have searched the existing issues

Description

When the server is started, it doesn't create a connection to the Redis server by default. The connection to Redis is created when a subscriber connects, but not when a publisher connects.

System information

1. Kali Linux
2. 2023.3
3. Raspberry Pi 4

Actual Behavior

• ASGI sever is started without errors.
• Sniffer connects to the server.
• Sniffer sends data through socket.
• Publisher receives data through socket from Sniffer, but as soon as it tries to send data to Redis channel it fails due to the fact that the connection to Redis was never created.

Expected Behavior

Connection to Redis server needs to be created when the ASGI server is first started.

Steps To Reproduce

1. Start the Redis server
2. Start the ASGI server
3. Start the Sniffer

Anything else?

Here is a screenshot of the error.

The connection object is None due to the fact the Redis connection was never created.

[AleksaMCode]

Also, due to this bug there is another problem.

Description

When the server is started, it doesn't create a connection to the Redis server by default. The connection to Redis is created when a subscriber connects, but not when a publisher connects. This means, that if the web application is started after running ASGI server without running Redis server, it will display a toast notification that it has connected to the server, after which the ASGI server will fail to handle Exceptions.

Actual Behavior

• ASGI sever is started without errors
• Web application connects to the server
• As soon as it connects to the server, it fails due to the fact that the connection to Redis was never created and the Exception is never handled correctly.

Expected Behavior

• Connection to Redis server needs to be created when the ASGI server is first started.
• Also, Exceptions due to Redis errors need to be handled.
• ASGI should fail to start if there is no Redis server running.

Steps To Reproduce

1. Start the Redis server
2. Start the React server

Anything else?

Here is a screenshot of the error.