[GH-ISSUE #7696] [Bug]: There was an unrecoverable error in the UI. Sorry! #117549

Closed
opened 2026-06-11 12:48:44 -05:00 by GiteaMirror · 12 comments
Owner

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

What happened?

Updated to lasted docker actual server image
Go to the site and get error.
There was an unrecoverable error in the UI. Sorry!
Console shows
Object { name: "TypeError", message: "crypto.randomUUID is not a function", stack:
I had previously when first installed gone to the advanced and turn off the security setting

How can we reproduce the issue?

I just updated in docker to the lasted (Running on a QNAP) . I have tried Firefox Chrome and Safari same error.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Mac OSX

Originally created by @yrubdarb on GitHub (May 4, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7696 ### What happened? Updated to lasted docker actual server image Go to the site and get error. There was an unrecoverable error in the UI. Sorry! Console shows Object { name: "TypeError", message: "crypto.randomUUID is not a function", stack: I had previously when first installed gone to the advanced and turn off the security setting ### How can we reproduce the issue? I just updated in docker to the lasted (Running on a QNAP) . I have tried Firefox Chrome and Safari same error. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox ### Operating System Mac OSX
GiteaMirror added the bug label 2026-06-11 12:48:44 -05:00
Author
Owner

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

Hi there,

same situation, using latest version (docker version) and got these error:

TypeError: crypto.randomUUID is not a function at http://x.x.x.x:xxxx/static/js/extends.RRv7gyle.chunk.js:5062:21 at new Promise () at send (http://x.x.x.x:xxxx/static/js/extends.RRv7gyle.chunk.js:5061:9) at init$1 (http://x.x.x.x:xxxx/static/js/index.BFVNfkrn.js:62943:30) at async Promise.all (index 1) at async initAll (http://x.x.x.x:x/static/js/index.BFVNfkrn.js:62956:5)

<!-- gh-comment-id:4369072454 --> @huudafakk commented on GitHub (May 4, 2026): Hi there, same situation, using latest version (docker version) and got these error: TypeError: crypto.randomUUID is not a function at http://x.x.x.x:xxxx/static/js/extends.RRv7gyle.chunk.js:5062:21 at new Promise (<anonymous>) at send (http://x.x.x.x:xxxx/static/js/extends.RRv7gyle.chunk.js:5061:9) at init$1 (http://x.x.x.x:xxxx/static/js/index.BFVNfkrn.js:62943:30) at async Promise.all (index 1) at async initAll (http://x.x.x.x:x/static/js/index.BFVNfkrn.js:62956:5)
Author
Owner

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

See https://actualbudget.org/docs/config/https/. You need to configure HTTPS properly to access Actual from anything other than localhost.

<!-- gh-comment-id:4369197951 --> @emiltb commented on GitHub (May 4, 2026): See https://actualbudget.org/docs/config/https/. You need to configure HTTPS properly to access Actual from anything other than `localhost`.
Author
Owner

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

Is this now enforce more in the latest version because it has been working fine for months?
added the config.json and the cert and key and is working now thanks

<!-- gh-comment-id:4369311368 --> @yrubdarb commented on GitHub (May 4, 2026): Is this now enforce more in the latest version because it has been working fine for months? added the config.json and the cert and key and is working now thanks
Author
Owner

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

fixed using tailscale with the https/magic dns service, works again like charm. thank you!

<!-- gh-comment-id:4369523175 --> @huudafakk commented on GitHub (May 4, 2026): fixed using tailscale with the https/magic dns service, works again like charm. thank you!
Author
Owner

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

fixed using tailscale with the https/magic dns service, works again like charm. thank you!

Can I ask how you did this? My tailscale install kind of broke.

edit: What I did to fix my Tailscale was (accidentally) resetting my configuration and then re-adding it. It seemed to work then.

<!-- gh-comment-id:4375452230 --> @MattDemers commented on GitHub (May 4, 2026): > fixed using tailscale with the https/magic dns service, works again like charm. thank you! Can I ask how you did this? My tailscale install kind of broke. **edit**: What I did to fix my Tailscale was (accidentally) resetting my configuration and then re-adding it. It seemed to work then.
Author
Owner

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

@emiltb @youngcw this is kind of breaking the flow for many self-hosters who access their Actual instance via internal IP. Wouldn't it have been appropriate at least to mention this, anywhere in any changelog/release notes/upcoming plans?
I don't mean to sound entitled, honestly thanks all for the hard work on a free software.

<!-- gh-comment-id:4379688724 --> @manolof commented on GitHub (May 5, 2026): @emiltb @youngcw this is kind of breaking the flow for many self-hosters who access their Actual instance via internal IP. Wouldn't it have been appropriate at least to mention this, anywhere in any changelog/release notes/upcoming plans? I don't mean to sound entitled, honestly thanks all for the hard work on a free software.
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:4380402756 --> @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

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

See https://actualbudget.org/docs/config/https/. You need to configure HTTPS properly to access Actual from anything other than localhost.

No.

<!-- gh-comment-id:4397767690 --> @boltadvantage commented on GitHub (May 7, 2026): > See https://actualbudget.org/docs/config/https/. You need to configure HTTPS properly to access Actual from anything other than `localhost`. No.
Author
Owner

@StevenLares commented on GitHub (May 10, 2026):

I self-host through Docker, keep it local (and only remotely access through Tailscale)

If that sounds like you, I suggest pinning sha-353e12a in your Docker Compose.

Unacceptable that this flow was broken without warning, and coincidentally around the time of the first AI push: https://slopwatch.dev/repo/actualbudget/actual

<!-- gh-comment-id:4415724371 --> @StevenLares commented on GitHub (May 10, 2026): I self-host through Docker, keep it local (and only remotely access through Tailscale) If that sounds like you, I suggest pinning sha-353e12a in your Docker Compose. Unacceptable that this flow was broken without warning, and coincidentally around the time of the first AI push: https://slopwatch.dev/repo/actualbudget/actual
Author
Owner

@pwinnski commented on GitHub (May 12, 2026):

What a weird hill to expose your personal financial data on. This isn't a media server, HTTPS should be considered a bare minimum. As the documentation says, if you already have Tailscale, you can use that, so you don't even need to use your own cert.

If you're really that determined to run insecurely, you can make up for using https://zzz.tailzzz.ts.net/ by printing out your bank statements and leaving them lying about, I suppose. 🤷

<!-- gh-comment-id:4430244469 --> @pwinnski commented on GitHub (May 12, 2026): What a weird hill to expose your personal financial data on. This isn't a media server, HTTPS should be considered a bare minimum. As the documentation says, if you already have Tailscale, you can use that, so you don't even need to use your own cert. If you're really that determined to run insecurely, you can make up for using https://zzz.tailzzz.ts.net/ by printing out your bank statements and leaving them lying about, I suppose. 🤷
Author
Owner

@manolof commented on GitHub (May 12, 2026):

What a weird hill to expose your personal financial data on. This isn't a media server, HTTPS should be considered a bare minimum. As the documentation says, if you already have Tailscale, you can use that, so you don't even need to use your own cert.

If you're really that determined to run insecurely, you can make up for using https://zzz.tailzzz.ts.net/ by printing out your bank statements and leaving them lying about, I suppose. 🤷

didn't fully get your response, but hey, Actual only stores numbers AFAIK, and 0 bank statements.. you're confusing it with Paperless-ngx...
And no thanks, I don't need an open-source software targeted towards self-hosters to dictate how to run my software on my own server under my desk...

<!-- gh-comment-id:4430284724 --> @manolof commented on GitHub (May 12, 2026): > What a weird hill to expose your personal financial data on. This isn't a media server, HTTPS should be considered a bare minimum. As the documentation says, if you already have Tailscale, you can use that, so you don't even need to use your own cert. > > If you're really that determined to run insecurely, you can make up for using https://zzz.tailzzz.ts.net/ by printing out your bank statements and leaving them lying about, I suppose. 🤷 didn't fully get your response, but hey, Actual only stores numbers AFAIK, and 0 bank statements.. you're confusing it with Paperless-ngx... And no thanks, I don't need an open-source software targeted towards self-hosters to dictate how to run my software on my own server under my desk...
Author
Owner

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

This is getting unnecessarily heated. The patch has been merged and released in 26.5.1 / 26.5.2.

Locking.

<!-- gh-comment-id:4430319356 --> @MatissJanis commented on GitHub (May 12, 2026): This is getting unnecessarily heated. The patch has been merged and released in 26.5.1 / 26.5.2. Locking.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#117549