{"version":"2.1.238","anchor":"remote-bridge-retries-rejections-that-did-not-come-from-the-","canonical_anchor":"remote-bridge-retries-rejections-that-did-not-come-from-the-","heading":"Remote bridge retries rejections that did not come from the origin server","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/remote-bridge-retries-rejections-that-did-not-come-from-the-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Remote bridge retries rejections that did not come from the origin server\n\nRemote bridge retries 401\/403\/404s that came from a proxy rather than closing permanently.\n\n**What**\n\nWhen the remote connection is rejected with a 401, 403 or 404 that is reported as coming from something other than the origin server (a proxy, for example), the bridge now retries within a time window instead of closing permanently. Controlled by `tengu_ethereal_mist`, which falls back to on.\n\n**Details**\n\n- Rejections are tracked as a streak; logs distinguish a permanent rejection from a retried non-origin one and include the attempt number.\n- A successful recovery is reported with the number of attempts and how long the streak lasted.\n\n**Evidence**\n\n`nonOrigin403Retry`\n\n- Flag `tengu_ethereal_mist`: Not enough to say (read for one account on one subscription tier against v2.1.238; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}