starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

Actual Budget 25.3.0 Update Failed #569

New Issue
Closed
opened 2026-02-04 19:54:52 +03:00 by OVERLORD · 33 comments
OVERLORD commented 2026-02-04 19:54:52 +03:00
Owner
Copy Link

Originally created by @Untoasted9577 on GitHub (Mar 1, 2025).

Originally assigned to: @MickLesk on GitHub.

✅ Have you read and understood the above guidelines?

yes

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

Actual Budget LXC

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/actualbudget.sh)"

📝 Provide a clear and concise description of the issue.

Actual Budget has moved their repository in the February 2025 update. The actual-server repository has been archived into read only mode. The script needs to be adjusted to point to the new repository.

https://actualbudget.org/docs/actual-server-repo-move/

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

update

❌ Paste the full error output (if available).

[ERROR] in line 42: exit code 0: while executing command wget -g "https://github.com/actualbudget/actual-server/archive/refs/tags/v${RELEASE}.tar.gz"

🖼️ Additional context (optional).

No response

Originally created by @Untoasted9577 on GitHub (Mar 1, 2025). Originally assigned to: @MickLesk on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Actual Budget LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/actualbudget.sh)" ### 📝 Provide a clear and concise description of the issue. Actual Budget has moved their repository in the February 2025 update. The actual-server repository has been archived into read only mode. The script needs to be adjusted to point to the new repository. https://actualbudget.org/docs/actual-server-repo-move/ ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. update ### ❌ Paste the full error output (if available). [ERROR] in line 42: exit code 0: while executing command wget -g "https://github.com/actualbudget/actual-server/archive/refs/tags/v${RELEASE}.tar.gz" ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 19:54:52 +03:00
OVERLORD commented 2026-02-04 19:55:02 +03:00
Author
Owner
Copy Link

@bourquep commented on GitHub (Mar 1, 2025):

The actual-server repository has been archived on Feb 10 2025 and merged into the main actual repository.

Doc about this change: https://actualbudget.org/docs/actual-server-repo-move

@bourquep commented on GitHub (Mar 1, 2025): The [actual-server](https://github.com/actualbudget/actual-server) repository has been archived on Feb 10 2025 and merged into the main [actual](https://github.com/actualbudget/actual) repository. Doc about this change: https://actualbudget.org/docs/actual-server-repo-move
OVERLORD commented 2026-02-04 19:55:08 +03:00
Author
Owner
Copy Link

@Untoasted9577 commented on GitHub (Mar 1, 2025):

The actual-server repository has been archived on Feb 10 2025 and merged into the main actual repository.

Doc about this change: https://actualbudget.org/docs/actual-server-repo-move

Correct. I have this in my bug report.

@Untoasted9577 commented on GitHub (Mar 1, 2025): > The [actual-server](https://github.com/actualbudget/actual-server) repository has been archived on Feb 10 2025 and merged into the main [actual](https://github.com/actualbudget/actual) repository. > > Doc about this change: https://actualbudget.org/docs/actual-server-repo-move Correct. I have this in my bug report.
OVERLORD commented 2026-02-04 19:55:16 +03:00
Author
Owner
Copy Link

@bourquep commented on GitHub (Mar 1, 2025):

Correct. I have this in my bug report.

Indeed you do, my bad for having missed it.

@bourquep commented on GitHub (Mar 1, 2025): > Correct. I have this in my bug report. Indeed you do, my bad for having missed it.
OVERLORD commented 2026-02-04 19:55:17 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 1, 2025):

Maybe at evening i take a Look

@MickLesk commented on GitHub (Mar 1, 2025): Maybe at evening i take a Look
OVERLORD commented 2026-02-04 19:55:28 +03:00
Author
Owner
Copy Link

@Untoasted9577 commented on GitHub (Mar 1, 2025):

Maybe at evening i take a Look

Thank you. I appreciate your help.

@Untoasted9577 commented on GitHub (Mar 1, 2025): > Maybe at evening i take a Look Thank you. I appreciate your help.
OVERLORD commented 2026-02-04 19:55:39 +03:00
Author
Owner
Copy Link

@Nerdtality commented on GitHub (Mar 1, 2025):

This looks like the new REPO for Actual Server (Now "Sync Server")
https://github.com/actualbudget/actual/tree/master/packages/sync-server

@Nerdtality commented on GitHub (Mar 1, 2025): This looks like the new REPO for Actual Server (Now "Sync Server") https://github.com/actualbudget/actual/tree/master/packages/sync-server
OVERLORD commented 2026-02-04 19:55:49 +03:00
Author
Owner
Copy Link

@Untoasted9577 commented on GitHub (Mar 1, 2025):

This looks like the new REPO for Actual Server (Now "Sync Server") https://github.com/actualbudget/actual/tree/master/packages/sync-server

Correct

@Untoasted9577 commented on GitHub (Mar 1, 2025): > This looks like the new REPO for Actual Server (Now "Sync Server") https://github.com/actualbudget/actual/tree/master/packages/sync-server Correct
OVERLORD commented 2026-02-04 19:55:52 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 1, 2025):

