checkServerIdentity never called

“1.3.14 and earlier connect, but only because they never verified the certificate with the ssl object form (see Additional information).”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/bun/issues/4774/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports and thumbs-up in the last two weeks, down from 3 a week at the late-September peak.

Custom checkServerIdentity callback is never called on TLS connections. Affects tls.checkServerIdentity assignment, Bun.SQL Postgres ssl options, and ws, undici, node-fetch; a callback that refuses every server is ignored.

Is this your bug?

File my report

Where: TLS clients
Versions: 1.4.2 to 1.4.3-canary.1
Platforms: Linux, macOS
How bad: Security risk: something exposed, or done without permission. Some reports say it used to work.

Not quite your bug?

TLS client sends Finished and certificate before rejecting server2 people
No TLS alert on rejection1 person

Original reports3, newest first

Sep 27, 2026ws, undici, node-fetch: checkServerIdentity is never called#44142
Sep 27, 2026node:tls: a function assigned to tls.checkServerIdentity is never called#44141
Sep 7, 2026Bun.SQL (Postgres): TLS hostname mismatch fails with an empty Error, and checkServerIdentity is ignored#41856

checkServerIdentity never called

Is this your bug? What gets counted gets fixed. Pile on.

Is this your bug?

Not quite your bug?

Original reports3, newest first

Do you work on Bun?