SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Cannot update Actual Budget #464

New Issue
Closed
opened 2025-11-20 04:48:56 -05:00 by saavagebueno · 6 comments
saavagebueno commented 2025-11-20 04:48:56 -05:00
Owner
Copy Link

Originally created by @timtjtim on GitHub (Feb 3, 2025).

✅ Have you read and understood the above guidelines?

yes

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

ActualBudget

📂 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.

Cannot update Actual Budget using update command / bash and wget command

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Run the update command

❌ Paste the full error output (if available).

  ✔️  Actual Budget Stopped
 ⠼mv: cannot stat '/opt/actualbudget_bak/.env': No such file or directory

[ERROR] in line 51: exit code 0: while executing command mv /opt/actualbudget_bak/.env /opt/actualbudget

🖼️ Additional context (optional).

File structure of /opt (depth 1):

/opt/
├── actualbudget
│   ├── app.js
│   ├── babel.config.json
│   ├── docker
│   ├── docker-compose.yml
│   ├── Dockerfile
│   ├── jest.config.json
│   ├── jest.global-setup.js
│   ├── jest.global-teardown.js
│   ├── LICENSE.txt
│   ├── migrations
│   ├── package.json
│   ├── README.md
│   ├── src
│   ├── tsconfig.json
│   ├── upcoming-release-notes
│   └── yarn.lock
├── actualbudget_self_bk
│   ├── app.js
│   ├── babel.config.json
│   ├── docker
│   ├── docker-compose.yml
│   ├── Dockerfile
│   ├── jest.config.json
│   ├── jest.global-setup.js
│   ├── jest.global-teardown.js
│   ├── LICENSE.txt
│   ├── migrations
│   ├── package.json
│   ├── README.md
│   ├── src
│   ├── tsconfig.json
│   ├── upcoming-release-notes
│   └── yarn.lock
└── response.txt
Originally created by @timtjtim on GitHub (Feb 3, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? ActualBudget ### 📂 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. Cannot update Actual Budget using update command / bash and wget command ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Run the update command ### ❌ Paste the full error output (if available). ``` ✔️ Actual Budget Stopped ⠼mv: cannot stat '/opt/actualbudget_bak/.env': No such file or directory [ERROR] in line 51: exit code 0: while executing command mv /opt/actualbudget_bak/.env /opt/actualbudget ``` ### 🖼️ Additional context (optional). File structure of `/opt` (depth 1): ``` /opt/ ├── actualbudget │ ├── app.js │ ├── babel.config.json │ ├── docker │ ├── docker-compose.yml │ ├── Dockerfile │ ├── jest.config.json │ ├── jest.global-setup.js │ ├── jest.global-teardown.js │ ├── LICENSE.txt │ ├── migrations │ ├── package.json │ ├── README.md │ ├── src │ ├── tsconfig.json │ ├── upcoming-release-notes │ └── yarn.lock ├── actualbudget_self_bk │ ├── app.js │ ├── babel.config.json │ ├── docker │ ├── docker-compose.yml │ ├── Dockerfile │ ├── jest.config.json │ ├── jest.global-setup.js │ ├── jest.global-teardown.js │ ├── LICENSE.txt │ ├── migrations │ ├── package.json │ ├── README.md │ ├── src │ ├── tsconfig.json │ ├── upcoming-release-notes │ └── yarn.lock └── response.txt ```
saavagebueno commented 2025-11-20 04:48:57 -05:00
Author
Owner
Copy Link

@maciejmatczak commented on GitHub (Feb 3, 2025):

With this one you'd need install Actual from scratch - the install script we used was "pre" era of using .env file. This change seemed non back compatible.

I just did that 1 hour ago. Sync actual, make actual export data, close browser. Make a Proxmox backup. Delete node, install from scratch. On next connect, Actual prompt me to register my budget file (yup, the one locally saved in my browser :P). It totally automagically worked.

@maciejmatczak commented on GitHub (Feb 3, 2025): With this one you'd need install Actual from scratch - the install script we used was "pre" era of using .env file. This change seemed non back compatible. I just did that 1 hour ago. Sync actual, make actual export data, close browser. Make a Proxmox backup. Delete node, install from scratch. On next connect, Actual prompt me to _register_ my budget file (yup, the one locally saved in my browser :P). It totally automagically worked.
saavagebueno commented 2025-11-20 04:48:57 -05:00
Author
Owner
Copy Link

@timtjtim commented on GitHub (Feb 3, 2025):

@maciejmatczak yeah though that might be the answer - thanks!

Good reminder of why we take a backup from the browser before any update

@timtjtim commented on GitHub (Feb 3, 2025): @maciejmatczak yeah though that might be the answer - thanks! Good reminder of why we take a backup from the browser before any update
saavagebueno commented 2025-11-20 04:48:57 -05:00
Author
Owner
Copy Link

@mellowism commented on GitHub (Feb 10, 2025):

With this one you'd need install Actual from scratch - the install script we used was "pre" era of using .env file. This change seemed non back compatible.

I just did that 1 hour ago. Sync actual, make actual export data, close browser. Make a Proxmox backup. Delete node, install from scratch. On next connect, Actual prompt me to register my budget file (yup, the one locally saved in my browser :P). It totally automagically worked.

I just tried this, and got this message when trying to reinstall again: [PINNER_PID: unbound variable](environment: line 67: SPINNER_PID: unbound variable). Any idea why this is?

@mellowism commented on GitHub (Feb 10, 2025): > With this one you'd need install Actual from scratch - the install script we used was "pre" era of using .env file. This change seemed non back compatible. > > I just did that 1 hour ago. Sync actual, make actual export data, close browser. Make a Proxmox backup. Delete node, install from scratch. On next connect, Actual prompt me to _register_ my budget file (yup, the one locally saved in my browser :P). It totally automagically worked. I just tried this, and got this message when trying to reinstall again: [PINNER_PID: unbound variable](environment: line 67: SPINNER_PID: unbound variable). Any idea why this is?
saavagebueno commented 2025-11-20 04:48:57 -05:00
Author
Owner
Copy Link

@maciejmatczak commented on GitHub (Feb 10, 2025):

Spinner? Sounds rather like an issue with common parts in Helper Scripts, not related (maybe) to Actual.

@maciejmatczak commented on GitHub (Feb 10, 2025): Spinner? Sounds rather like an issue with common parts in Helper Scripts, not related (maybe) to Actual.
saavagebueno commented 2025-11-20 04:48:57 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 10, 2025):

was a bug into core. its fixed since 20min

@MickLesk commented on GitHub (Feb 10, 2025): was a bug into core. its fixed since 20min
saavagebueno commented 2025-11-20 04:48:57 -05:00
Author
Owner
Copy Link

@mellowism commented on GitHub (Feb 10, 2025):

was a bug into core. its fixed since 20min

I restarted the node, and tried again and that worked. Thought it was the restart that did it, but I guess not :) Thanks!

@mellowism commented on GitHub (Feb 10, 2025): > was a bug into core. its fixed since 20min I restarted the node, and tried again and that worked. Thought it was the restart that did it, but I guess not :) Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#464
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?