heavy. The Whole Script doesnt work now.
It makes you wonder how you come up with such a stupid idea to rebuild the whole repo in this way.

Changing it for new installations probably won't be that complicated, but I can't yet say how it is for existing scripts.

i build an script and test locally...

For now i break the update part until its fixed.

@MickLesk commented on GitHub (Mar 1, 2025): heavy. The Whole Script doesnt work now. It makes you wonder how you come up with such a stupid idea to rebuild the whole repo in this way. Changing it for new installations probably won't be that complicated, but I can't yet say how it is for existing scripts. i build an script and test locally... For now i break the update part until its fixed.
OVERLORD commented 2026-02-04 19:56:04 +03:00
Author
Owner
Copy Link

@Untoasted9577 commented on GitHub (Mar 1, 2025):

heavy. The Whole Script doesnt work now. It makes you wonder how you come up with such a stupid idea to rebuild the whole repo in this way.

Changing it for new installations probably won't be that complicated, but I can't yet say how it is for existing scripts.

i build an script and test locally...

For now i break the update part until its fixed.

I think the best route to take here is to update the script to work with the new repo. Tell all existing users to backup their budget, delete the LXC, and deploy a new LXC using the new script. I'd be perfectly fine with that.

@Untoasted9577 commented on GitHub (Mar 1, 2025): > heavy. The Whole Script doesnt work now. It makes you wonder how you come up with such a stupid idea to rebuild the whole repo in this way. > > Changing it for new installations probably won't be that complicated, but I can't yet say how it is for existing scripts. > > i build an script and test locally... > > For now i break the update part until its fixed. I think the best route to take here is to update the script to work with the new repo. Tell all existing users to backup their budget, delete the LXC, and deploy a new LXC using the new script. I'd be perfectly fine with that.
OVERLORD commented 2026-02-04 19:56:17 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 1, 2025):

For new installations, i think its done. anyone need to check after #2770 merged

@MickLesk commented on GitHub (Mar 1, 2025): For new installations, i think its done. anyone need to check after #2770 merged
OVERLORD commented 2026-02-04 19:56:35 +03:00
Author
Owner
Copy Link

@Untoasted9577 commented on GitHub (Mar 1, 2025):

For new installations, i think its done. anyone need to check after #2770 merged

Very cool. So if we deploy with the new script, can use still use the "update" command for future releases?

@Untoasted9577 commented on GitHub (Mar 1, 2025): > For new installations, i think its done. anyone need to check after [#2770](https://github.com/community-scripts/ProxmoxVE/pull/2770) merged Very cool. So if we deploy with the new script, can use still use the "update" command for future releases?
OVERLORD commented 2026-02-04 19:56:46 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 1, 2025):

Not yet, need to be rebuild by me. I need some time for this

@MickLesk commented on GitHub (Mar 1, 2025): Not yet, need to be rebuild by me. I need some time for this
OVERLORD commented 2026-02-04 19:56:53 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 1, 2025):

