When fetch can't reach the mail server at all (DNS, a refused connection, a certificate Node doesn't trust), its message is only "fetch failed" and the reason sits on err.cause. The sign-in and token-refresh warnings logged only the message, so an operator whose proxy never saw the request had nothing to go on. Reported in https://community.coffeylabs.org/t/webmail-failing-to-access-server/122.
failureReason() in upstream.ts adds the cause, e.g. fetch failed (UNABLE_TO_VERIFY_LEAF_SIGNATURE: unable to verify the first certificate). Used at the four sign-in/refresh warnings in app.ts. Typecheck, tests and build pass locally; new tests in server/src/failurereason.test.ts.
No new strings.
When fetch can't reach the mail server at all (DNS, a refused connection, a certificate Node doesn't trust), its message is only "fetch failed" and the reason sits on `err.cause`. The sign-in and token-refresh warnings logged only the message, so an operator whose proxy never saw the request had nothing to go on. Reported in https://community.coffeylabs.org/t/webmail-failing-to-access-server/122.
`failureReason()` in upstream.ts adds the cause, e.g. `fetch failed (UNABLE_TO_VERIFY_LEAF_SIGNATURE: unable to verify the first certificate)`. Used at the four sign-in/refresh warnings in app.ts. Typecheck, tests and build pass locally; new tests in server/src/failurereason.test.ts.
No new strings.
When fetch can't reach the mail server at all (DNS, a refused connection, a certificate Node doesn't trust), its message is only "fetch failed" and the reason is on err.cause. The sign-in and token-refresh warnings logged the message alone, so an operator whose proxy never saw the request had nothing to go on (community thread 122). They now add the cause, e.g. "fetch failed (UNABLE_TO_VERIFY_LEAF_SIGNATURE: unable to verify the first certificate)".
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When fetch can't reach the mail server at all (DNS, a refused connection, a certificate Node doesn't trust), its message is only "fetch failed" and the reason sits on
err.cause. The sign-in and token-refresh warnings logged only the message, so an operator whose proxy never saw the request had nothing to go on. Reported in https://community.coffeylabs.org/t/webmail-failing-to-access-server/122.failureReason()in upstream.ts adds the cause, e.g.fetch failed (UNABLE_TO_VERIFY_LEAF_SIGNATURE: unable to verify the first certificate). Used at the four sign-in/refresh warnings in app.ts. Typecheck, tests and build pass locally; new tests in server/src/failurereason.test.ts.No new strings.