[GH-ISSUE #6856] [Bug]: "Enable Encryption" button disabled in Desktop App despite HTTPS (Self-Signed Cert) #52014

Closed
opened 2026-04-30 20:06:54 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @CSBailey on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6856

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I am hosting Actual Server via Docker with HTTPS enabled using a self-signed certificate. In Safari: Actual loads using https and my server address, shows a valid connection, and the "Enable Encryption" button in settings is functional.

However, in the Desktop App, the app connects to the server successfully via https, but the "Enable Encryption" button is greyed out.

It appears the Desktop App does not recognize the connection as a "Secure Context".

MacOS 26.2
Actual Client and Server version: v26.2.0

How can we reproduce the issue?

  1. Set up Actual Server using Docker image with a self-signed HTTPS certificate.
  2. Access via Safari: Observe that "Enable Encryption" is available.
  3. Access via Desktop App: Observe that the UI loads, but "Enable Encryption" remains disabled/greyed out.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Safari

Operating System

Mac OSX

Originally created by @CSBailey on GitHub (Feb 4, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/6856 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I am hosting Actual Server via Docker with HTTPS enabled using a self-signed certificate. In Safari: Actual loads using https and my server address, shows a valid connection, and the "Enable Encryption" button in settings is functional. However, in the Desktop App, the app connects to the server successfully via https, but the "Enable Encryption" button is greyed out. It appears the Desktop App does not recognize the connection as a "Secure Context". MacOS 26.2 Actual Client and Server version: v26.2.0 ### How can we reproduce the issue? 1. Set up Actual Server using Docker image with a self-signed HTTPS certificate. 2. Access via Safari: Observe that "Enable Encryption" is available. 3. Access via Desktop App: Observe that the UI loads, but "Enable Encryption" remains disabled/greyed out. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Safari ### Operating System Mac OSX
GiteaMirror added the electrongood first issuebug labels 2026-04-30 20:06:55 -05:00
Author
Owner

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

Hi.

Can confirm, this isn't working on Desktop App - definite bug. It's because the app doesn't have the crypto.subtle module for some reason, so it can't encrypt.

For whoever wants to pick this up, it'll be a matter of figuring out why crypto.subtle isn't available.

Side note: We highly discourage using the desktop app when you use an external server. We document the reasons here: https://actualbudget.org/docs/install/desktop-app#who-shouldnt-use-the-desktop-app

Basically it's to do with version mismatches. If you use the PWA instead, you get a desktop experience, avoid version mismatches and encryption should also work.

<!-- gh-comment-id:3849379066 --> @MikesGlitch commented on GitHub (Feb 4, 2026): Hi. Can confirm, this isn't working on Desktop App - definite bug. It's because the app doesn't have the `crypto.subtle` module for some reason, so it can't encrypt. For whoever wants to pick this up, it'll be a matter of figuring out why crypto.subtle isn't available. Side note: We highly discourage using the desktop app when you use an external server. We document the reasons here: https://actualbudget.org/docs/install/desktop-app#who-shouldnt-use-the-desktop-app Basically it's to do with version mismatches. If you use the PWA instead, you get a desktop experience, avoid version mismatches and encryption should also work.
Author
Owner

@wtsiamruk commented on GitHub (Apr 3, 2026):

looks like crypto.subtle can be missing on custom protocol without secure config

https://www.electronjs.org/docs/latest/api/protocol

Trying to verify it in https://github.com/actualbudget/actual/pull/7368

<!-- gh-comment-id:4181922583 --> @wtsiamruk commented on GitHub (Apr 3, 2026): looks like crypto.subtle can be missing on custom protocol without secure config https://www.electronjs.org/docs/latest/api/protocol Trying to verify it in https://github.com/actualbudget/actual/pull/7368
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#52014