Skip to content

fix(gateway): improve error message for Docker bridge connectivity#4095

Merged
theonlyhennygod merged 3 commits intomasterfrom
fix/4086-gateway-docker-bind
Mar 21, 2026
Merged

fix(gateway): improve error message for Docker bridge connectivity#4095
theonlyhennygod merged 3 commits intomasterfrom
fix/4086-gateway-docker-bind

Conversation

@theonlyhennygod
Copy link
Copy Markdown
Collaborator

Summary

  • Improves the gateway security guard error message to mention the Docker use case when a public bind address is blocked
  • Provides clear instructions for connecting from Docker containers (host.docker.internal)
  • No behavior change; error message text only

Closes #4086

Test plan

  • Verify cargo check and cargo clippy pass
  • Start gateway with --host 0.0.0.0 without allow_public_bind = true and confirm the updated error message appears with Docker instructions
  • Confirm default 127.0.0.1 bind still works without any error

When the gateway security guard blocks a public bind address, the error
message now mentions the Docker use case and provides clear instructions
for connecting from Docker containers.

Closes #4086
@theonlyhennygod theonlyhennygod merged commit 46f6e79 into master Mar 21, 2026
17 checks passed
@theonlyhennygod theonlyhennygod deleted the fix/4086-gateway-docker-bind branch March 21, 2026 04:16
webhive pushed a commit to webhive/zeroclaw that referenced this pull request Mar 24, 2026
…eroclaw-labs#4095)

When the gateway security guard blocks a public bind address, the error
message now mentions the Docker use case and provides clear instructions
for connecting from Docker containers.

Closes zeroclaw-labs#4086
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: gateway

1 participant