installation looks good, can anyone test it?

Update Script coming asap. i rework it

@MickLesk commented on GitHub (Mar 1, 2025): installation looks good, can anyone test it? Update Script coming asap. i rework it
OVERLORD commented 2026-02-04 19:57:00 +03:00
Author
Owner
Copy Link

@chmsant commented on GitHub (Mar 1, 2025):

installation looks good, can anyone test it?

Update Script coming asap. i rework it

Fresh LXC installation worked just fine here with your most recent changes. 25.3.0 installed successfully.

@chmsant commented on GitHub (Mar 1, 2025): > installation looks good, can anyone test it? > > Update Script coming asap. i rework it Fresh LXC installation worked just fine here with your most recent changes. 25.3.0 installed successfully.
OVERLORD commented 2026-02-04 19:57:01 +03:00
Author
Owner
Copy Link

@cipheredsyntax commented on GitHub (Mar 2, 2025):

I tested the new install script just now and it seems that Actual Budget isn't working. The LXC is created successfully and I can see that /opt/actualbudget, /opt/actualbudget-data and /opt/actualbudget_version.txt are created but the app itself is unreachable, with or without a reverse proxy. Navigating to 192.168.x.x:5006 gives me a "The connection was reset" error and using HTTPS gives me "502 Bad Gateway".

@cipheredsyntax commented on GitHub (Mar 2, 2025): I tested the new install script just now and it seems that Actual Budget isn't working. The LXC is created successfully and I can see that /opt/actualbudget, /opt/actualbudget-data and /opt/actualbudget_version.txt are created but the app itself is unreachable, with or without a reverse proxy. Navigating to 192.168.x.x:5006 gives me a "The connection was reset" error and using HTTPS gives me "502 Bad Gateway".
OVERLORD commented 2026-02-04 19:57:05 +03:00
Author
Owner
Copy Link

@qkevinto commented on GitHub (Mar 2, 2025):

I'm experiencing a similar issue to what @cipheredsyntax has described. Running journalctl -u actualbudget.service I can see that the server has started without errors and is listening for requests: Listening on :::5006... but it doesn't seem to be responding to anything. Oddly enough if I stop the service with systemctl stop actualbudget and then run the server manually with /usr/bin/yarn start:server then it works just fine.

@qkevinto commented on GitHub (Mar 2, 2025): I'm experiencing a similar issue to what @cipheredsyntax has described. Running `journalctl -u actualbudget.service` I can see that the server has started without errors and is listening for requests: `Listening on :::5006...` but it doesn't seem to be responding to anything. Oddly enough if I stop the service with `systemctl stop actualbudget` and then run the server manually with `/usr/bin/yarn start:server` then it works just fine.
OVERLORD commented 2026-02-04 19:57:13 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 2, 2025):

Heh? Some says it Work fine and some says no

Ive deployed 5 Times and everytime the webui worked fine. (Default settings)

@MickLesk commented on GitHub (Mar 2, 2025): Heh? Some says it Work fine and some says no Ive deployed 5 Times and everytime the webui worked fine. (Default settings)
OVERLORD commented 2026-02-04 19:57:22 +03:00
Author
Owner
Copy Link

@Nerdtality commented on GitHub (Mar 2, 2025):

I'm experiencing a similar issue to what @cipheredsyntax has described. Running journalctl -u actualbudget.service I can see that the server has started without errors and is listening for requests: Listening on :::5006... but it doesn't seem to be responding to anything. Oddly enough if I stop the service with systemctl stop actualbudget and then run the server manually with /usr/bin/yarn start:server then it works just fine.

I tested the new install script just now and it seems that Actual Budget isn't working. The LXC is created successfully and I can see that /opt/actualbudget, /opt/actualbudget-data and /opt/actualbudget_version.txt are created but the app itself is unreachable, with or without a reverse proxy. Navigating to 192.168.x.x:5006 gives me a "The connection was reset" error and using HTTPS gives me "502 Bad Gateway".

Were both of these fresh installs?

