diff --git a/deploy/site/webclient.html b/deploy/site/webclient.html
index 2c4fe48d..4dac85f9 100644
--- a/deploy/site/webclient.html
+++ b/deploy/site/webclient.html
@@ -205,7 +205,7 @@
         <li>Pick the node and enter its PIN if it asks.</li></ol></div>
       <div class="way"><h3><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M5 12.55a11 11 0 0 1 14 0"/><path d="M1.42 9a16 16 0 0 1 21.16 0"/><path d="M8.53 16.11a6 6 0 0 1 6.95 0"/><path d="M12 20h.01"/></svg>Wi-Fi</h3><p class="who">Any browser, nodes with WADAMESH or meshcomod firmware</p><ol>
         <li>Turn Wi-Fi on, on the node, on the same network as you.</li>
-        <li>Open the <a href="http://app.wadamesh.com/">Wi-Fi version</a> of the web client.</li>
+        <li>Open the <a href="http://wifi.wadamesh.com/">Wi-Fi version</a> (wifi.wadamesh.com) of the web client.</li>
         <li>Press Connect, then Wi-Fi, and type the node's address.</li></ol></div>
     </div>
     <p class="note">Why a separate Wi-Fi version? Nodes speak plain, unencrypted WebSocket on your network (encryption is too heavy for the radio's chip next to Wi-Fi), and browsers do not let a secure https page open an unencrypted connection. The Wi-Fi version is the same client on plain http. Browsers in turn only allow USB, Bluetooth and your location on secure pages, so those work in the main version. In Chrome you can also allow "Insecure content" for the site to use Wi-Fi from the main version.</p>