Protected mode in Redis - Step-by-Step Execution

Concept Flow - Protected mode

Redis Server Starts

↓

Check Protected Mode Setting

↓

Bind to localhost

↓

Accept only local

↓

connections

↓

Wait for Client Commands

When Redis starts, it checks if protected mode is on. If yes, it only accepts local connections to keep safe. If no, it accepts connections from anywhere.

Execution Sample

Redis

redis-server --protected-mode yes
# Server starts in protected mode
# Binds only to localhost
# Rejects remote connections

This starts Redis with protected mode enabled, so it only accepts connections from the local machine.

Execution Table

Step	Action	Protected Mode	Bind Address	Connection Allowed	Reason
1	Start Redis Server	Yes	127.0.0.1	Yes	Protected mode enabled, binds localhost only
2	Client tries local connection	Yes	127.0.0.1	Yes	Local connection allowed
3	Client tries remote connection	Yes	127.0.0.1	No	Remote connections blocked in protected mode
4	Restart Redis with protected mode no	No	0.0.0.0	Yes	Binds all interfaces, accepts remote
5	Client tries remote connection	No	0.0.0.0	Yes	Remote connection allowed
6	Client tries local connection	No	0.0.0.0	Yes	Local connection allowed
7	Server stops	No	-	-	Server shutdown

💡 Execution stops when server shuts down or no more connection attempts

Variable Tracker

Variable	Start	After Step 1	After Step 4	Final
protected_mode	undefined	Yes	No	No
bind_address	undefined	127.0.0.1	0.0.0.0	0.0.0.0
connection_allowed_local	undefined	Yes	Yes	Yes
connection_allowed_remote	undefined	No	Yes	Yes

Key Moments - 3 Insights

Why does Redis reject remote connections when protected mode is enabled?

Because in protected mode Redis binds only to localhost (127.0.0.1), so remote clients cannot connect. See execution_table row 3.

What changes when protected mode is disabled?

Redis binds to all network interfaces (0.0.0.0) and accepts remote connections. See execution_table rows 4 and 5.

Can local connections be made when protected mode is enabled?

Yes, local connections are allowed because Redis binds to localhost. See execution_table row 2.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Redis start accepting remote connections?

A Step 5

B Step 2

C Step 3

D Step 6

💡 Hint

Check the 'Connection Allowed' column for remote connections in execution_table rows.

According to variable_tracker, what is the bind_address after step 1?

A 0.0.0.0

B 127.0.0.1

C localhost

D undefined

💡 Hint

Look at the 'bind_address' row and 'After Step 1' column in variable_tracker.

If protected_mode was set to 'No' from the start, what would be the connection_allowed_remote value after step 1?

A Undefined

B No

C Yes

D Depends on client

💡 Hint

Refer to variable_tracker 'connection_allowed_remote' values and execution_table step 4.

Concept Snapshot

Protected mode in Redis:
- Enabled by default for safety
- Binds Redis to localhost (127.0.0.1)
- Blocks remote connections
- Disable to allow remote access (bind 0.0.0.0)
- Prevents accidental exposure of Redis server

Full Transcript

When Redis server starts, it checks if protected mode is enabled. If yes, it binds only to localhost (127.0.0.1) and accepts connections only from the local machine. This blocks any remote connection attempts to protect the server from unauthorized access. If protected mode is disabled, Redis binds to all network interfaces (0.0.0.0) and accepts connections from remote clients. Local connections are always allowed. This behavior helps keep Redis safe by default and requires explicit action to expose it remotely.