#752 - [GH-ISSUE #3678] Actual Budget install/update breaks app – missing index.html in desktop-client - starred/ProxmoxVE

kerem commented

2026-02-26 12:46:32 +03:00

Owner

Originally created by @msclp on GitHub (Apr 5, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/3678

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

actual bedget

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/actualbudget.sh)"

📝 Provide a clear and concise description of the issue.

After running the helper script to install or update Actual Budget on a Proxmox container, the application fails to start. When accessing it via browser, the following error is shown:
Error: ENOENT: no such file or directory, stat '/opt/actualbudget/packages/desktop-client/build/index.html'

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Step 1: Install or update actual budget
Step 2: go to the URL of actual budget

❌ Paste the full error output (if available).

Error: ENOENT: no such file or directory, stat '/opt/actualbudget/packages/desktop-client/build/index.html'

🖼️ Additional context (optional).

No response

Originally created by @msclp on GitHub (Apr 5, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/3678 ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? actual bedget ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/actualbudget.sh)" ### 📝 Provide a clear and concise description of the issue. After running the helper script to install or update Actual Budget on a Proxmox container, the application fails to start. When accessing it via browser, the following error is shown: `Error: ENOENT: no such file or directory, stat '/opt/actualbudget/packages/desktop-client/build/index.html'` ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Step 1: Install or update actual budget Step 2: go to the URL of actual budget ### ❌ Paste the full error output (if available). Error: ENOENT: no such file or directory, stat '/opt/actualbudget/packages/desktop-client/build/index.html' ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:46:32 +03:00

closed this issue
added the
bug

external

dependencies
labels

kerem commented

2026-02-26 12:46:32 +03:00

Author

Owner

@msclp commented on GitHub (Apr 5, 2025):

ugh, tha app now requires way more resources, especially ram
giving 8GB of ram fixed the issue, 4GB was not enough

@msclp commented on GitHub (Apr 5, 2025): ugh, tha app now requires way more resources, especially ram giving 8GB of ram fixed the issue, 4GB was not enough

kerem commented

2026-02-26 12:46:32 +03:00

Author

Owner

@dwcorium commented on GitHub (Apr 5, 2025):

For me it doesnt fix it and my had only 2GB

@dwcorium commented on GitHub (Apr 5, 2025): For me it doesnt fix it and my had only 2GB

kerem commented

2026-02-26 12:46:32 +03:00

Author

Owner

@MickLesk commented on GitHub (Apr 5, 2025):

Thats not our issue. We Crawl the full Release File, If this Missing, its an actual issue (Like many other Issues from this Script)

@MickLesk commented on GitHub (Apr 5, 2025): Thats not our issue. We Crawl the full Release File, If this Missing, its an actual issue (Like many other Issues from this Script)

kerem commented

2026-02-26 12:46:32 +03:00

Author

Owner

@dwcorium commented on GitHub (Apr 5, 2025):

ok so i came on to this https://github.com/actualbudget/actual/issues/4746 and after i reupped the ram and followed this it now works could the change of the process on their side have a impact on the script?

@dwcorium commented on GitHub (Apr 5, 2025): ok so i came on to this https://github.com/actualbudget/actual/issues/4746 and after i reupped the ram and followed this it now works could the change of the process on their side have a impact on the script?

kerem commented

2026-02-26 12:46:32 +03:00

Author

Owner

@danluckner commented on GitHub (Apr 5, 2025):

ok so i came on to this actualbudget/actual#4746 and after i reupped the ram and followed this it now works could the change of the process on their side have a impact on the script?

I tried this, but I'm getting this error:

user@actualbudget:/opt/actualbudget/bin# yarn build:server
Updating translations...
./bin/package-browser: line 9: git: command not found

Still can't access my Actual Budget instance.

