{"version":"2.1.246","anchor":"artifact-uploads-report-a-refused-proxy-distinctly","canonical_anchor":"artifact-uploads-report-a-refused-proxy-distinctly","heading":"Artifact uploads report a refused proxy distinctly","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/artifact-uploads-report-a-refused-proxy-distinctly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Artifact uploads report a refused proxy distinctly\n\nArtifact uploads blocked by a network proxy now say so and confirm nothing was sent.\n\n**What**\n\nAn artifact store request that fails because a network proxy rejected the connection now reports that specific cause and states that nothing was sent, rather than a generic request error. Relay requests through the artifact gateway also record whether the request went through a tunnel.\n\n**Details**\n\n- The failure reason is `proxy_refused`; the tunnel marker is added alongside the existing runner marker on artifact frame relay events.\n- Both apply unconditionally on the artifact upload and store path.\n\n**Evidence**\n\n`a network proxy refused the connection; nothing was sent`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}