docs: add WSL2 networking guide for local model servers#5616
Merged
Conversation
Windows users running Hermes in WSL2 with model servers on the Windows host hit 'connection refused' because WSL2's NAT networking means localhost points to the VM, not Windows. Covers: - Mirrored networking mode (Win 11 22H2+) — makes localhost work - NAT mode fallback using the host IP via ip route - Per-server bind address table (Ollama, LM Studio, llama-server, vLLM, SGLang) - Detailed Ollama Windows service config for OLLAMA_HOST - Windows Firewall rules for WSL2 connections - Quick verification steps - Cross-reference from Troubleshooting section
|
dbmizrahi
pushed a commit
to dbmizrahi/hermes-agent
that referenced
this pull request
Apr 10, 2026
…#5616) Windows users running Hermes in WSL2 with model servers on the Windows host hit 'connection refused' because WSL2's NAT networking means localhost points to the VM, not Windows. Covers: - Mirrored networking mode (Win 11 22H2+) — makes localhost work - NAT mode fallback using the host IP via ip route - Per-server bind address table (Ollama, LM Studio, llama-server, vLLM, SGLang) - Detailed Ollama Windows service config for OLLAMA_HOST - Windows Firewall rules for WSL2 connections - Quick verification steps - Cross-reference from Troubleshooting section
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a dedicated WSL2 Networking section to the AI Providers docs page, covering how to connect from Hermes (running in WSL2) to model servers running on the Windows host.
This is a common pain point — WSL2's default NAT networking means
localhostinside WSL2 refers to the Linux VM, not the Windows host. Users get "connection refused" when pointing Hermes athttp://localhost:11434for Ollama on Windows.What's covered
localhostwork bidirectionallyip route, dynamic helper script, mDNS approach127.0.0.1which rejects WSL2 NAT connections)OLLAMA_HOST=0.0.0.0Placement
New
### WSL2 Networking (Windows Users)section between LM Studio and Troubleshooting Local Models — positioned as a setup consideration alongside the server sections, not buried in troubleshooting.Test plan
skills.jsonbuild error):::tip,:::note,:::caution) follows existing patterns