# Firefox will not load CA on Purism Librem 5 running Pure OS

**URL:** <https://community.start9.com/t/firefox-will-not-load-ca-on-purism-librem-5-running-pure-os/4300>\
**Category:** DIY Community\
**Created:** [October 18, 2025, 3:06pm UTC](https://community.start9.com/t/firefox-will-not-load-ca-on-purism-librem-5-running-pure-os/4300 "2025-10-18T15:06:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![authorjawebb](https://community.start9.com/letter_avatar_proxy/v4/letter/a/7bcc69/32.png) [@authorjawebb](https://community.start9.com/u/authorjawebb)\
**Post date:** [October 18, 2025, 3:06pm UTC](https://community.start9.com/t/firefox-will-not-load-ca-on-purism-librem-5-running-pure-os/4300/1 "2025-10-18T15:06:15Z")

</div>

I just got a Librem 5 and am working on the setup.

I successfully trusted the root CA in terminal, then went to Firefox. Correctly configured the About:Config settings but when attempting to load the P11 System CA Trust module in Firefox\>settings\>security\>devices it keeps returning an error message “unable to load”.

I’ve attempted multiple Firefox and device restarts with no luck.

Has anyone successfully forced Firefox to load the p11 on a Librem 5 device?

---

<div class="post-metadata">

**Author:** ![StuPleb](https://community.start9.com/user_avatar/community.start9.com/stupleb/32/195_2.png) [@StuPleb](https://community.start9.com/u/StuPleb)\
**Post date:** [October 18, 2025, 4:06pm UTC](https://community.start9.com/t/firefox-will-not-load-ca-on-purism-librem-5-running-pure-os/4300/2 "2025-10-18T16:06:41Z")

</div>

I’m no Purism expert, and I don’t now much about their devices.

I assume this is the phone that runs linux, right?

And that you’re going through this guide: [Start9 | Configuring Firefox to Respect Your Root CA](https://docs.start9.com/0.3.5.x/misc-guides/ca-ff.html)

and you’re probably on Step 3.

The only comment I’d have is to look at the tip that’s there about processor architecture. You’ll probably has to ask a purism community what the path should be.

---

<div class="post-metadata">

**Author:** ![authorjawebb](https://community.start9.com/letter_avatar_proxy/v4/letter/a/7bcc69/32.png) [@authorjawebb](https://community.start9.com/u/authorjawebb)\
**Post date:** [October 18, 2025, 4:34pm UTC](https://community.start9.com/t/firefox-will-not-load-ca-on-purism-librem-5-running-pure-os/4300/3 "2025-10-18T16:34:21Z")

</div>

Correct- step 3, and I appreciate your fast response- checking with them on pathing- will respond here if we get resolution

TY!

---

<div class="post-metadata">

**Author:** ![authorjawebb](https://community.start9.com/letter_avatar_proxy/v4/letter/a/7bcc69/32.png) [@authorjawebb](https://community.start9.com/u/authorjawebb)\
**Post date:** [October 21, 2025, 1:58pm UTC](https://community.start9.com/t/firefox-will-not-load-ca-on-purism-librem-5-running-pure-os/4300/4 "2025-10-21T13:58:09Z")

</div>

Got the info from Purism as follows:

As per [Debian -- File list of package p11-kit-modules/trixie/arm64](https://packages.debian.org/trixie/arm64/p11-kit-modules/filelist) this should be /usr/lib/aarch64-linux-gnu/pkcs11/p11-kit-trust.so

That worked- and now have https locked. Now to get apps installed and interfaced- if other hiccups with that will post here

---

<div class="post-metadata">

**Author:** ![system](https://community.start9.com/uploads/default/original/1X/2dcde8aa6ad3ce3d7873096ee4b3e5395e19a7b5.png) [@system](https://community.start9.com/u/system)\
**Post date:** [October 23, 2025, 1:58pm UTC](https://community.start9.com/t/firefox-will-not-load-ca-on-purism-librem-5-running-pure-os/4300/5 "2025-10-23T13:58:25Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.