Add changelog entry for dial 127.0.0.1 bugfix

thallgren · thallgren · commit d3bff59eea2d · 2026-02-14T05:24:11.000+01:00
Signed-off-by: Thomas Hallgren &lt;thomas@tada.se&gt;
diff --git a/CHANGELOG.yml b/CHANGELOG.yml
@@ -55,6 +55,14 @@ items:
   - version: 2.26.2
     date: (TBD)
     notes:
+      - type: bugfix
+        title: Dial 127.0.0.1 instead of 0.0.0.0 when connecting to local daemons
+        body: >-
+          When a VPN routes all private network addresses, dialing 0.0.0.0 gets routed through the VPN instead
+          of reaching the locally running daemon. This causes Telepresence to report that no daemon is running
+          even though the processes are active and listening. The client now dials 127.0.0.1 explicitly, and
+          the Docker-published daemon port is bound to 127.0.0.1 to match.
+        docs: https://github.com/telepresenceio/telepresence/issues/4048
       - type: bugfix
         title: Fix HTTP intercepts via telepresence compose failing when httpFilters or httpPaths are set
         body: >-
diff --git a/docs/release-notes.md b/docs/release-notes.md
@@ -21,6 +21,12 @@ A new Windows installer (.exe) is now available that installs Telepresence with
 </div>
 
 ## Version 2.26.2
+## <div style="display:flex;"><img src="images/bugfix.png" alt="bugfix" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">[Dial 127.0.0.1 instead of 0.0.0.0 when connecting to local daemons](https://github.com/telepresenceio/telepresence/issues/4048)</div></div>
+<div style="margin-left: 15px">
+
+When a VPN routes all private network addresses, dialing 0.0.0.0 gets routed through the VPN instead of reaching the locally running daemon. This causes Telepresence to report that no daemon is running even though the processes are active and listening. The client now dials 127.0.0.1 explicitly, and the Docker-published daemon port is bound to 127.0.0.1 to match.
+</div>
+
 ## <div style="display:flex;"><img src="images/bugfix.png" alt="bugfix" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">Fix HTTP intercepts via telepresence compose failing when httpFilters or httpPaths are set</div></div>
 <div style="margin-left: 15px">
 
diff --git a/docs/release-notes.mdx b/docs/release-notes.mdx
@@ -27,6 +27,12 @@ A new Windows installer (.exe) is now available that installs Telepresence with
   </Body>
 </Note>
 ## Version 2.26.2
+<Note>
+	<Title type="bugfix" docs="https://github.com/telepresenceio/telepresence/issues/4048">Dial 127.0.0.1 instead of 0.0.0.0 when connecting to local daemons</Title>
+	<Body>
+When a VPN routes all private network addresses, dialing 0.0.0.0 gets routed through the VPN instead of reaching the locally running daemon. This causes Telepresence to report that no daemon is running even though the processes are active and listening. The client now dials 127.0.0.1 explicitly, and the Docker-published daemon port is bound to 127.0.0.1 to match.
+  </Body>
+</Note>
 <Note>
 	<Title type="bugfix">Fix HTTP intercepts via telepresence compose failing when httpFilters or httpPaths are set</Title>
 	<Body>