@Nerdtality commented on GitHub (Mar 2, 2025): > I'm experiencing a similar issue to what [@cipheredsyntax](https://github.com/cipheredsyntax) has described. Running `journalctl -u actualbudget.service` I can see that the server has started without errors and is listening for requests: `Listening on :::5006...` but it doesn't seem to be responding to anything. Oddly enough if I stop the service with `systemctl stop actualbudget` and then run the server manually with `/usr/bin/yarn start:server` then it works just fine. > I tested the new install script just now and it seems that Actual Budget isn't working. The LXC is created successfully and I can see that /opt/actualbudget, /opt/actualbudget-data and /opt/actualbudget_version.txt are created but the app itself is unreachable, with or without a reverse proxy. Navigating to 192.168.x.x:5006 gives me a "The connection was reset" error and using HTTPS gives me "502 Bad Gateway". Were both of these fresh installs?
OVERLORD commented 2026-02-04 19:57:24 +03:00
Author
Owner
Copy Link

@Unostot commented on GitHub (Mar 2, 2025):

I'm experiencing a similar issue to what @cipheredsyntax has described. Running journalctl -u actualbudget.service I can see that the server has started without errors and is listening for requests: Listening on :::5006... but it doesn't seem to be responding to anything. Oddly enough if I stop the service with systemctl stop actualbudget and then run the server manually with /usr/bin/yarn start:server then it works just fine.

I had the same problem last night. Install worked fine, systemd status reported listening...
but I got no response...not on htttp 5006 nor through the reverse proxy... (and yes, the 'old' actual budget LXC was off at the time ;) )

Edith:
I've just noticed that the LXC no listens with HTTPS on 5006:
https://10.42.20.92:5006
and there I also receive an answer with an self signed cert...

I'm not sure if this is intended or not. Until now actual itself was listening without SSL just on HTTP:5006 and usually a reverse proxy was handeling the SSL...

At least this explains why it works with @MickLesk but not with others, who might not noticed this change :)
So problem right now: new installation serves on https+5006, not http+5006 like the old one...

Greetings,
Uno

@Unostot commented on GitHub (Mar 2, 2025): > I'm experiencing a similar issue to what [@cipheredsyntax](https://github.com/cipheredsyntax) has described. Running `journalctl -u actualbudget.service` I can see that the server has started without errors and is listening for requests: `Listening on :::5006...` but it doesn't seem to be responding to anything. Oddly enough if I stop the service with `systemctl stop actualbudget` and then run the server manually with `/usr/bin/yarn start:server` then it works just fine. I had the same problem last night. Install worked fine, systemd status reported listening... but I got no response...not on htttp 5006 nor through the reverse proxy... (and yes, the 'old' actual budget LXC was off at the time ;) ) Edith: I've just noticed that the LXC no listens with HTTPS on 5006: `https://10.42.20.92:5006` and there I also receive an answer with an self signed cert... I'm not sure if this is intended or not. Until now actual itself was listening without SSL just on HTTP:5006 and usually a reverse proxy was handeling the SSL... At least this explains why it works with @MickLesk but not with others, who might not noticed this change :) So problem right now: new installation serves on https+5006, not http+5006 like the old one... Greetings, Uno
OVERLORD commented 2026-02-04 19:57:38 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 2, 2025):

Yep https:// because http caused to many Issues in the past.

@MickLesk commented on GitHub (Mar 2, 2025): Yep https:// because http caused to many Issues in the past.
OVERLORD commented 2026-02-04 19:57:48 +03:00
Author
Owner
Copy Link

@Unostot commented on GitHub (Mar 2, 2025):

Yep https:// because http caused to many Issues in the past.

Yeah, but maybe this was then the "main issue" this time. At least I just installed a new container with the same mac, so after restart it had the same IP and it should have worked thorugh the reverse proxy again...
this was not the case, and manual opening of the "known" 5006 URL was also not working...I guess in those cases nobody expected or noticed the subtle change to https...
Myself had also a big fight with the hotel wifi and the vpn to my home, so there were just too many other things as possible additional points of failure to debug it carefully last night :)

