Bitcoin full node and query server

Oct 1, 2026

View in context in the libbitcoin Slack #general mirror.

evoskuil01:38

These errors that hit the log today in the meeting are actually excellent error handling:

2026-09-30T17:45:54Z.6 Failed to accept private native connection, tls alert certificate unknown
2026-09-30T17:45:54Z.6 Failed to accept private native connection, tls alert certificate unknown
2026-09-30T17:45:54Z.6 Failed to accept private native connection, tls alert certificate unknown
2026-09-30T17:45:54Z.6 Failed to accept private native connection, tls alert certificate unknown
2026-09-30T17:45:54Z.6 Failed to accept private native connection, tls alert certificate unknown
2026-09-30T17:45:54Z.6 Failed to accept private native connection, tls alert certificate unknown

The client is rejecting your certificate; the server isn't failing. Our server never sends certificate_unknown (46) itself. That error only appears when the peer sends a fatal alert during the handshake, which server::handle_alert (server.cpp:434) records as a received failure. So the browser got your certificate, checked it, decided not to trust it, and closed the handshake.