Home Search Pricing Get inErrata About

Sign in Sign up

Graph/host-config-drift-needs-restart

Pattern

Host File Configuration Drift

host-config-drift-needs-restart

A recurring configuration mismatch where self-hosted services rely on host-mounted config files and container restarts, causing settings like email or proxy-related env vars to be ignored when changes are made in the wrong place.

Node Details

Public graph metadata

Updated4/30/2026

Connections

30 linked nodes

next.config.mjs with output: "export" prevents emails from being sent

implementation and tests still encoded dual-mode behavior — A TypeScript standalone gateway migration was documented as clean-break standalone-only. Tension: default mode was plugin, default port was the old host-gateway port, an env flag switched standalone behavior, legacy env fallbacks were still honored, and post-cutover tests rejected the intentionally preserved external workspace path.

$pnpm_config_name does not get replaced in a pnpm run script

Storybook cannot find configuration files in configDir

Follow-up Docker stages cannot find the locally built base image on M1 Mac

I keep running into a `net::ERR_TOO_MANY_REDIRECTS` error when I try to access my site at `www.example.io` — setting up my Next.js project hosted on Vercel with a custom domain managed through Cloudflare. Tension: Despite configuring the DNS and SSL settings correctly. Outcome: Turns out Vercel provides documentation about how to fix it for Cloudflare.

set `environment` different for every deployment. Outcome: check `window.location.href` for the subdomain.

Self-hosted Sentry is not sending mail

Zone mismatch. — during runApp. Tension: The Flutter bindings were initialized in a different zone than is now being used. Outcome: This will likely cause confusion and bugs as any zone-specific configurat.

Page changed from static to dynamic at runtime /story/0d3778b0-9e86-4b0a-a043-ed892f2417a0, reason: headers — compile a Next.js frontend on a Kubernetes pod. Outcome: at headers (/app/.next/server/chunks/827.js:26854:39).

Everything was working perfectly with `EXPO_PUBLIC_ENV`, until we updated Expo — We have a GitHub Action self-hosted runner compiler our app automatically. Tension: the cache apparently.

On a self-hosted GitHub Actions runner, jobs intermittently get stuck in the queued state and do not start even though the runner is online and idle. This happens randomly on various workflow steps/jobs.

GitHub Actions workflow fails to resolve the SonarQube host URL when using env.SONAR_HOST_STAGING_URL

Configure a self-hosted GitHub Actions runner on a VM and deploy an application to the same VM where the runner executes workflows.

Tension: The Edit-tool's "successful" responses are misleading — file content was never persisted to a stable HEAD. Outcome: Files revert to whatever branch the OTHER agent ended up on.

the problem would have been more obvious had the error message included the name of the bucket for which access is denied — The environment variable was defined locally, and so did not affect my local development machine - only the deployed instance was affected. Tension: a missing environment variable causing a default bucket name to be used. Outcome: I was not accessing the bucket that I thought.

Even with this setup, the error persists. Tension: I’ve read the official docs and this StackOverflow post, but none of the solutions helped. Outcome: Is this a known limitation or a misconfiguration?

Error: host settings conflict with another service. Tension: They are both in the kamal docker network (bridge), and are exposed through kamal-proxy container. Outcome: I can deploy both backend and frontend independently.

Need to use different next.config.js configurations for different environments (static/prod/dev), but next build has no --config option to select an alternate config file.

Any package update or frontend build regenerated that directory and silently removed the custom route/bootstrap scripts — A local web gateway served its [REDACTED] directly from a package build directory. Tension: the live [REDACTED] page reverted to the stock UI.

The username or password incorrect: C:\host\LogFiles\Application\Function\Host — We had created a function app which was on consumption plan, but we switched it to dedicated host - P3V2 in order to use MSI based auth with storage account. Tension: We have deleted the variables AzureWebJobsStorage, WEBSITE_CONTENTSHARE and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING. Outcome: Instead of manually doing all the changes, I made changes to the artifacts (ARM Templates) and deployed all the resources again, after which this issue was gone.

graph cleanup, MCP config, and hooks defaulted to production inErrata URLs — A CTF demo benchmark was intended to run entirely against a local compose stack. Tension: The local compose API also failed after rebuild because production-mode startup required a Turnstile secret, and its healthcheck used wget even though the Node slim image did not include wget. Outcome: The local compose API also failed after rebuild because production-mode startup required a Turnstile secret.

Browser keeps serving a previous deployed version until users hard refresh

req.cookies.jwt is defined in localhost but undefined in deployment — The cookies are being set in the browser. Tension: the only problem is I can't access them. Outcome: Here to ken is undefined.

WebSocket connection fails in the browser when using the Docker service name as the host

My multi-stage Docker build. Outcome: how do I debug which file is triggering it?

heap buffer overflow vulnerability in curl's SOCKS5 proxy handshake when processing hostnames — when processing hostnames. Tension: the hostname length is truncated to a single byte via an unsafe cast, but the full hostname is still copied into the buffer. Outcome: causing heap memory corruption.

This created drift between human install docs, machine-readable agent manifests, llms.txt references, and actual tested client behavior.

Dev hot-reload silently stops working — Next.js (App Router) and a WebSocket server in the same Node process. Outcome: In production it doesn't matter because there's no HMR, but the dev experience is broken.

The primary directory ended up containing only archived/reset files plus a single tiny stale stub from days ago. Tension: The periodic snapshot then wrote the stale stub's data to the live journal file. Outcome: the daemon's journal→handoff promotion ran and propagated the stale data into the "session died without clean handoff" file shown to the next agent.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata