[Bug]: #2282

Closed
opened 2026-02-28 20:08:53 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @TomzBench on GitHub (Jul 15, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When I enable HTTPS, I would expect the HTTP protocol to be redirected to HTTPS, or the HTTP connection rejected. Currently, enabling HTTPS simply allows for both HTTP and HTTPS protocols over the same port.

How can we reproduce the issue?

install a self signed cert and open a browser to https://127.0.0.1:5006 and http://127.0.0.1:5006. There is no redirect and both pages are served.

(Logs incase i missed something)

12:49 $ ./node_modules/.bin/actual-server --config ~/.config/actual.json
Loading config from /home/thomas/.config/actual.json
Found existing data directory
Data directory: /home/thomas/Git/actual/data
  actual:config Project root: '/home/thomas/Git/actual/packages/sync-server' +0ms
  actual:config Actual web build path: '/home/thomas/Git/actual/packages/desktop-client/build' +1ms
  actual:config loading config from ACTUAL_CONFIG_PATH: '/home/thomas/.config/actual.json' +5ms
  actual:config Config loaded +1ms
  actual:config Validating config +1ms
  actual:config Project root: /home/thomas/Git/actual/packages/sync-server +1ms
  actual:config Port: 5006 +0ms
  actual:config Hostname: :: +0ms
  actual:config Data directory: /home/thomas/Git/actual/data +0ms
  actual:config Server files: /home/thomas/Git/actual/data/server-files +0ms
  actual:config User files: /home/thomas/Git/actual/data/user-files +0ms
  actual:config Web root: /home/thomas/Git/actual/packages/desktop-client/build +0ms
  actual:config Login method: password +0ms
  actual:config Allowed methods: password, header, openid +1ms
  actual:config HTTPS Key: **************************** +0ms
  actual:config HTTPS Cert: **************************** +0ms

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @TomzBench on GitHub (Jul 15, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? When I enable HTTPS, I would expect the HTTP protocol to be redirected to HTTPS, or the HTTP connection rejected. Currently, enabling HTTPS simply allows for both HTTP and HTTPS protocols over the same port. ### How can we reproduce the issue? install a self signed cert and open a browser to https://127.0.0.1:5006 and http://127.0.0.1:5006. There is no redirect and both pages are served. (Logs incase i missed something) ``` 12:49 $ ./node_modules/.bin/actual-server --config ~/.config/actual.json Loading config from /home/thomas/.config/actual.json Found existing data directory Data directory: /home/thomas/Git/actual/data actual:config Project root: '/home/thomas/Git/actual/packages/sync-server' +0ms actual:config Actual web build path: '/home/thomas/Git/actual/packages/desktop-client/build' +1ms actual:config loading config from ACTUAL_CONFIG_PATH: '/home/thomas/.config/actual.json' +5ms actual:config Config loaded +1ms actual:config Validating config +1ms actual:config Project root: /home/thomas/Git/actual/packages/sync-server +1ms actual:config Port: 5006 +0ms actual:config Hostname: :: +0ms actual:config Data directory: /home/thomas/Git/actual/data +0ms actual:config Server files: /home/thomas/Git/actual/data/server-files +0ms actual:config User files: /home/thomas/Git/actual/data/user-files +0ms actual:config Web root: /home/thomas/Git/actual/packages/desktop-client/build +0ms actual:config Login method: password +0ms actual:config Allowed methods: password, header, openid +1ms actual:config HTTPS Key: **************************** +0ms actual:config HTTPS Cert: **************************** +0ms ``` ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the bug label 2026-02-28 20:08:53 -06:00
Author
Owner

@TomzBench commented on GitHub (Jul 15, 2025):

Unsecure connection was from Cache and marked as offline. Woops

@TomzBench commented on GitHub (Jul 15, 2025): Unsecure connection was from Cache and marked as offline. Woops
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2282