Skip to main content
0 reactions

Fixed: “Could not connect to Valkey at 127.0.0.1:6379: setsockopt(TCP_NODELAY): Invalid argument” on macOS

Featured image for the fix of setsockopt(TCP_NODELAY): Invalid argument on macOS, with a warning sign, the words Could not connect to Valkey, and the fix, brew services start valkey.
Fixed: setsockopt(TCP_NODELAY): Invalid argument on macOS.

If valkey-cli on a Mac prints the message below, Valkey® isn’t answering at that address. The words setsockopt(TCP_NODELAY) make it look like a network setting is wrong, but it’s the same problem as “Connection refused”.

OutputPlain text
Could not connect to Valkey at 127.0.0.1:6379: setsockopt(TCP_NODELAY): Invalid argument

What I Was Doing

I had just installed Valkey 9.1.4 with Homebrew on an Apple silicon Mac with macOS 26, for How to Install Valkey on macOS. I stopped the service with brew services stop valkey while writing that guide’s stop and start steps, then ran valkey-cli ping.

What I Expected

A message saying that nothing was listening, such as “Connection refused”.

What I Got

TerminalBash
valkey-cli ping
OutputPlain text
Could not connect to Valkey at 127.0.0.1:6379: setsockopt(TCP_NODELAY): Invalid argument
Terminal window showing valkey-cli ping failing with Could not connect to Valkey at 127.0.0.1:6379: setsockopt(TCP_NODELAY): Invalid argument.
The message valkey-cli prints on macOS when Valkey isn’t running.

What I Checked

Valkey’s installation guide for macOS (opens in a new tab) checks that Valkey is running with brew services info valkey:

TerminalBash
brew services info valkey
OutputPlain text
valkey (sh.brew.valkey)
Running: ✘
Loaded: ✘
Schedulable: ✘
Terminal window showing brew services info valkey with Running, Loaded and Schedulable each marked with a red cross.
brew services info valkey shows that Valkey isn’t running.

Running: ✘ means Valkey isn’t running, so nothing answers on port 6379.

Why It Happens

valkey-cli connects to 127.0.0.1, port 6379, unless you give it another host or port. When nothing listens there, the connection fails. On macOS, Valkey’s client library mistakes that failed connection for an open one, so its next step, switching on the TCP_NODELAY option for the connection, fails with “Invalid argument”. That later error is the one it prints.

Valkey’s own tests meet the same message on macOS, where they expect “Connection refused” (valkey-io/valkey issue #5330 (opens in a new tab)), and a fix to the client library is open (pull request #5331 (opens in a new tab)). The message also appears for a port where nothing listens:

TerminalBash
valkey-cli -p 6380 ping
OutputPlain text
Could not connect to Valkey at 127.0.0.1:6380: setsockopt(TCP_NODELAY): Invalid argument

The Fix

Start Valkey

TerminalBash
brew services start valkey
OutputPlain text
==> Successfully started `valkey` (label: sh.brew.valkey)

Or point valkey-cli at the right port

If you gave valkey-cli a port with -p, use the port your Valkey listens on, or leave -p out. The Homebrew service uses port 6379, set in /opt/homebrew/etc/valkey.conf.

After the Fix

TerminalBash
valkey-cli ping
OutputPlain text
PONG
Terminal window showing brew services start valkey succeeding and valkey-cli ping answering PONG after the fix.
After starting Valkey, valkey-cli ping answers PONG.

Valkey answers PONG, and brew services info valkey now shows Running: ✔.

Common Mistakes

MistakeWhat happensDo this instead
Changing network or firewall settings because the message names TCP_NODELAYNothing improves, because that option isn’t the problemStart Valkey, or point valkey-cli at the port Valkey uses
Running valkey-cli -p 6380 for the Homebrew serviceNothing listens on 6380, so you get the same messageLeave out -p to use port 6379

FAQ

Is this a bug in Valkey?

The wording is misleading on macOS, and Valkey tracks it in issue #5330. The situation behind it is normal: valkey-cli couldn’t reach a Valkey server.

Does this happen on Linux?

Valkey’s tests expect “Connection refused” for the same situation and fail only on macOS, so on Linux you see the usual “Connection refused” message.

Do I need to change TCP_NODELAY?

No. valkey-cli switches that option on by itself for every network connection. Nothing in your settings needs to change.

Conclusion

On macOS, “setsockopt(TCP_NODELAY): Invalid argument” from valkey-cli means nothing answered at that address and port. Check with brew services info valkey, then start Valkey or use the right port.

Additional Resources

Valkey® is a registered trademark of LF Projects, LLC. Redis® is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Other names mentioned are trademarks of their respective owners. JD Bots isn’t affiliated with the Valkey project, LF Projects or Redis Ltd., and isn’t endorsed, supported or certified by them.

0 comments