[GH-ISSUE #7715] [Bug]: TypeError: crypto.randomUUID is not a function #80611

Closed
opened 2026-05-19 04:26:33 -05:00 by GiteaMirror · 13 comments
Owner

Originally created by @MrClassicT on GitHub (May 4, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7715

What happened?

I was trying to login on the latest version of actual (in my sandbox env, just a new setup)
Expected: To see the login/start screen where I can select my desired "save" of finance data.
Actual: Error screen with 'TypeError: crypto.randomUUID is not a function'

Image

Error:
Fatal Error
There was an unrecoverable error in the UI. Sorry!
If this error persists, please get in touch so it can be investigated.
Restart app
Show Error
TypeError: crypto.randomUUID is not a function at http://localip:5007/static/js/extends.RRv7gyle.chunk.js:5062:21 at new Promise () at send (http://localip:5007/static/js/extends.RRv7gyle.chunk.js:5061:9) at init$1 (http://localip:5007/static/js/index.BFVNfkrn.js:62943:30) at async Promise.all (index 1) at async initAll (http://localip:5007/static/js/index.BFVNfkrn.js:62956:5)

Image

How can we reproduce the issue?

Deploy version 26.5.0, through Coolify locally hosted on linux machine. Client is Macbook pro with M1 chip. (though that should not be relevant I think?)
Open the webpage
We see the error

If we roll back to version 26.4.0, the issue is not there.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Mac OSX

Originally created by @MrClassicT on GitHub (May 4, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7715 ### What happened? I was trying to login on the latest version of actual (in my sandbox env, just a new setup) Expected: To see the login/start screen where I can select my desired "save" of finance data. Actual: Error screen with 'TypeError: crypto.randomUUID is not a function' <img width="728" height="482" alt="Image" src="https://github.com/user-attachments/assets/e0314834-8642-43e2-8b62-dce44b65c08e" /> Error: Fatal Error There was an unrecoverable error in the UI. Sorry! If this error persists, please get [in touch](https://actualbudget.org/contact) so it can be investigated. Restart app Show Error TypeError: crypto.randomUUID is not a function at http://localip:5007/static/js/extends.RRv7gyle.chunk.js:5062:21 at new Promise (<anonymous>) at send (http://localip:5007/static/js/extends.RRv7gyle.chunk.js:5061:9) at init$1 (http://localip:5007/static/js/index.BFVNfkrn.js:62943:30) at async Promise.all (index 1) at async initAll (http://localip:5007/static/js/index.BFVNfkrn.js:62956:5) <img width="2608" height="1134" alt="Image" src="https://github.com/user-attachments/assets/c8b9ec1f-1152-4352-b310-976074ec214e" /> ### How can we reproduce the issue? Deploy version 26.5.0, through Coolify locally hosted on linux machine. Client is Macbook pro with M1 chip. (though that should not be relevant I think?) Open the webpage *We see the error* If we roll back to version 26.4.0, the issue is not there. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Mac OSX
GiteaMirror added the bug label 2026-05-19 04:26:33 -05:00
Author
Owner

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

I'm open to provide more info/help debug where needed. I'm also in the Discord server, so feel free to shoot me a message through the channels there if that would be easier.

<!-- gh-comment-id:4374171993 --> @MrClassicT commented on GitHub (May 4, 2026): I'm open to provide more info/help debug where needed. I'm also in the Discord server, so feel free to shoot me a message through the channels there if that would be easier.
Author
Owner

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

Setup https. See #7696

<!-- gh-comment-id:4374175711 --> @youngcw commented on GitHub (May 4, 2026): Setup https. See #7696
Author
Owner

@coderabbitai[bot] commented on GitHub (May 4, 2026):

⚠️ Possible Duplicate Issue(s)

📝 Issue Planner

Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

  • Create Plan

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

<!-- gh-comment-id:4374181008 --> @coderabbitai[bot] commented on GitHub (May 4, 2026): <!-- This is an auto-generated issue plan by CodeRabbit --> <details> <summary>⚠️ Possible Duplicate Issue(s)</summary> - https://github.com/actualbudget/actual/issues/7708 </details> --- <details> <summary>📝 Issue Planner</summary> <sub>Check the box below or use the `@coderabbitai plan` command to generate an implementation plan and prompts that you can use with your favorite coding assistant.</sub> - [ ] <!-- {"checkboxId": "8d4f2b9c-3e1a-4f7c-a9b2-d5e8f1c4a7b9"} --> Create Plan </details> --- <details> <summary> 🧪 Issue enrichment is currently in open beta.</summary> You can configure auto-planning by selecting labels in the issue_enrichment configuration. To disable automatic issue enrichment, add the following to your `.coderabbit.yaml`: ```yaml issue_enrichment: auto_enrich: enabled: false ``` </details> 💬 Have feedback or questions? Drop into our [discord](https://discord.gg/coderabbit)!
Author
Owner

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

I'll re-open this issue so we stop getting the duplicates.

A discussion thread on discord: https://discord.com/channels/937901803608096828/1500590121362133164/1500590121362133164

TLDR: we should do something about this. Maybe swap back to a UUID lib that is usable outside secure context or a polyfill. Either way we shouldn't let the app blow up like this.

<!-- gh-comment-id:4374273057 --> @MatissJanis commented on GitHub (May 4, 2026): I'll re-open this issue so we stop getting the duplicates. A discussion thread on discord: https://discord.com/channels/937901803608096828/1500590121362133164/1500590121362133164 TLDR: we should do something about this. Maybe swap back to a UUID lib that is usable outside secure context or a polyfill. Either way we shouldn't let the app blow up like this.
Author
Owner

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

I got the same error. Installed 26.4.0 and it now works again.

I really don't want to run HTTPS on my completely local instance of Actual that is running as Docker on Synology NAS. I'm not sure if I can even do HTTPS. This is a SHOWSTOPPER for me with versison 26.5.0.

<!-- gh-comment-id:4381006614 --> @Jeff9000 commented on GitHub (May 5, 2026): I got the same error. Installed 26.4.0 and it now works again. I really don't want to run HTTPS on my completely local instance of Actual that is running as Docker on Synology NAS. I'm not sure if I can even do HTTPS. This is a SHOWSTOPPER for me with versison 26.5.0.
Author
Owner

@Dare2Code commented on GitHub (May 6, 2026):

Same goes for me, am running this as an add-on in Home Assistant (Raspberry PI) completely local. not sure if HTTPS is supported when someone like me is using Nabu.casa.

<!-- gh-comment-id:4391942914 --> @Dare2Code commented on GitHub (May 6, 2026): Same goes for me, am running this as an add-on in Home Assistant (Raspberry PI) completely local. not sure if HTTPS is supported when someone like me is using Nabu.casa.
Author
Owner

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

@Jeff9000 i was having the same issue but followed the instructions for self-signed certs. It still wasn't working until I realized that an ip address in my address bar is defaulting to http. As soon as I put in https it started working. No need for any DNS/proxy etc with the self-signed certs.

<!-- gh-comment-id:4397754500 --> @Normanras commented on GitHub (May 7, 2026): @Jeff9000 i was having the same issue but followed [the instructions for self-signed certs](https://actualbudget.org/docs/config/https). It still wasn't working until I realized that an ip address in my address bar is defaulting to `http`. As soon as I put in `https` it started working. No need for any DNS/proxy etc with the self-signed certs.
Author
Owner

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

Oh, wow, can you please give us exactly what you've done. Am using
nabu.case so my setup and instructions were not all aligning and there. TBH.
Many Thanks in advance..

Regards,
Sri

On Thu, 7 May 2026 at 09:57, Norm @.***> wrote:

Normanras left a comment (actualbudget/actual#7715)
https://github.com/actualbudget/actual/issues/7715#issuecomment-4397754500

@Jeff9000 https://github.com/Jeff9000 i was having the same issue but
followed the instructions for self-signed certs
https://actualbudget.org/docs/config/https. It still wasn't working
until I realized that an ip address in my address bar is defaulting to
http. As soon as I put in https it started working. No need for any
DNS/proxy etc with the self-signed certs.


Reply to this email directly, view it on GitHub
https://github.com/actualbudget/actual/issues/7715#issuecomment-4397754500,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVY2Z4HNSA25JGV5G43PLL4ZSI6FAVCNFSM6AAAAACYQUW342VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGOJXG42TINJQGA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you are subscribed to this thread.Message
ID: @.***>

<!-- gh-comment-id:4398064547 --> @Dare2Code commented on GitHub (May 7, 2026): Oh, wow, can you please give us exactly what you've done. Am using nabu.case so my setup and instructions were not all aligning and there. TBH. Many Thanks in advance.. Regards, Sri On Thu, 7 May 2026 at 09:57, Norm ***@***.***> wrote: > *Normanras* left a comment (actualbudget/actual#7715) > <https://github.com/actualbudget/actual/issues/7715#issuecomment-4397754500> > > @Jeff9000 <https://github.com/Jeff9000> i was having the same issue but > followed the instructions for self-signed certs > <https://actualbudget.org/docs/config/https>. It still wasn't working > until I realized that an ip address in my address bar is defaulting to > http. As soon as I put in https it started working. No need for any > DNS/proxy etc with the self-signed certs. > > — > Reply to this email directly, view it on GitHub > <https://github.com/actualbudget/actual/issues/7715#issuecomment-4397754500>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAVY2Z4HNSA25JGV5G43PLL4ZSI6FAVCNFSM6AAAAACYQUW342VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGOJXG42TINJQGA> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >
Author
Owner

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

I don't know exactly how it works with nabu.casa, but I am leveraging https just for running this on my internal network. Here's how I did it:

  1. In my data directory, I ran: openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout selfhost.key -out selfhost.crt
  2. Ran ls to confirm that the two files (selfhost.key and selfhost.crt) were there.
  3. In my docker-compose.yml I added the following:
    environment:
       - ACTUAL_HTTPS_KEY=/data/selfhost.key
       - ACTUAL_HTTPS_CERT=/data/selfhost.crt
...
    healthcheck:
      test: ['CMD-SHELL', 'NODE_EXTRA_CA_CERTS=/data/selfhost.crt node src/scripts/health-check.js']
  1. Then pull the container down and back up.

Then you should be able to access your actual instance at https://ip-address:5006. Trying to access it with http:// resulted in a 502 error.

<!-- gh-comment-id:4398644346 --> @Normanras commented on GitHub (May 7, 2026): I don't know exactly how it works with nabu.casa, but I am leveraging https just for running this on my internal network. Here's how I did it: 1. In my data directory, I ran: `openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout selfhost.key -out selfhost.crt` 2. Ran `ls` to confirm that the two files (`selfhost.key` and `selfhost.crt`) were there. 3. In my `docker-compose.yml` I added the following: ``` environment: - ACTUAL_HTTPS_KEY=/data/selfhost.key - ACTUAL_HTTPS_CERT=/data/selfhost.crt ... healthcheck: test: ['CMD-SHELL', 'NODE_EXTRA_CA_CERTS=/data/selfhost.crt node src/scripts/health-check.js'] ``` 4. Then pull the container down and back up. Then you should be able to access your actual instance at `https://ip-address:5006`. Trying to access it with `http://` resulted in a 502 error.
Author
Owner

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

@Normanras Do you know how I would do that when my Docker is running in a Synology NAS. I am hoping not to use SSH into Linux because I really don't know Linux. I'm using Portainer to manage my Dockers.

<!-- gh-comment-id:4398766149 --> @Jeff9000 commented on GitHub (May 7, 2026): @Normanras Do you know how I would do that when my Docker is running in a Synology NAS. I am hoping not to use SSH into Linux because I really don't know Linux. I'm using Portainer to manage my Dockers.
Author
Owner

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

v26.5.1 will fix this. You can either wait for that to be released or upgrade directly to edge (though that will pull in some more changes that might not have been fully vetted yet).

<!-- gh-comment-id:4401141932 --> @MatissJanis commented on GitHub (May 7, 2026): [v26.5.1](https://github.com/actualbudget/actual/pull/7745) will fix this. You can either wait for that to be released or upgrade directly to `edge` (though that will pull in some more changes that might not have been fully vetted yet).
Author
Owner

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

@MatissJanis Thanks to @Normanras posts above I was able to easily get the self certs working. Thanks!

<!-- gh-comment-id:4407698145 --> @Jeff9000 commented on GitHub (May 8, 2026): @MatissJanis Thanks to @Normanras posts above I was able to easily get the self certs working. Thanks!
Author
Owner

@MatissJanis commented on GitHub (May 9, 2026):

v26.5.1 / v26.5.2 is released with the patch

<!-- gh-comment-id:4413587818 --> @MatissJanis commented on GitHub (May 9, 2026): v26.5.1 / v26.5.2 is released with the patch
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#80611