Answer: If some users can connect to Kiro but others cannot, see Network connectivity issues in the troubleshooting guide. If your network performs TLS inspection and Kiro IDE requests fail with read ECONNRESET, see TLS inspection compatibility. Status: Confirmed Entry: tool/kiro/troubleshooting/troubleshoot-connection-issues Revision: 3 Digest: sha256:6b293381a6ef3624 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:44:20Z Last changed: 2026-11-19T13:22:48Z (TLS inspection troubleshooting: — → TLS inspection compatibility) Last verified: 2026-11-20T13:31:41Z Next check: 2026-11-21T13:31:41Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of General connectivity troubleshooting | Network connectivity issues | [1] | 2026-11-20 TLS inspection troubleshooting | TLS inspection compatibility | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Firewalls, proxies, and data perimeters - Privacy and Security - Docs - Kiro". https://kiro.dev/docs/privacy-and-security/firewalls/ Role: primary. Accessed: 2026-11-20T13:31:41Z Quote: "If some users can connect to Kiro but others cannot, see Network connectivity issues in the troubleshooting guide." (Supports: General connectivity troubleshooting) Quote: "If your network performs TLS inspection and Kiro IDE requests fail with read ECONNRESET , see TLS inspection compatibility ." (Supports: TLS inspection troubleshooting) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 928a03f3d9448fdb2dec91bd6a39021d05bc1b8775f0225403eb1f2862ec0952 (captured 2026-11-20T13:31:38Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:31:41Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:31:41Z Last attempt: 2026-11-20T13:31:41Z Notes and limitations: Extracted automatically from a single official source (section "Troubleshooting connection issues"). Related: https://latestn.com/tool/kiro/troubleshooting/troubleshoot-dashboard How do I troubleshoot issues with the Kiro usage dashboard? https://latestn.com/tool/kiro/troubleshooting/troubleshoot-mcp-tool-usage How do I troubleshoot an MCP tool that is not responding or not available in Kiro? https://latestn.com/tool/kiro/troubleshooting/troubleshoot-payment-issues What should I do if I have a payment issue in Kiro? https://latestn.com/tool/kiro/troubleshooting/tangent-merge-errors What should I do if I get a merge error when merging a Kiro tangent? https://latestn.com/tool/kiro/troubleshooting/todo-list-limitations What are the limitations of TODO lists in Kiro CLI? https://latestn.com/tool/kiro/troubleshooting/troubleshoot-agent-notifications How do I troubleshoot agent notifications that aren't working in Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:22:48Z | changed | TLS inspection troubleshooting: — → TLS inspection compatibility | [1] 2026-11-19T13:22:48Z | changed | General connectivity troubleshooting: — → Network connectivity issues | [1] 2026-11-19T13:22:48Z | changed | TLS inspection error: read ECONNRESET → — | [1] 2026-11-19T13:22:48Z | changed | General connectivity issue: Network connectivity issues → — | [1] 2026-11-18T13:26:20Z | changed | General connectivity issue: — → Network connectivity issues | [1] 2026-11-18T13:26:20Z | changed | general troubleshooting: Network connectivity issues → — | [1] 2026-11-13T03:44:20Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/troubleshooting/troubleshoot-connection-issues/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/troubleshooting/troubleshoot-connection-issues POST: https://latestn.com/dispute/tool/kiro/troubleshooting/troubleshoot-connection-issues with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/troubleshooting/troubleshoot-connection-issues?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I troubleshoot connection issues with Kiro behind a firewall or proxy? Revision 3, last verified 2026-11-20T13:31:41Z. https://latestn.com/tool/kiro/troubleshooting/troubleshoot-connection-issues (accessed 2026-11-21T10:03:25Z). @misc{LatestN_tool_kiro_troubleshooting_troubleshoot_connection_issues_r3, title = {How do I troubleshoot connection issues with Kiro behind a firewall or proxy?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/troubleshooting/troubleshoot-connection-issues}}, note = {Revision 3; digest sha256:6b293381a6ef3624; last verified 2026-11-20T13:31:41Z; accessed 2026-11-21T10:03:25Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/troubleshooting/troubleshoot-connection-issues