@danluckner commented on GitHub (Apr 5, 2025): > ok so i came on to this [actualbudget/actual#4746](https://github.com/actualbudget/actual/issues/4746) and after i reupped the ram and followed this it now works could the change of the process on their side have a impact on the script? I tried this, but I'm getting this error: ``` user@actualbudget:/opt/actualbudget/bin# yarn build:server Updating translations... ./bin/package-browser: line 9: git: command not found ``` Still can't access my Actual Budget instance.

kerem commented

2026-02-26 12:46:32 +03:00

Author

Owner

@Rodrigueztb commented on GitHub (Apr 5, 2025):

ok so i came on to this actualbudget/actual#4746 and after i reupped the ram and followed this it now works could the change of the process on their side have a impact on the script?

I tried this, but I'm getting this error:
user@actualbudget:/opt/actualbudget/bin# yarn build:server
Updating translations...
./bin/package-browser: line 9: git: command not found
Still can't access my Actual Budget instance.

Same here. A fresh install in proxmox give me the same error. Installing via docker works okay, Already try to give 8gb and more, but didnt work

@Rodrigueztb commented on GitHub (Apr 5, 2025): > > ok so i came on to this [actualbudget/actual#4746](https://github.com/actualbudget/actual/issues/4746) and after i reupped the ram and followed this it now works could the change of the process on their side have a impact on the script? > > I tried this, but I'm getting this error: > > ``` > user@actualbudget:/opt/actualbudget/bin# yarn build:server > Updating translations... > ./bin/package-browser: line 9: git: command not found > ``` > > Still can't access my Actual Budget instance. Same here. A fresh install in proxmox give me the same error. Installing via docker works okay, Already try to give 8gb and more, but didnt work

kerem commented

2026-02-26 12:46:32 +03:00

Author

Owner

@MickLesk commented on GitHub (Apr 5, 2025):

We dont use git. Then there Release package is broken (once again)

I cant do anything on the Script

@MickLesk commented on GitHub (Apr 5, 2025): We dont use git. Then there Release package is broken (once again) I cant do anything on the Script

kerem commented

2026-02-26 12:46:32 +03:00

Author

Owner

@MickLesk commented on GitHub (Apr 5, 2025):

That is one of the reasons. Which is why we have repeatedly considered removing actualbudget completely. Their releases simply suck. Every time something is defective or something else.

@MickLesk commented on GitHub (Apr 5, 2025): That is one of the reasons. Which is why we have repeatedly considered removing actualbudget completely. Their releases simply suck. Every time something is defective or something else.

kerem commented

2026-02-26 12:46:32 +03:00

Author

Owner

@danluckner commented on GitHub (Apr 5, 2025):

I also spun up a Docker LXC and used the docker version of Actual budget, with my backup.
Gladly I learned how important it is to backup the data before updating Actual Budget.

@MickLesk I understand you.
Last two times upgrading it to newer version, we had problems. Hopefully with Docker that won't be a problem anymore.

@danluckner commented on GitHub (Apr 5, 2025): I also spun up a Docker LXC and used the docker version of Actual budget, with my backup. Gladly I learned how important it is to backup the data before updating Actual Budget. @MickLesk I understand you. Last two times upgrading it to newer version, we had problems. Hopefully with Docker that won't be a problem anymore.

kerem commented

2026-02-26 12:46:32 +03:00

Author

Owner

@SplendidAppendix commented on GitHub (Apr 5, 2025):

We dont use git. Then there Release package is broken (once again)

I cant do anything on the Script

Why wouldn't you just use git?

That is one of the reasons. Which is why we have repeatedly considered removing actualbudget completely. Their releases simply suck. Every time something is defective or something else.

Can you elaborate on what is terrible about it? If the script isn't following their build recommendations, then wouldn't that be an issue with the script itself?

I was able to go the docs and within 5 minutes have a working install again. I just followed the instructions, and updated my actualbudget.service to point to /opt/actual for that piece and retain everything else. My specialized SSO config, budgets, everything were retained.

@SplendidAppendix commented on GitHub (Apr 5, 2025): > We dont use git. Then there Release package is broken (once again) > > I cant do anything on the Script Why wouldn't you just use git? > That is one of the reasons. Which is why we have repeatedly considered removing actualbudget completely. Their releases simply suck. Every time something is defective or something else. Can you elaborate on what is terrible about it? If the script isn't following their build recommendations, then wouldn't that be an issue with the script itself? I was able to go the [docs](https://actualbudget.org/docs/install/build-from-source/) and within 5 minutes have a working install again. I just followed the instructions, and updated my actualbudget.service to point to /opt/actual for that piece and retain everything else. My specialized SSO config, budgets, everything were retained.

kerem commented

2026-02-26 12:46:32 +03:00

Author

Owner

@stevester-codes commented on GitHub (Apr 5, 2025):

Use at your own risk, I made this script to fix the issue on my system. Always back up first.

#!/usr/bin/env bash

# Always run the original update script (will skip if already up to date)
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/actualbudget.sh)"

# Rebuild frontend regardless of version check
echo "[Actual Budget] Rebuilding frontend to fix missing index.html..."

cd /opt/actualbudget || exit 1

# Ensure required tools are available
apt-get update
apt-get install -y git

yarn install
yarn run build:server

systemctl restart actualbudget

echo "[Actual Budget] Rebuild and restart completed."

@stevester-codes commented on GitHub (Apr 5, 2025): Use at your own risk, I made this script to fix the issue on my system. Always back up first. ```bash #!/usr/bin/env bash # Always run the original update script (will skip if already up to date) bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/actualbudget.sh)" # Rebuild frontend regardless of version check echo "[Actual Budget] Rebuilding frontend to fix missing index.html..." cd /opt/actualbudget || exit 1 # Ensure required tools are available apt-get update apt-get install -y git yarn install yarn run build:server systemctl restart actualbudget echo "[Actual Budget] Rebuild and restart completed." ```

kerem commented

2026-02-26 12:46:32 +03:00

Author

Owner

@MickLesk commented on GitHub (Apr 5, 2025):

Then do an PR? Why do we always have to do this? I deleted the script a long time ago. Both in docker and in LXC. It just got on my nerves.

By the way, we do it voluntarily. We don't scan every document. And especially with those who feel like they're shooting something to pieces with every release, no thanks. Feel free to do a PR, I won't fix it until next Tuesday.

@MickLesk commented on GitHub (Apr 5, 2025): Then do an PR? Why do we always have to do this? I deleted the script a long time ago. Both in docker and in LXC. It just got on my nerves. By the way, we do it voluntarily. We don't scan every document. And especially with those who feel like they're shooting something to pieces with every release, no thanks. Feel free to do a PR, I won't fix it until next Tuesday.

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@timtjtim commented on GitHub (Apr 5, 2025):

Yeah this has broken the last 4 times for me, every time actual budget totally change their repo and something new happens. Don't envy you trying to keep this working.

I don't even remember the first issue, then it was the migrations bug with the .migrations file, then a broken key, and now it needing git (and 8GB RAM!).

Maybe we should just move to docker if they can't keep their from-source install even slightly consistent :(

@timtjtim commented on GitHub (Apr 5, 2025): Yeah this has broken the last 4 times for me, every time actual budget totally change their repo and something new happens. Don't envy you trying to keep this working. I don't even remember the first issue, then it was the migrations bug with the .migrations file, then a broken key, and now it needing git (and 8GB RAM!). Maybe we should just move to docker if they can't keep their from-source install even slightly consistent :(

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@SplendidAppendix commented on GitHub (Apr 5, 2025):

@MickLesk and @timtjtim Why is it such a big deal to use git? See my comment above. 5 mins I was up and running.

Edit: I just checked the wayback machine to just make sure I wasn't missing something. From 03/31/25: It was using git prior to the release of this version. So if the script was using git, then it would sync those changes.

@SplendidAppendix commented on GitHub (Apr 5, 2025): @MickLesk and @timtjtim Why is it such a big deal to use git? See my comment above. 5 mins I was up and running. Edit: I just checked the wayback machine to just make sure I wasn't missing something. From 03/31/25: It was using git prior to the release of this version. So if the script was using git, then it would sync those changes.

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@MickLesk commented on GitHub (Apr 5, 2025):

As dependency its okay, but as Git Pull not. We use the fixed Release Tarball

@MickLesk commented on GitHub (Apr 5, 2025): As dependency its okay, but as Git Pull not. We use the fixed Release Tarball

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@c3kuperus commented on GitHub (Apr 6, 2025):

script to fix this issue by @stevester-codes works.
thank you

@c3kuperus commented on GitHub (Apr 6, 2025): script to fix this issue by @stevester-codes works. thank you

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@timtjtim commented on GitHub (Apr 6, 2025):

@MickLesk and @timtjtim Why is it such a big deal to use git? See my comment above. 5 mins I was up and running.

A git pull on a main branch is very very likely to give you broken code unless the team are exceptionally careful about what is merged in.

The only thing you should be running is a git tagged version, or you're opening yourself up to a world of security vulnerabilities.

@timtjtim commented on GitHub (Apr 6, 2025): > @MickLesk and @timtjtim Why is it such a big deal to use git? See my comment above. 5 mins I was up and running. A git pull on a main branch is very very likely to give you broken code unless the team are exceptionally careful about what is merged in. The only thing you should be running is a git tagged version, or you're opening yourself up to a world of security vulnerabilities.

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@c3kuperus commented on GitHub (Apr 6, 2025):

Hi Everyone. Please keep in mind that git is a software developers tool and not a deployment mechanism. People come to these Proxmox server scripts to make deployment of server applications easier. I am a software developer for 20 years and I did not know what to do when I found this bug as On the script link page nore script running output on my Proxmox shell was there any post script deployment steps listed. So I had to search the internet to findout if there is someone else that had the same issue and found this issue link. We as developer's should always keep in mind that not everyone here would have a mindset of a developer and we should be inclusive of them to use the software.

@c3kuperus commented on GitHub (Apr 6, 2025): Hi Everyone. Please keep in mind that `git` is a software developers tool and not a deployment mechanism. People come to these Proxmox server scripts to make deployment of server applications easier. I am a software developer for 20 years and I did not know what to do when I found this `bug` as On the script link page nore script running output on my Proxmox shell was there any post script deployment steps listed. So I had to search the internet to findout if there is someone else that had the same issue and found this issue link. We as developer's should always keep in mind that not everyone here would have a mindset of a developer and we should be inclusive of them to use the software.

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@carpathianecs commented on GitHub (Apr 6, 2025):

Hey folks. I just tried using the updated script and got the following error:

 ⠋ Installing Actual Budget 
[ERROR] in line 50: exit code 0: while executing command "$@" > /dev/null 2>&1
The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output.

Was using the default configuration.

Ran with verbose and the following additional output appeared:

exit_script
{
    "status": "$status",
    "error": "$error",
    "random_id": "$RANDOM_UUID"
}
EOF

@carpathianecs commented on GitHub (Apr 6, 2025): Hey folks. I just tried using the updated script and got the following error: ``` ⠋ Installing Actual Budget [ERROR] in line 50: exit code 0: while executing command "$@" > /dev/null 2>&1 The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output. ``` Was using the default configuration. Ran with verbose and the following additional output appeared: ``` exit_script { "status": "$status", "error": "$error", "random_id": "$RANDOM_UUID" } EOF ```

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@MickLesk commented on GitHub (Apr 6, 2025):

OK time to remove the Script. It makes no sense. It is 1:1 their documentation + the user message

@MickLesk commented on GitHub (Apr 6, 2025): OK time to remove the Script. It makes no sense. It is 1:1 their documentation + the user message

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@c3kuperus commented on GitHub (Apr 6, 2025):

1 change that I had from the fixed update on the script I that I neede to install yarn first with command apt install yarn so.

# Rebuild frontend regardless of version check
echo "[Actual Budget] Rebuilding frontend to fix missing index.html..."

cd /opt/actualbudget || exit 1

# Ensure required tools are available
apt update
apt install -y git yarn

yarn install
yarn run build:server

systemctl restart actualbudget

echo "[Actual Budget] Rebuild and restart completed."

@c3kuperus commented on GitHub (Apr 6, 2025): 1 change that I had from the fixed update on the script I that I neede to install yarn first with command `apt install yarn` so. ``` # Rebuild frontend regardless of version check echo "[Actual Budget] Rebuilding frontend to fix missing index.html..." cd /opt/actualbudget || exit 1 # Ensure required tools are available apt update apt install -y git yarn yarn install yarn run build:server systemctl restart actualbudget echo "[Actual Budget] Rebuild and restart completed." ```

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@c3kuperus commented on GitHub (Apr 6, 2025):

It did work for me.
I don't think this script should be removed please.
I think there is many people that would like to install a self hosted budget mangement app.

@c3kuperus commented on GitHub (Apr 6, 2025): It did work for me. I don't think this script should be removed `please`. I think there is many people that would like to install a self hosted budget mangement app.

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@MickLesk commented on GitHub (Apr 6, 2025):

apt Install yarn? Lol, yarn will be installed by NodeJS, not the old Debian repo thing. Dont do this

@MickLesk commented on GitHub (Apr 6, 2025): apt Install yarn? Lol, yarn will be installed by NodeJS, not the old Debian repo thing. Dont do this

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@MickLesk commented on GitHub (Apr 6, 2025):

It did work for me.
I don't think this script should be removed please.
I think there is many people that would like to install a self hosted budget mangement app.

Then feel free to Push an issue there and they should check whats Missing. Its the 10 time in a half year, where this Script is broken. Maybe its better to use dockge or docker LXC

@MickLesk commented on GitHub (Apr 6, 2025): > It did work for me. > I don't think this script should be removed `please`. > I think there is many people that would like to install a self hosted budget mangement app. Then feel free to Push an issue there and they should check whats Missing. Its the 10 time in a half year, where this Script is broken. Maybe its better to use dockge or docker LXC

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@timtjtim commented on GitHub (Apr 6, 2025):

@MickLesk how would you feel about a script that just used the docker LXC? I know that’s not ideal as people want a “bare metal” install rather than two layers of virtualisation, but it might be a suitable middle ground vs removing the script completely?

@timtjtim commented on GitHub (Apr 6, 2025): @MickLesk how would you feel about a script that just used the docker LXC? I know that’s not ideal as people want a “bare metal” install rather than two layers of virtualisation, but it might be a suitable middle ground vs removing the script completely?

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@c3kuperus commented on GitHub (Apr 6, 2025):

okay. cool. but for now it is working.

@c3kuperus commented on GitHub (Apr 6, 2025): okay. cool. but for now it is working.

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@c3kuperus commented on GitHub (Apr 6, 2025):

@timtjtim I think that is a good idea to create a seperate install script for docker LXC then people can make there own chose.

@c3kuperus commented on GitHub (Apr 6, 2025): @timtjtim I think that is a good idea to create a seperate install script for docker LXC then people can make there own chose.

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@timtjtim commented on GitHub (Apr 6, 2025):

@c3kuperus sure, in a very insecure not maintainable way, not in a way that can be turned into a reusable, shareable script sadly.

@timtjtim commented on GitHub (Apr 6, 2025): @c3kuperus sure, in a very insecure not maintainable way, not in a way that can be turned into a reusable, shareable script sadly.

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@c3kuperus commented on GitHub (Apr 6, 2025):

okay

@c3kuperus commented on GitHub (Apr 6, 2025): okay

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@dannyellis commented on GitHub (Apr 6, 2025):

New script works fine for a fresh install if you up the RAM. Failed with not enough heap at defaults just FYI

@dannyellis commented on GitHub (Apr 6, 2025): New script works fine for a fresh install if you up the RAM. Failed with not enough heap at defaults just FYI

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@carpathianecs commented on GitHub (Apr 6, 2025):

New script works fine for a fresh install if you up the RAM. Failed with not enough heap at defaults just FYI

Confirmed. I upped it to 8 GB, and the new scripts works fine.

Seems like the fix would be to up the default RAM from 2048 to 8096.

@carpathianecs commented on GitHub (Apr 6, 2025): > New script works fine for a fresh install if you up the RAM. Failed with not enough heap at defaults just FYI Confirmed. I upped it to 8 GB, and the new scripts works fine. Seems like the fix would be to up the default RAM from 2048 to 8096.

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@ghost commented on GitHub (Apr 7, 2025):

Seems more ram availability set as a default would certainly help a bit? Idk just my two cents

@ghost commented on GitHub (Apr 7, 2025): Seems more ram availability set as a default would certainly help a bit? Idk just my two cents

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@GilDev commented on GitHub (Apr 7, 2025):

Tried updating, told me I needed to up the RAM which I did, also increased disk to 8 GB at the same time because it seems to be required albeit not notified, the update went file but the service won’t start now:

Apr 07 13:26:13 actualbudget systemd[1]: Started actualbudget.service - Actual Budget Service.
Apr 07 13:26:15 actualbudget yarn[4399]: Checking if there are any migrations to run for direction "up"...
Apr 07 13:26:15 actualbudget yarn[4399]: Migrations: DONE
Apr 07 13:26:16 actualbudget yarn[4399]: Running in production mode - Serving static React app
Apr 07 13:26:16 actualbudget yarn[4399]: Rejection: Error: ENOENT: no such file or directory, open '/opt/actualbudget/selfhost.key'
Apr 07 13:26:16 actualbudget yarn[4399]:     at Object.openSync (node:fs:574:18)
Apr 07 13:26:16 actualbudget yarn[4399]:     at Object.readFileSync (node:fs:453:35)
Apr 07 13:26:16 actualbudget yarn[4399]:     at parseHTTPSConfig (file:///opt/actualbudget/packages/sync-server/src/app.js:107:13)
Apr 07 13:26:16 actualbudget yarn[4399]:     at Module.run (file:///opt/actualbudget/packages/sync-server/src/app.js:129:12) {
Apr 07 13:26:16 actualbudget yarn[4399]:   errno: -2,
Apr 07 13:26:16 actualbudget yarn[4399]:   code: 'ENOENT',
Apr 07 13:26:16 actualbudget yarn[4399]:   syscall: 'open',
Apr 07 13:26:16 actualbudget yarn[4399]:   path: '/opt/actualbudget/selfhost.key'
Apr 07 13:26:16 actualbudget yarn[4399]: }
Apr 07 13:26:16 actualbudget systemd[1]: actualbudget.service: Deactivated successfully.
Apr 07 13:26:16 actualbudget systemd[1]: actualbudget.service: Consumed 3.374s CPU time.

@GilDev commented on GitHub (Apr 7, 2025): Tried updating, told me I needed to up the RAM which I did, also increased disk to 8 GB at the same time because it seems to be required albeit not notified, the update went file but the service won’t start now: ``` Apr 07 13:26:13 actualbudget systemd[1]: Started actualbudget.service - Actual Budget Service. Apr 07 13:26:15 actualbudget yarn[4399]: Checking if there are any migrations to run for direction "up"... Apr 07 13:26:15 actualbudget yarn[4399]: Migrations: DONE Apr 07 13:26:16 actualbudget yarn[4399]: Running in production mode - Serving static React app Apr 07 13:26:16 actualbudget yarn[4399]: Rejection: Error: ENOENT: no such file or directory, open '/opt/actualbudget/selfhost.key' Apr 07 13:26:16 actualbudget yarn[4399]: at Object.openSync (node:fs:574:18) Apr 07 13:26:16 actualbudget yarn[4399]: at Object.readFileSync (node:fs:453:35) Apr 07 13:26:16 actualbudget yarn[4399]: at parseHTTPSConfig (file:///opt/actualbudget/packages/sync-server/src/app.js:107:13) Apr 07 13:26:16 actualbudget yarn[4399]: at Module.run (file:///opt/actualbudget/packages/sync-server/src/app.js:129:12) { Apr 07 13:26:16 actualbudget yarn[4399]: errno: -2, Apr 07 13:26:16 actualbudget yarn[4399]: code: 'ENOENT', Apr 07 13:26:16 actualbudget yarn[4399]: syscall: 'open', Apr 07 13:26:16 actualbudget yarn[4399]: path: '/opt/actualbudget/selfhost.key' Apr 07 13:26:16 actualbudget yarn[4399]: } Apr 07 13:26:16 actualbudget systemd[1]: actualbudget.service: Deactivated successfully. Apr 07 13:26:16 actualbudget systemd[1]: actualbudget.service: Consumed 3.374s CPU time. ```

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@MickLesk commented on GitHub (Apr 7, 2025):

How old is your install? The selfhst.key are available since 2 or 3 month

@MickLesk commented on GitHub (Apr 7, 2025): How old is your install? The selfhst.key are available since 2 or 3 month

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@GilDev commented on GitHub (Apr 7, 2025):

@MickLesk Probably older than that… time for a complete reinstall I guess? Or maybe it’s time to migrate to Docker as you suggested.

@GilDev commented on GitHub (Apr 7, 2025): @MickLesk Probably older than that… time for a complete reinstall I guess? Or maybe it’s time to migrate to Docker as you suggested.

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@MickLesk commented on GitHub (Apr 7, 2025):

check this https://github.com/community-scripts/ProxmoxVE/discussions/2509

@MickLesk commented on GitHub (Apr 7, 2025): check this https://github.com/community-scripts/ProxmoxVE/discussions/2509

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@GilDev commented on GitHub (Apr 7, 2025):

@MickLesk Thanks! Hopefully this script won’t cause you more trouble in the future…

@GilDev commented on GitHub (Apr 7, 2025): @MickLesk Thanks! Hopefully this script won’t cause you more trouble in the future…

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@aperezva commented on GitHub (Apr 19, 2025):

To me script it´s not working, my installation ahs the last version before taht, and I increased memory to 8 GB.

Thinking to change solution to another more robust. Any recomendation?

@aperezva commented on GitHub (Apr 19, 2025): To me script it´s not working, my installation ahs the last version before taht, and I increased memory to 8 GB. Thinking to change solution to another more robust. Any recomendation?

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@MickLesk commented on GitHub (Apr 19, 2025):

Yes, read the Changelog and you see we have removed it

@MickLesk commented on GitHub (Apr 19, 2025): Yes, read the Changelog and you see we have removed it

kerem commented

2026-02-26 12:46:33 +03:00

Author

Owner

@nichtdu commented on GitHub (Jun 30, 2025):

came along the same issue - increasing ram for the upgrade process resolved the issue

@nichtdu commented on GitHub (Jun 30, 2025): came along the same issue - increasing ram for the upgrade process resolved the issue

kerem referenced this issue

2026-02-26 13:31:36 +03:00

[PR #753] [CLOSED] Update Script: Syncthing.sh Fix wrong config path #2863

Rows
Columns

[GH-ISSUE #3678] Actual Budget install/update breaks app – missing index.html in desktop-client #752

✅ Have you read and understood the above guidelines?

📜 What is the name of the script you are using?

📂 What was the exact command used to execute the script?

📝 Provide a clear and concise description of the issue.

⚙️ What settings are you using?

🖥️ Which Linux distribution are you using?

🔄 Steps to reproduce the issue.

❌ Paste the full error output (if available).

🖼️ Additional context (optional).