# Remote SSH: Extension Host crashes with TypeError: Converting circular structure to JSON (issuerCertificate) **URL:** \ **Category:** Bug Reports\ **Tags:** extensions, crashes, ssh\ **Created:** [July 28, 2026, 4:16pm UTC](https://forum.cursor.com/t/remote-ssh-extension-host-crashes-with-typeerror-converting-circular-structure-to-json-issuercertificate/166879 "2026-07-28T16:16:45Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [July 28, 2026, 5:54pm UTC](https://forum.cursor.com/t/remote-ssh-extension-host-crashes-with-typeerror-converting-circular-structure-to-json-issuercertificate/166879/5 "2026-07-28T17:54:00Z")
Hey, thanks for the detailed breakdown. It’s clear you’ve already ruled out SSH, AppArmor, Git, and MCP. The `Converting circular structure to JSON … 'issuerCertificate'` error almost always happens when TLS certificate verification fails on some HTTPS connection. When verification fails, Node attaches the full certificate chain to the error. That chain references itself via `issuerCertificate`, and trying to JSON-serialize it crashes the Extension Host. So the root cause is a failed TLS handshake, and the crash is just a side effect. A similar case was discussed here: [IssuerCertificate api2.cursor.sh](https://forum.cursor.com/t/issuercertificate-api2-cursor-sh/137347) Since your local Mac can reach the backend fine, and only the remote session crashes, you should look at the remote host’s egress (LXC inside OrbStack). Think proxy or antivirus traffic interception, DNS issues, or an incomplete CA store inside the container. A few things that should help us move forward: - On the remote Ubuntu host, run this and share the output: - The logs didn’t attach. There are no attachments in the post. Please re-upload them and most importantly include the full stack trace from the remote extension host log at `~/.cursor-server/data/logs//remoteexthost.log` on the remote host, or from Output → Remote Extension Host. The stack will show which component is triggering the serialization. You can also quickly try a workaround. In settings, search for HTTP/2 and enable Disable HTTP/2, then reconnect. Once you have the `curl` output and the stack trace, post them here and we’ll dig in further. --- _[View the full topic](https://forum.cursor.com/t/remote-ssh-extension-host-crashes-with-typeerror-converting-circular-structure-to-json-issuercertificate/166879)._