[GH-ISSUE #7700] [Bug]: Self-signed certs no longer work on 26.05 on Electron #80603

Closed
opened 2026-05-19 04:25:42 -05:00 by GiteaMirror · 8 comments
Owner

Originally created by @tjmills-dev on GitHub (May 4, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7700

Originally assigned to: @MikesGlitch on GitHub.

What happened?

After updating to 26.05 I am no longer able to use my self-hosted Actual with a non-public CA cert.
I have tested and the issue exists on x86 Windows and Linux (AppImage & Flatpak). I'm unable to verify whether the issue presents on Mac as I don't have access to that platform.
The error does not occur on 26.04.

The UI presents:

Image

When ran from bash, both the Flatpak and Appimage produce the following error:

"Server Log: TypeError: fetch failed
    at node:internal/deps/undici/undici:14902:13
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
    at async fetch$1 (/tmp/.mount_Actual6PJ4Lt/resources/app.asar/build/loot-core/lib-dist/electron/bundle.desktop.js:61883:10)
    at async needsBootstrap (/tmp/.mount_Actual6PJ4Lt/resources/app.asar/build/loot-core/lib-dist/electron/bundle.desktop.js:112078:13) {
  [cause]: Error: unable to get local issuer certificate
      at TLSSocket.onConnectSecure (node:_tls_wrap:1697:34)
      at TLSSocket.emit (node:events:519:28)
      at TLSSocket._finishInit (node:_tls_wrap:1095:8)
      at ssl.onhandshakedone (node:_tls_wrap:881:12) {
    code: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY'
  }
}"

How can we reproduce the issue?

  1. Open the Actual desktop app and attempt to configure a server that uses a self-signed/non-public CA
  2. Be greeted by the self-signed error message
  3. Click the link to add a certificate - error message disappears
  4. Click Start - error message reappears

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Linux

Originally created by @tjmills-dev on GitHub (May 4, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7700 Originally assigned to: @MikesGlitch on GitHub. ### What happened? After updating to 26.05 I am no longer able to use my self-hosted Actual with a non-public CA cert. I have tested and the issue exists on x86 Windows and Linux (AppImage & Flatpak). I'm unable to verify whether the issue presents on Mac as I don't have access to that platform. The error does not occur on 26.04. The UI presents: <img width="820" height="386" alt="Image" src="https://github.com/user-attachments/assets/cbcbbb7b-8a9a-47b7-9a61-fccd911903b7" /> When ran from bash, both the Flatpak and Appimage produce the following error: ``` "Server Log: TypeError: fetch failed at node:internal/deps/undici/undici:14902:13 at process.processTicksAndRejections (node:internal/process/task_queues:103:5) at async fetch$1 (/tmp/.mount_Actual6PJ4Lt/resources/app.asar/build/loot-core/lib-dist/electron/bundle.desktop.js:61883:10) at async needsBootstrap (/tmp/.mount_Actual6PJ4Lt/resources/app.asar/build/loot-core/lib-dist/electron/bundle.desktop.js:112078:13) { [cause]: Error: unable to get local issuer certificate at TLSSocket.onConnectSecure (node:_tls_wrap:1697:34) at TLSSocket.emit (node:events:519:28) at TLSSocket._finishInit (node:_tls_wrap:1095:8) at ssl.onhandshakedone (node:_tls_wrap:881:12) { code: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY' } }" ``` ### How can we reproduce the issue? 1. Open the Actual desktop app and attempt to configure a server that uses a self-signed/non-public CA 2. Be greeted by the self-signed error message 3. Click the link to add a certificate - error message disappears 4. Click Start - error message reappears ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Desktop App (Electron) ### Operating System Linux
GiteaMirror added the electronbug labels 2026-05-19 04:25:42 -05:00
Author
Owner

@tjmills-dev commented on GitHub (May 4, 2026):

You can also pass NODE_TLS_REJECT_UNAUTHORIZED=0 as an env var and that lets you connect, although comes with the obvious security risks

<!-- gh-comment-id:4372560750 --> @tjmills-dev commented on GitHub (May 4, 2026): You can also pass `NODE_TLS_REJECT_UNAUTHORIZED=0` as an env var and that lets you connect, although comes with the obvious security risks
Author
Owner

@sauravchoudhury007 commented on GitHub (May 4, 2026):

I can't even rollback to 26.04. I get the following error and it doesn't let me use it.

Image
<!-- gh-comment-id:4373537391 --> @sauravchoudhury007 commented on GitHub (May 4, 2026): I can't even rollback to 26.04. I get the following error and it doesn't let me use it. <img width="556" height="331" alt="Image" src="https://github.com/user-attachments/assets/3b81d91c-bfd2-495e-87fc-f5117bf7095a" />
Author
Owner

@MikesGlitch commented on GitHub (May 4, 2026):

I have a fix, can someone help us verify it works?

You can download the relevant installers here: https://github.com/actualbudget/actual/actions/runs/25337706776

<!-- gh-comment-id:4373781575 --> @MikesGlitch commented on GitHub (May 4, 2026): I have a fix, can someone help us verify it works? You can download the relevant installers here: https://github.com/actualbudget/actual/actions/runs/25337706776
Author
Owner

@sauravchoudhury007 commented on GitHub (May 4, 2026):

Worked for me. No errors.

<!-- gh-comment-id:4373848793 --> @sauravchoudhury007 commented on GitHub (May 4, 2026): Worked for me. No errors.
Author
Owner

@dpantaz commented on GitHub (May 5, 2026):

fixed it for me as well! thank you!

<!-- gh-comment-id:4377924448 --> @dpantaz commented on GitHub (May 5, 2026): fixed it for me as well! thank you!
Author
Owner

@RealGandy commented on GitHub (May 5, 2026):

Can confirm this fixes the issue for me on Windows x64 platform.

<!-- gh-comment-id:4377925782 --> @RealGandy commented on GitHub (May 5, 2026): Can confirm this fixes the issue for me on Windows x64 platform.
Author
Owner

@MikesGlitch commented on GitHub (May 7, 2026):

Will be fixed on next release (next day or so)

<!-- gh-comment-id:4401205787 --> @MikesGlitch commented on GitHub (May 7, 2026): Will be fixed on next release (next day or so)
Author
Owner

@erikhuizinga commented on GitHub (May 8, 2026):

Thanks for the report and the fix. I decided this was a good time to say goodbye to the desktop app and adopt a web app first approach. Let's see if it stands the test of time... Just leaving this here in case it brings anyone to an idea.

<!-- gh-comment-id:4409489319 --> @erikhuizinga commented on GitHub (May 8, 2026): Thanks for the report and the fix. I decided this was a good time to say goodbye to the desktop app and adopt a web app first approach. Let's see if it stands the test of time... Just leaving this here in case it brings anyone to an idea.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#80603