Now just coming updates using update need to work, and I'm happy (the last few versions I installed usually the LXC new since the update script had each time some hickups...)

And by the way: thanks for the quick repair yesterday...thanks to the proxmox helper scripts I stumbled over actual budget in the first place last year :)

Greetings,
Uno

@Unostot commented on GitHub (Mar 2, 2025): > Yep https:// because http caused to many Issues in the past. Yeah, but maybe this was then the "main issue" this time. At least I just installed a new container with the same mac, so after restart it had the same IP and it should have worked thorugh the reverse proxy again... this was not the case, and manual opening of the "known" 5006 URL was also not working...I guess in those cases nobody expected or noticed the subtle change to https... Myself had also a big fight with the hotel wifi and the vpn to my home, so there were just too many other things as possible additional points of failure to debug it carefully last night :) Now just coming updates using `update` need to work, and I'm happy (the last few versions I installed usually the LXC new since the update script had each time some hickups...) And by the way: thanks for the quick repair yesterday...thanks to the proxmox helper scripts I stumbled over actual budget in the first place last year :) Greetings, Uno
OVERLORD commented 2026-02-04 19:57:53 +03:00
Author
Owner
Copy Link

@qkevinto commented on GitHub (Mar 2, 2025):

At least I just installed a new container with the same mac, so after restart it had the same IP and it should have worked thorugh the reverse proxy again...
this was not the case, and manual opening of the "known" 5006 URL was also not working...I guess in those cases nobody expected or noticed the subtle change to https...

That's exactly it! I did the exact same thing, new container, retained MAC address but didn't update my nginx reverse proxy config as I wasn't aware that it changed to https by default. Just tried it again and this time updated my nginx reverse proxy config to https and it's all working as expected. Thank you very much! 🙂

@qkevinto commented on GitHub (Mar 2, 2025): > At least I just installed a new container with the same mac, so after restart it had the same IP and it should have worked thorugh the reverse proxy again... this was not the case, and manual opening of the "known" 5006 URL was also not working...I guess in those cases nobody expected or noticed the subtle change to https... That's exactly it! I did the exact same thing, new container, retained MAC address but didn't update my nginx reverse proxy config as I wasn't aware that it changed to `https` by default. Just tried it again and this time updated my nginx reverse proxy config to `https` and it's all working as expected. Thank you very much! 🙂
OVERLORD commented 2026-02-04 19:58:06 +03:00
Author
Owner
Copy Link

@Nedlinin commented on GitHub (Mar 3, 2025):

Another confirmation of the new script working for a new install

@Nedlinin commented on GitHub (Mar 3, 2025): Another confirmation of the new script working for a new install
OVERLORD commented 2026-02-04 19:58:11 +03:00
Author
Owner
Copy Link

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

I think i can prepare an update fix tomorrow.

@MickLesk commented on GitHub (Mar 6, 2025): I think i can prepare an update fix tomorrow.
OVERLORD commented 2026-02-04 19:58:17 +03:00
Author
Owner
Copy Link

@ftbboy2115 commented on GitHub (Mar 7, 2025):

I think i can prepare an update fix tomorrow.

I really appreciate all your hard work. I didn't get the opportunity before, but I apologize for coming off as ungrateful for the effort you and the others put into providing this to the community. Keep up the great work ☺️

@ftbboy2115 commented on GitHub (Mar 7, 2025): > I think i can prepare an update fix tomorrow. I really appreciate all your hard work. I didn't get the opportunity before, but I apologize for coming off as ungrateful for the effort you and the others put into providing this to the community. Keep up the great work ☺️
OVERLORD commented 2026-02-04 19:58:18 +03:00
Author
Owner
Copy Link

@ftbboy2115 commented on GitHub (Mar 7, 2025):

Not yet, need to be rebuild by me. I need some time for this

BTW, I never did see this, so I understand why you may have gotten frustrated by my post in the other bug report. Again, I'm sorry, didn't mean to step on toes.

