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 LXC Error #645

New Issue
Closed
opened 2026-02-04 20:32:44 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 20:32:44 +03:00
Owner
Copy Link

Originally created by @ChristianHandy on GitHub (Mar 16, 2025).

✅ 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?

RELEASE=$(curl -s https://api.github.com/repos/actualbudget/actual/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }')

📝 Provide a clear and concise description of the issue.

Script errors out at line 40.

See shell output:
___ __ __ ____ __ __
/ | / / ______ / / / __ ) / / ____ / /
/ /| |/ / __/ / / / __ / / / __ / / / / __ / __ / _ / /
/ ___ / // // // / // / / / // / // / // / // / / /
// |_/_/_,/_,// /___/_,/_,/__, /_/_/
/___/
⚙️ Using Default Settings on node pve03
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
💾 Disk Size: 4 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🆔 Container ID: 101
🚀 Creating a Actual Budget LXC using the above default settings

✔️ Using local for Template Storage.
✔️ Using Store for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Template is ready to use.
✔️ LXC Container 101 was successfully created.
✔️ Started LXC Container
✔️ Set up Container OS
✔️ Network Connected: 192.168.1.150
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ DNS Resolved github.com to 140.82.121.3
✔️ Updated Container OS
✔️ Installed Dependencies
✔️ Set up Node.js Repository
✔️ Installed Node.js
⠙ Installing Actual Budget
[ERROR] in line 40: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/actualbudget/actual/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }')
root@pve03:~#

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Use the standard and see shell output.

❌ Paste the full error output (if available).

[ERROR] in line 40: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/actualbudget/actual/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }')

🖼️ Additional context (optional).

No response

Originally created by @ChristianHandy on GitHub (Mar 16, 2025). ### ✅ 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? RELEASE=$(curl -s https://api.github.com/repos/actualbudget/actual/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }') ### 📝 Provide a clear and concise description of the issue. Script errors out at line 40. See shell output: ___ __ __ ____ __ __ / | _____/ /___ ______ _/ / / __ )__ ______/ /___ ____ / /_ / /| |/ ___/ __/ / / / __ `/ / / __ / / / / __ / __ `/ _ \/ __/ / ___ / /__/ /_/ /_/ / /_/ / / / /_/ / /_/ / /_/ / /_/ / __/ /_ /_/ |_\___/\__/\__,_/\__,_/_/ /_____/\__,_/\__,_/\__, /\___/\__/ /____/ ⚙️ Using Default Settings on node pve03 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 💾 Disk Size: 4 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🆔 Container ID: 101 🚀 Creating a Actual Budget LXC using the above default settings ✔️ Using local for Template Storage. ✔️ Using Store for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 101 was successfully created. ✔️ Started LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.1.150 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ DNS Resolved github.com to 140.82.121.3 ✔️ Updated Container OS ✔️ Installed Dependencies ✔️ Set up Node.js Repository ✔️ Installed Node.js ⠙ Installing Actual Budget [ERROR] in line 40: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/actualbudget/actual/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }') root@pve03:~# ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Use the standard and see shell output. ### ❌ Paste the full error output (if available). [ERROR] in line 40: exit code 0: while executing command RELEASE=$(curl -s https://api.github.com/repos/actualbudget/actual/releases/latest | grep "tag_name" | awk '{print substr($2, 3, length($2)-4) }') ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 20:32:44 +03:00
OVERLORD commented 2026-02-04 20:32:57 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Mar 16, 2025):

Most likly a issue on your network side, you can not reach github.

Turn off all adblock and dns (like pihole) and so on and try again.

@michelroegl-brunner commented on GitHub (Mar 16, 2025): Most likly a issue on your network side, you can not reach github. Turn off all adblock and dns (like pihole) and so on and try again.
OVERLORD commented 2026-02-04 20:33:01 +03:00
Author
Owner
Copy Link

@ChristianHandy commented on GitHub (Mar 16, 2025):

I disabled all ad blockers and my pihole and also used googles DNS.
The issue still existed, tho.

A manual curl on the proxmox server gave a different error:
root@pve03:~# curl -s https://api.github.com/repos/actualbudget/actual/releases/latest
{"message":"API rate limit exceeded for 79.198.150.15. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"}

There seems to be something wrong with the API or repo on GitHub's site.

@ChristianHandy commented on GitHub (Mar 16, 2025): I disabled all ad blockers and my pihole and also used googles DNS. The issue still existed, tho. A manual curl on the proxmox server gave a different error: root@pve03:~# curl -s https://api.github.com/repos/actualbudget/actual/releases/latest {"message":"API rate limit exceeded for 79.198.150.15. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"} There seems to be something wrong with the API or repo on GitHub's site.
OVERLORD commented 2026-02-04 20:33:05 +03:00
Author
Owner
Copy Link

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

Then its not an Script issue.

Try with an PAT at your node, If this works

@MickLesk commented on GitHub (Mar 16, 2025): Then its not an Script issue. Try with an PAT at your node, If this works
OVERLORD commented 2026-02-04 20:33:08 +03:00
Author
Owner
Copy Link

@ChristianHandy commented on GitHub (Mar 17, 2025):

Thanks for your help.
This fixed my issue.

@ChristianHandy commented on GitHub (Mar 17, 2025): Thanks for your help. This fixed my issue.
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#645
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?