Error when running update script: "Due to major changes in the Actual Budget repository, we are currently unable to provide updates. Please check back later." #582

Closed
opened 2026-02-04 20:06:28 +03:00 by OVERLORD · 7 comments
Owner

Originally created by @ftbboy2115 on GitHub (Mar 4, 2025).

Have you read and understood the above guidelines?

yes

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

actualbudget.sh

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

For the last 2 updates, I've not been able to update using the script. Last time (for version 25.2.0/1) I got an error about it not finding actual, even though I was in the console of the AB container. Thus, I had to export the files, start up a new container with the script and import my files into it. This time, again I'm getting an error while trying to update with the "updatable" script command (same as the new install script, at least to start with).
The current error is: "Due to major changes in the Actual Budget repository, we are currently unable to provide updates. Please check back later."

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Copy command from Proxmox Helper Scripts page. Paste into Actual Budget console and run.

Paste the full error output (if available).

Due to major changes in the Actual Budget repository, we are currently unable to provide updates. Please check back later.

🖼️ Additional context (optional).

No response

Originally created by @ftbboy2115 on GitHub (Mar 4, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? actualbudget.sh ### 📂 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. For the last 2 updates, I've not been able to update using the script. Last time (for version 25.2.0/1) I got an error about it not finding actual, even though I was in the console of the AB container. Thus, I had to export the files, start up a new container with the script and import my files into it. This time, again I'm getting an error while trying to update with the "updatable" script command (same as the new install script, at least to start with). The current error is: "Due to major changes in the Actual Budget repository, we are currently unable to provide updates. Please check back later." ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Copy command from Proxmox Helper Scripts page. Paste into Actual Budget console and run. ### ❌ Paste the full error output (if available). Due to major changes in the Actual Budget repository, we are currently unable to provide updates. Please check back later. ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 20:06:28 +03:00
Author
Owner

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

that was the Message say. Currently WE dont provide an Update function If its fixed. See other issue #2751

@MickLesk commented on GitHub (Mar 4, 2025): that was the Message say. Currently WE dont provide an Update function If its fixed. See other issue #2751
Author
Owner

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

When I searched for Actual Budget, this other Issue report didn't come up. I didn't see it until just now. But I'm guessing it's related to this other issue: https://github.com/community-scripts/ProxmoxVE/issues/2751

@ftbboy2115 commented on GitHub (Mar 4, 2025): When I searched for Actual Budget, this other Issue report didn't come up. I didn't see it until just now. But I'm guessing it's related to this other issue: https://github.com/community-scripts/ProxmoxVE/issues/2751
Author
Owner

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

that was the Message say. Currently WE dont provide an Update function If its fixed. See other issue

I'm confused... The script says it's updateable

Image

@ftbboy2115 commented on GitHub (Mar 4, 2025): > that was the Message say. Currently WE dont provide an Update function If its fixed. See other issue I'm confused... The script says it's updateable ![Image](https://github.com/user-attachments/assets/ba2ea45d-2e75-4358-9263-5ea6ce059db7)
Author
Owner

@aghadjip commented on GitHub (Mar 4, 2025):

that was the Message say. Currently WE dont provide an Update function If its fixed. See other issue

I'm confused... The script says it's updateable

Image

Im confused as well, fist time updating and receive this message. Is there a path forward or?

@aghadjip commented on GitHub (Mar 4, 2025): > > that was the Message say. Currently WE dont provide an Update function If its fixed. See other issue > > I'm confused... The script says it's updateable > > ![Image](https://github.com/user-attachments/assets/ba2ea45d-2e75-4358-9263-5ea6ce059db7) Im confused as well, fist time updating and receive this message. Is there a path forward or?
Author
Owner

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

Lol. Guys, I took out the update function this week. I described it the same way. What's the wave you guys are making? The whole repo has changed from them. Before every script breaks, we took everything out and just updated the installation.

Just wait and see. Such an unrelaxing thing.

@MickLesk commented on GitHub (Mar 4, 2025): Lol. Guys, I took out the update function this week. I described it the same way. What's the wave you guys are making? The whole repo has changed from them. Before every script breaks, we took everything out and just updated the installation. Just wait and see. Such an unrelaxing thing.
Author
Owner

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

Just so I understand, this is closed as unplanned... So, does that mean every month or less when there's an update, I'll need to export all the files (about 6 for my family), spin up a new CT, point everything to that new one including routing, and move everything over to it, including importing the 6 exported files?
And because this is closed unplanned, that means this is the intention to remain this way?

@ftbboy2115 commented on GitHub (Mar 4, 2025): Just so I understand, this is closed as unplanned... So, does that mean every month or less when there's an update, I'll need to export all the files (about 6 for my family), spin up a new CT, point everything to that new one including routing, and move everything over to it, including importing the 6 exported files? And because this is closed unplanned, that means this is the intention to remain this way?
Author
Owner

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

Are you a little bit stupid? The fix comes in next days. Linked over other Issue.
We all have an live, and we dont jump for every dude that sends an request.

For the Reddit Guys:
https://github.com/community-scripts/ProxmoxVE/issues/2751

Here are all marked, we work on it.

@MickLesk commented on GitHub (Mar 4, 2025): Are you a little bit stupid? The fix comes in next days. Linked over other Issue. We all have an live, and we dont jump for every dude that sends an request. For the Reddit Guys: https://github.com/community-scripts/ProxmoxVE/issues/2751 Here are all marked, we work on it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#582