[Danielle9897]

Issue link

https://issues.ravendb.net/issue/RDoc-4123/Quill-Document-Windows-Docker-Desktop-LAN-access

Additional description

---

Article organization:
Split the existing Networking & DNS article into two articles under a new Networking section:

• DNS & IP Configuration
• LAN Access on Windows

---

Content:
The new LAN Access on Windows article covers cases where Quill is reachable through localhost but cannot be reached through the Windows machine’s LAN address. Applies to Docker Desktop’s WSL 2 backend and Docker Engine running inside WSL.

• Mirrored networking and hostAddressLoopback configuration.
• Applying the settings and restarting Quill.
• Updating Quill’s DNS records to the Windows machine’s LAN address.
• Firewall checks and verification from both the Windows host and another LAN device.

---

Type of change

• Content - docs
• Content - cloud
• Content - Quill
• Content - guides
• Content - start pages/other
• New docs feature (consider updating /templates or readme)
• Bug fix
• Optimization
• Other

Changes in docs URLs

• No changes in docs URLs
• Articles are restructured, URLs will change, mapping is required (update /scripts/redirects.json file, set Documents Moved PR label)

Changes in UX/UI

• No changes in UX/UI
• Changes in UX/UI (include screenshots and description)

[Danielle9897]

@TheGoldenPlatypus
Could you address these questions?
I’ll update the docs based on your answers.

[TheGoldenPlatypus]

Which Windows, WSL, and Docker Desktop versions was the workaround verified on?

A: Tested on Windows 11 (build 26200, 24H2-class) with Docker Desktop (WSL2 backend).
But I’d rather not pin exact versions in the docs - the only real gate is “Windows 11 22H2+” (mirrored mode’s actual requirement), which the Prerequisites already state. Pinning a specific WSL/Docker Desktop build would just go stale and make users on other versions think it won’t work.

Was access verified from another LAN device as well as from the Windows machine through its LAN address?

A: yes to both. reached it from another device on the same Wi-Fi (and confirmed it’s LAN-only - cellular failed), and the host reached Quill via its own LAN IP once hostAddressLoopback was set.

Is an inbound firewall rule for port 443 required (Windows Firewall or Hyper-V firewall)? If so, which one?

A:* Not cleanly isolated . our testing had firewall changes in play, so I can’t say the Hyper-V rule is strictly mandatory with a clean mirrored config. Keep it as “may be required” under “If another device cannot connect” (as written) rather than stating it as a required step

[Danielle9897]

@TheGoldenPlatypus
Once the docs are approved, merged, and published, this link should work:
https://docs.ravendb.net/quill/networking/lan-access-on-windows