https://errorvault.dev/tags/resolution/ Recent content in Resolution on ErrorVault — Developer Error Code Dictionary Hugo en-us Sat, 04 Jul 2026 11:17:00 +0800 https://errorvault.dev/docker/docker-docker-dns-resolution-failed-container-dns-issue/ Sat, 04 Jul 2026 11:17:00 +0800 https://errorvault.dev/docker/docker-docker-dns-resolution-failed-container-dns-issue/ <p>The <code>docker-dns-resolution-failed</code> error indicates that a Docker container is unable to resolve domain names to IP addresses, effectively preventing it from accessing external network resources like APIs, package repositories, or other services on the internet. This issue manifests as connectivity failures within the container, even if the host machine has full network access. Understanding and resolving this error is crucial for deploying functional containerized applications that rely on external communication.</p> https://errorvault.dev/openclaw/openclaw-clw-api-not-found-api-endpoint-resolution/ Thu, 11 Jun 2026 22:20:04 +0800 https://errorvault.dev/openclaw/openclaw-clw-api-not-found-api-endpoint-resolution/ <h2 id="1-symptoms">1. Symptoms</h2> <p>The <code>clw-api-not-found</code> error manifests when OpenClaw fails to resolve or locate a required API endpoint during runtime. Developers typically encounter this error immediately after initiating a connection, running a sync operation, or attempting to access cloud resources through the OpenClaw CLI or API client.</p> <p><strong>Common symptom patterns include:</strong></p> <ul> <li>CLI command terminates with exit code 127 and the <code>clw-api-not-found</code> message</li> <li>API calls return 404 status codes or connection failures</li> <li>Configuration files appear correct but operations fail silently or with cryptic messages</li> <li>The error occurs on first-time setup or after infrastructure changes</li> </ul> <p><strong>Typical error output:</strong></p>