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

Actual Budget unreachable after reboot #2152

New Issue
Closed
opened 2025-11-20 05:24:17 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 05:24:17 -05:00
Owner
Copy Link

Originally created by @DenSinH on GitHub (Oct 20, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Actual Budget

📂 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)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/8.4.1/2a5fa54a8503f96d (running kernel: 6.8.12-9-pve)

📝 Provide a clear and concise description of the issue.

First seemingly something was going wrong configuring a static IP. I ran the script, set the IP that I wanted it to have, but it would complain about the LXC not having network. Then I decided to install it with the default settings, and change the IP after installation. I could not reach actual budget, even though I could open a console in proxmox and see that the IP was indeed as I configured, and the actualbudget systemd service was running (and listening). I was in fact going to the right port as well (5006). I then decided to first install with default settings, and try and see if I could reach it through the DHCP assigned IP. I could indeed, but then after restarting the LXC, I couldn't reach the service anymore, even though it even got assigned the same IP... I am not sure what I could be doing wrong here. I am able to ping the LXC, but a curl to the IP:5006 just gives me an empty reply...

🔄 Steps to reproduce the issue.

  1. Install LXC
  2. Reboot LXC
  3. You can no longer reach it (or at least I can't)

❌ Paste the full error output (if available).

There is no error output

🖼️ Additional context (optional).

No response

Originally created by @DenSinH on GitHub (Oct 20, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Actual Budget ### 📂 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)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/8.4.1/2a5fa54a8503f96d (running kernel: 6.8.12-9-pve) ### 📝 Provide a clear and concise description of the issue. First seemingly something was going wrong configuring a static IP. I ran the script, set the IP that I wanted it to have, but it would complain about the LXC not having network. Then I decided to install it with the default settings, and change the IP after installation. I could not reach actual budget, even though I could open a console in proxmox and see that the IP was indeed as I configured, and the actualbudget systemd service was running (and listening). I was in fact going to the right port as well (5006). I then decided to first install with default settings, and try and see if I could reach it through the DHCP assigned IP. I could indeed, but then after restarting the LXC, I couldn't reach the service anymore, even though it even got assigned the same IP... I am not sure what I could be doing wrong here. I am able to ping the LXC, but a curl to the IP:5006 just gives me an empty reply... ### 🔄 Steps to reproduce the issue. 1. Install LXC 2. Reboot LXC 3. You can no longer reach it (or at least I can't) ### ❌ Paste the full error output (if available). There is no error output ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:24:17 -05:00
saavagebueno commented 2025-11-20 05:24:18 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 20, 2025):

Looks Like missconfigured. Its an simple npm Tool

Run /usr/bin/actual-server --config /opt/actualbudget-data/config.json

@MickLesk commented on GitHub (Oct 20, 2025): Looks Like missconfigured. Its an simple npm Tool Run /usr/bin/actual-server --config /opt/actualbudget-data/config.json
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 bug
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#2152
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?