SharedArrayBuffer and HTTPS #264

Closed
opened 2026-02-28 18:54:43 -06:00 by GiteaMirror · 10 comments
Owner

Originally created by @Marcus-Schubert on GitHub (Feb 5, 2023).

Hey there,

I'm currently running actual server in a local network on HTTP via Docker. Since the latest update (23.2.5), I get the SharedArrayBuffer info page and can't access my actual server instance.

When looking into the documentation, it says that actual requires SharedArrayBuffer and that HTTPS is required for SharedArrayBuffer.

Does this mean, actual server will no longer work with HTTP but only HTTPS?

Originally created by @Marcus-Schubert on GitHub (Feb 5, 2023). Hey there, I'm currently running actual server in a local network on HTTP via Docker. Since the latest update (23.2.5), I get the SharedArrayBuffer info page and can't access my actual server instance. When looking into the [documentation](https://actualbudget.github.io/docs/Troubleshooting/SharedArrayBuffer/), it says that actual requires SharedArrayBuffer and that HTTPS is required for SharedArrayBuffer. Does this mean, actual server will no longer work with HTTP but only HTTPS?
Author
Owner

@j-f1 commented on GitHub (Feb 5, 2023):

Except when you’re running on localhost, we do require HTTPS now. This is a limitation imposed by browsers — things appeared to work OK in the past but our database layer had bugs when SharedArrayBuffer wasn’t supported, resulting in budgets being merged if you had multiple files, and probably other issues too.

@j-f1 commented on GitHub (Feb 5, 2023): Except when you’re running on localhost, we do require HTTPS now. This is a limitation imposed by browsers — things appeared to work OK in the past but our database layer had bugs when `SharedArrayBuffer` wasn’t supported, resulting in budgets being merged if you had multiple files, and probably other issues too.
Author
Owner

@Marcus-Schubert commented on GitHub (Feb 5, 2023):

Thank you for the quick response. I guess I will switch to HTTPS now 👍

@Marcus-Schubert commented on GitHub (Feb 5, 2023): Thank you for the quick response. I guess I will switch to HTTPS now :+1:
Author
Owner

@hofq commented on GitHub (Feb 6, 2023):

@j-f1
Edit: My first comment is obsolete (i think) because i haven't looked into this enough.
Could you make configuration via Environment Variables Possible? At least the HTTPS one since you can't add specific files to an Unraid Deployment unless you rebuild the image. Alternatively 2 Seperate Ports, like some other apps do, would also be fine for me

@hofq commented on GitHub (Feb 6, 2023): @j-f1 Edit: My first comment is obsolete (i think) because i haven't looked into this enough. Could you make configuration via Environment Variables Possible? At least the HTTPS one since you can't add specific files to an Unraid Deployment unless you rebuild the image. Alternatively 2 Seperate Ports, like some other apps do, would also be fine for me
Author
Owner

@j-f1 commented on GitHub (Feb 6, 2023):

Could you make configuration via Environment Variables Possible? At least the HTTPS one since you can't add specific files to an Unraid Deployment unless you rebuild the image

Yep! In the latest version (not tagged yet, but you can use edge for now) you can specify ACTUAL_HTTPS_KEY and ACTUAL_HTTPS_CERT environment variables with the path to the key or the key content itself. See the updated config docs which will hopefully be merged soon

@j-f1 commented on GitHub (Feb 6, 2023): > Could you make configuration via Environment Variables Possible? At least the HTTPS one since you can't add specific files to an Unraid Deployment unless you rebuild the image Yep! In the latest version (not tagged yet, but you can use `edge` for now) you can specify `ACTUAL_HTTPS_KEY` and `ACTUAL_HTTPS_CERT` environment variables with the path to the key or the key content itself. See [the updated config docs](https://deploy-preview-96--zingy-bonbon-b1b286.netlify.app/Installing/Configuration) which will hopefully be merged soon
Author
Owner

@hofq commented on GitHub (Feb 7, 2023):

Does it automatically generate self signed certs or do you have to do it yourself?

@hofq commented on GitHub (Feb 7, 2023): Does it automatically generate self signed certs or do you have to do it yourself?
Author
Owner

@j-f1 commented on GitHub (Feb 7, 2023):

You’ll have to do that yourself (partially because we didn’t implement that functionality, partially because I don’t want people to get used to clicking through certificate errors). It might be nice to have a tool to do that automatically somehow though!

@j-f1 commented on GitHub (Feb 7, 2023): You’ll have to do that yourself (partially because we didn’t implement that functionality, partially because I don’t want people to get used to clicking through certificate errors). It might be nice to have a tool to do that automatically somehow though!
Author
Owner

@MatissJanis commented on GitHub (Feb 9, 2023):

We have added a way to bypass this error in version 23.2.9. Please use it at your own risk.

@MatissJanis commented on GitHub (Feb 9, 2023): We have added a way to bypass this error in version 23.2.9. Please use it at your own risk.
Author
Owner

@Presjar commented on GitHub (Mar 7, 2023):

I use traefik2 to generate certificates for each of my services. Is anyone else using traefik for similar so they can access for example https://actual.foobar.com ? I could see that enabling https on actual would perhaps conflict with the https of traefik? But to stop the SharedArrayBuffer issue I need to enable https in Actual?

@Presjar commented on GitHub (Mar 7, 2023): I use traefik2 to generate certificates for each of my services. Is anyone else using traefik for similar so they can access for example https://actual.foobar.com ? I could see that enabling https on actual would perhaps conflict with the https of traefik? But to stop the SharedArrayBuffer issue I need to enable https in Actual?
Author
Owner

@j-f1 commented on GitHub (Mar 7, 2023):

You don’t need to enable HTTPS in Actual itself, as long as you have something adding HTTPS between you and the server.

@j-f1 commented on GitHub (Mar 7, 2023): You don’t need to enable HTTPS in Actual itself, as long as you have something adding HTTPS between you and the server.
Author
Owner

@Presjar commented on GitHub (Mar 7, 2023):

Oh great! This should work easily then!
Thanks for letting me know.

On Tue, 7 Mar 2023, 10:51 pm Jed Fox, @.***> wrote:

You don’t need to enable HTTPS in Actual itself, as long as you have
something adding HTTPS between you and the server.


Reply to this email directly, view it on GitHub
https://github.com/actualbudget/actual/issues/637#issuecomment-1458118031,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEKQVK7OIYWEP45BMV442WTW24VMZANCNFSM6AAAAAAUR7AZFA
.
You are receiving this because you commented.Message ID:
@.***>

@Presjar commented on GitHub (Mar 7, 2023): Oh great! This should work easily then! Thanks for letting me know. On Tue, 7 Mar 2023, 10:51 pm Jed Fox, ***@***.***> wrote: > You don’t need to enable HTTPS in Actual itself, as long as you have > something adding HTTPS between you and the server. > > — > Reply to this email directly, view it on GitHub > <https://github.com/actualbudget/actual/issues/637#issuecomment-1458118031>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEKQVK7OIYWEP45BMV442WTW24VMZANCNFSM6AAAAAAUR7AZFA> > . > You are receiving this because you commented.Message ID: > ***@***.***> >
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#264