@ftbboy2115 commented on GitHub (Mar 7, 2025): > Not yet, need to be rebuild by me. I need some time for this BTW, I never did see this, so I understand why you may have gotten frustrated by my post in the other bug report. Again, I'm sorry, didn't mean to step on toes.
OVERLORD commented 2026-02-04 19:58:30 +03:00
Author
Owner
Copy Link

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

merged

@MickLesk commented on GitHub (Mar 7, 2025): merged
OVERLORD commented 2026-02-04 19:58:55 +03:00
Author
Owner
Copy Link

@Unostot commented on GitHub (Mar 8, 2025):

not sure if its just happening for me...
after the update it is not working, journalctl says something that the selfhost.key is missing

Mar 07 21:42:19 actualbudget yarn[1499]: Checking if there are any migrations to run for direction "up"...
Mar 07 21:42:19 actualbudget yarn[1499]: Migrations: DONE
Mar 07 21:42:20 actualbudget yarn[1499]: Running in production mode - Serving static React app
Mar 07 21:42:20 actualbudget yarn[1499]: Rejection: Error: ENOENT: no such file or directory, open '/opt/actualbudget/selfhost.key'
Mar 07 21:42:20 actualbudget yarn[1499]:     at Object.openSync (node:fs:562:18)
Mar 07 21:42:20 actualbudget yarn[1499]:     at Object.readFileSync (node:fs:446:35)
Mar 07 21:42:20 actualbudget yarn[1499]:     at parseHTTPSConfig (file:///opt/actualbudget/packages/sync-server/src/app.js:100:13)
Mar 07 21:42:20 actualbudget yarn[1499]:     at Module.run (file:///opt/actualbudget/packages/sync-server/src/app.js:108:12) {
Mar 07 21:42:20 actualbudget yarn[1499]:   errno: -2,
Mar 07 21:42:20 actualbudget yarn[1499]:   code: 'ENOENT',
Mar 07 21:42:20 actualbudget yarn[1499]:   syscall: 'open',
Mar 07 21:42:20 actualbudget yarn[1499]:   path: '/opt/actualbudget/selfhost.key'
Mar 07 21:42:20 actualbudget yarn[1499]: }
Mar 07 21:42:20 actualbudget systemd[1]: actualbudget.service: Deactivated successfully.

this is a LXC which was created with your new setup method, and updated using update...not sure why the selfhost key disappeared...

Greetings,
Uno

@Unostot commented on GitHub (Mar 8, 2025): not sure if its just happening for me... after the update it is not working, journalctl says something that the `selfhost.key` is missing ``` Mar 07 21:42:19 actualbudget yarn[1499]: Checking if there are any migrations to run for direction "up"... Mar 07 21:42:19 actualbudget yarn[1499]: Migrations: DONE Mar 07 21:42:20 actualbudget yarn[1499]: Running in production mode - Serving static React app Mar 07 21:42:20 actualbudget yarn[1499]: Rejection: Error: ENOENT: no such file or directory, open '/opt/actualbudget/selfhost.key' Mar 07 21:42:20 actualbudget yarn[1499]: at Object.openSync (node:fs:562:18) Mar 07 21:42:20 actualbudget yarn[1499]: at Object.readFileSync (node:fs:446:35) Mar 07 21:42:20 actualbudget yarn[1499]: at parseHTTPSConfig (file:///opt/actualbudget/packages/sync-server/src/app.js:100:13) Mar 07 21:42:20 actualbudget yarn[1499]: at Module.run (file:///opt/actualbudget/packages/sync-server/src/app.js:108:12) { Mar 07 21:42:20 actualbudget yarn[1499]: errno: -2, Mar 07 21:42:20 actualbudget yarn[1499]: code: 'ENOENT', Mar 07 21:42:20 actualbudget yarn[1499]: syscall: 'open', Mar 07 21:42:20 actualbudget yarn[1499]: path: '/opt/actualbudget/selfhost.key' Mar 07 21:42:20 actualbudget yarn[1499]: } Mar 07 21:42:20 actualbudget systemd[1]: actualbudget.service: Deactivated successfully. ``` this is a LXC which was created with your new setup method, and updated using update...not sure why the selfhost key disappeared... Greetings, Uno
OVERLORD commented 2026-02-04 19:58:59 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 8, 2025):

