<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Update-Ca-Certificates on Support Tools</title><link>https://support.tools/tags/update-ca-certificates/</link><description>Recent content in Update-Ca-Certificates on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://support.tools/tags/update-ca-certificates/index.xml" rel="self" type="application/rss+xml"/><item><title>Add a CA Certificate to Ubuntu: update-ca-certificates</title><link>https://support.tools/post/installing-custom-ca-certificates-in-ubuntu/</link><pubDate>Thu, 12 Oct 2023 23:18:00 -0500</pubDate><guid>https://support.tools/post/installing-custom-ca-certificates-in-ubuntu/</guid><description>&lt;p&gt;To trust a private or self-signed certificate authority on Ubuntu, put the CA certificate in &lt;code&gt;/usr/local/share/ca-certificates/&lt;/code&gt; with a &lt;code&gt;.crt&lt;/code&gt; extension and run &lt;code&gt;sudo update-ca-certificates&lt;/code&gt;. That rebuilds &lt;code&gt;/etc/ssl/certs/ca-certificates.crt&lt;/code&gt;, the bundle that curl, wget, git, apt, OpenSSL and most other tools on Ubuntu read. The procedure is identical on Ubuntu 22.04, 24.04 and 26.04. This guide covers getting the right certificate, the expected output, the three mistakes that make it silently do nothing, and the applications that ignore the system store.&lt;/p&gt;</description></item></channel></rss>