Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Feature]: False gateway unreachable on TLS local gateway: probe uses wrong local target strategy [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#61767•Fetched 2026-04-08 02:54:44
View on GitHub
Comments
0
Participants
1
Timeline
9
Reactions
0
Author
Michae1GMichae1G
Participants
Michae1GMichae1G
Timeline (top)
referenced ×6closed ×1cross-referenced ×1labeled ×1

When a local gateway is TLS-enabled, openclaw gateway probe / related status checks can report the gateway as unreachable even though the gateway is actually healthy.

Root Cause

When a local gateway is TLS-enabled, openclaw gateway probe / related status checks can report the gateway as unreachable even though the gateway is actually healthy.

RAW_BUFFERClick to expand / collapse

Summary

Summary

When a local gateway is TLS-enabled, openclaw gateway probe / related status checks can report the gateway as unreachable even though the gateway is actually healthy.

Version

  • OpenClaw CLI: 2026.4.5
  • OS: macOS

Reproduction

  1. Enable local gateway TLS
  2. Start the gateway successfully
  3. Confirm the gateway is healthy over HTTPS/TLS
  4. Run openclaw gateway probe
  5. The CLI reports the gateway unreachable / closed

Expected

Local probe/status logic should resolve a TLS-valid target for a TLS-enabled local gateway.

Actual

The CLI probes a local target that is invalid for the current TLS setup, causing a false-negative health result.

Evidence

In the installed CLI bundle, local probe target generation is handled in dist/gateway-cli-9MGfQOH5.js (resolveTargets() / buildNetworkHints()), while dist/probe-Cv3pJ1Va.js forwards the generated URL directly into GatewayClient.

So if the chosen local target is wrong for the TLS setup, probe/status fails even though the gateway itself is up.

Suggested fix

Please make local probe target resolution TLS-aware and certificate-aware, instead of assuming a single fixed local target strategy.

Problem to solve

Summary

When a local gateway is TLS-enabled, openclaw gateway probe / related status checks can report the gateway as unreachable even though the gateway is actually healthy.

Version

  • OpenClaw CLI: 2026.4.5
  • OS: macOS

Reproduction

  1. Enable local gateway TLS
  2. Start the gateway successfully
  3. Confirm the gateway is healthy over HTTPS/TLS
  4. Run openclaw gateway probe
  5. The CLI reports the gateway unreachable / closed

Expected

Local probe/status logic should resolve a TLS-valid target for a TLS-enabled local gateway.

Actual

The CLI probes a local target that is invalid for the current TLS setup, causing a false-negative health result.

Evidence

In the installed CLI bundle, local probe target generation is handled in dist/gateway-cli-9MGfQOH5.js (resolveTargets() / buildNetworkHints()), while dist/probe-Cv3pJ1Va.js forwards the generated URL directly into GatewayClient.

So if the chosen local target is wrong for the TLS setup, probe/status fails even though the gateway itself is up.

Suggested fix

Please make local probe target resolution TLS-aware and certificate-aware, instead of assuming a single fixed local target strategy.

Proposed solution

Summary

When a local gateway is TLS-enabled, openclaw gateway probe / related status checks can report the gateway as unreachable even though the gateway is actually healthy.

Version

  • OpenClaw CLI: 2026.4.5
  • OS: macOS

Reproduction

  1. Enable local gateway TLS
  2. Start the gateway successfully
  3. Confirm the gateway is healthy over HTTPS/TLS
  4. Run openclaw gateway probe
  5. The CLI reports the gateway unreachable / closed

Expected

Local probe/status logic should resolve a TLS-valid target for a TLS-enabled local gateway.

Actual

The CLI probes a local target that is invalid for the current TLS setup, causing a false-negative health result.

Evidence

In the installed CLI bundle, local probe target generation is handled in dist/gateway-cli-9MGfQOH5.js (resolveTargets() / buildNetworkHints()), while dist/probe-Cv3pJ1Va.js forwards the generated URL directly into GatewayClient.

So if the chosen local target is wrong for the TLS setup, probe/status fails even though the gateway itself is up.

Suggested fix

Please make local probe target resolution TLS-aware and certificate-aware, instead of assuming a single fixed local target strategy.

Alternatives considered

No response

Impact

Summary

When a local gateway is TLS-enabled, openclaw gateway probe / related status checks can report the gateway as unreachable even though the gateway is actually healthy.

Version

  • OpenClaw CLI: 2026.4.5
  • OS: macOS

Reproduction

  1. Enable local gateway TLS
  2. Start the gateway successfully
  3. Confirm the gateway is healthy over HTTPS/TLS
  4. Run openclaw gateway probe
  5. The CLI reports the gateway unreachable / closed

Expected

Local probe/status logic should resolve a TLS-valid target for a TLS-enabled local gateway.

Actual

The CLI probes a local target that is invalid for the current TLS setup, causing a false-negative health result.

Evidence

In the installed CLI bundle, local probe target generation is handled in dist/gateway-cli-9MGfQOH5.js (resolveTargets() / buildNetworkHints()), while dist/probe-Cv3pJ1Va.js forwards the generated URL directly into GatewayClient.

So if the chosen local target is wrong for the TLS setup, probe/status fails even though the gateway itself is up.

Suggested fix

Please make local probe target resolution TLS-aware and certificate-aware, instead of assuming a single fixed local target strategy.

Evidence/examples

No response

Additional information

No response

extent analysis

TL;DR

Make the local probe target resolution TLS-aware and certificate-aware to fix the issue with the openclaw gateway probe reporting a healthy TLS-enabled gateway as unreachable.

Guidance

  • Review the resolveTargets() and buildNetworkHints() functions in dist/gateway-cli-9MGfQOH5.js to understand how local probe targets are generated.
  • Modify the target generation logic to consider the TLS setup and certificate of the local gateway.
  • Update the dist/probe-Cv3pJ1Va.js file to forward the corrected URL to the GatewayClient.
  • Verify the fix by running the openclaw gateway probe command after making the changes.

Example

No specific code example can be provided without modifying the existing codebase, but the fix should involve updating the resolveTargets() and buildNetworkHints() functions to handle TLS-enabled gateways.

Notes

The provided information suggests that the issue is specific to the OpenClaw CLI version 2026.4.5 on macOS, but the fix should be applicable to other versions and platforms as well.

Recommendation

Apply the suggested fix to make the local probe target resolution TLS-aware and certificate-aware, as this should resolve the issue with the openclaw gateway probe reporting a healthy TLS-enabled gateway as unreachable.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#container setup#orchestration issue#cache issue#memory leak#API versioning

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Feature]: False gateway unreachable on TLS local gateway: probe uses wrong local target strategy [1 participants]