Fixed for Update function directly

@MickLesk commented on GitHub (Mar 8, 2025): Fixed for Update function directly
OVERLORD commented 2026-02-04 19:59:10 +03:00
Author
Owner
Copy Link

@Unostot commented on GitHub (Mar 8, 2025):

Fixed for Update function directly

thank you, tried again, now the key stays and it works without problems 👍

Thank you for the quick fix, and lets hope that in the near future no changes to the script are needed :)

@Unostot commented on GitHub (Mar 8, 2025): > Fixed for Update function directly thank you, tried again, now the key stays and it works without problems 👍 Thank you for the quick fix, and lets hope that in the near future no changes to the script are needed :)
OVERLORD commented 2026-02-04 19:59:24 +03:00
Author
Owner
Copy Link

@cipheredsyntax commented on GitHub (Apr 8, 2025):

@MickLesk I am having the same issue with the following error:

Rejection: Error: ENOENT: no such file or directory, open '/opt/actualbudget/selfhost.key'

However, I don't have a selfhost.key. I use Nginx Proxy Manager to serve Actual Budget via HTTPS. It's now broken after using the update function.

@cipheredsyntax commented on GitHub (Apr 8, 2025): @MickLesk I am having the same issue with the following error: `Rejection: Error: ENOENT: no such file or directory, open '/opt/actualbudget/selfhost.key'` However, I don't have a selfhost.key. I use Nginx Proxy Manager to serve Actual Budget via HTTPS. It's now broken after using the update function.
OVERLORD commented 2026-02-04 19:59:29 +03:00
Author
Owner
Copy Link

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

That's not our fault. You will have to adjust it manually. You have the option, otherwise we can only remove the script completely, as it only causes "problems"

By the way, in discussion is an guide for this. You need to reeingineer this.

@MickLesk commented on GitHub (Apr 8, 2025): That's not our fault. You will have to adjust it manually. You have the option, otherwise we can only remove the script completely, as it only causes "problems" By the way, in discussion is an guide for this. You need to reeingineer this.
OVERLORD commented 2026-02-04 19:59:42 +03:00
Author
Owner
Copy Link

@Unostot commented on GitHub (Apr 9, 2025):

@MickLesk I am having the same issue with the following error:

Rejection: Error: ENOENT: no such file or directory, open '/opt/actualbudget/selfhost.key'

However, I don't have a selfhost.key. I use Nginx Proxy Manager to serve Actual Budget via HTTPS. It's now broken after using the update function.

did you by any chance not use the "new" install script, which @MickLesk did for the 25.3.0 update?

I setup a new LXC with this, and did the most recent update without problems some days ago...so the script, including the update script, is working...

The selfhost key was not there in the older scripts before the changes in 25.3.0.
Since the rework it now has the selfhost.key and serves via https on port 5006 without problems.

And also the update via script works now.
So I guess your problem really comes from the mixing of old and new setup/update scripts...

and @MickLesk : please don't remove the script, now that it is working again... :o)

@Unostot commented on GitHub (Apr 9, 2025): > [@MickLesk](https://github.com/MickLesk) I am having the same issue with the following error: > > `Rejection: Error: ENOENT: no such file or directory, open '/opt/actualbudget/selfhost.key'` > > However, I don't have a selfhost.key. I use Nginx Proxy Manager to serve Actual Budget via HTTPS. It's now broken after using the update function. did you by any chance not use the "new" install script, which @MickLesk did for the 25.3.0 update? I setup a new LXC with this, and did the most recent update without problems some days ago...so the script, including the update script, is working... The selfhost key was not there in the older scripts before the changes in 25.3.0. Since the rework it now has the selfhost.key and serves via https on port 5006 without problems. And also the update via script works now. So I guess your problem really comes from the mixing of old and new setup/update scripts... and @MickLesk : please don't remove the script, now that it is working again... :o)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#569
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?