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 11 Packages Projects Releases 10 Wiki Activity

Vikunja v1 update not working #2439

New Issue
Closed
opened 2026-02-05 04:51:59 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-05 04:51:59 +03:00
Owner
Copy Link

Originally created by @apachelance on GitHub (Feb 3, 2026).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

No response

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

Vikunja

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

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📈 Which Proxmox version are you on?

latest

📝 Provide a clear and concise description of the issue.

I saw that @CrazyWolf13 fixed the update script for Vikunja (https://github.com/community-scripts/ProxmoxVE/pull/11308). However, it is not working (at least for me). I am running Vikunja 0.24.6 und wanted to update to the latest v1.

🔄 Steps to reproduce the issue.

Run update inside LXC

❌ Paste the full error output (if available).

root@vikunja:~# update
curl: (22) The requested URL returned error: 404

🖼️ Additional context (optional).

No response

Originally created by @apachelance on GitHub (Feb 3, 2026). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? _No response_ ### 📜 What is the name of the script you are using? Vikunja ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📈 Which Proxmox version are you on? latest ### 📝 Provide a clear and concise description of the issue. I saw that @CrazyWolf13 fixed the update script for Vikunja (https://github.com/community-scripts/ProxmoxVE/pull/11308). However, it is not working (at least for me). I am running Vikunja 0.24.6 und wanted to update to the latest v1. ### 🔄 Steps to reproduce the issue. Run update inside LXC ### ❌ Paste the full error output (if available). root@vikunja:~# update curl: (22) The requested URL returned error: 404 ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 04:51:59 +03:00
OVERLORD commented 2026-02-05 04:52:07 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 3, 2026):

Whats inside of /usr/bin/update?

@MickLesk commented on GitHub (Feb 3, 2026): Whats inside of /usr/bin/update?
OVERLORD commented 2026-02-05 04:52:12 +03:00
Author
Owner
Copy Link

@apachelance commented on GitHub (Feb 3, 2026):

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/raw/main/ct/vikunja.sh)"

@apachelance commented on GitHub (Feb 3, 2026): `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/raw/main/ct/vikunja.sh)"`
OVERLORD commented 2026-02-05 04:52:19 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Feb 3, 2026):

@apachelance
Seems like you got the wrong URL, there is a /raw too much in there, why I ended up there I can't tell you, maybe you edited manually or some core logic broke? @MickLesk any ideas?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/vikunja.sh)"
@CrazyWolf13 commented on GitHub (Feb 3, 2026): @apachelance Seems like you got the wrong URL, there is a /raw too much in there, why I ended up there I can't tell you, maybe you edited manually or some core logic broke? @MickLesk any ideas? ```bash bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/vikunja.sh)" ```
OVERLORD commented 2026-02-05 04:52:26 +03:00
Author
Owner
Copy Link

@apachelance commented on GitHub (Feb 3, 2026):

@CrazyWolf13 I did not modify the update file. Now the update is working. Thanks.

@apachelance commented on GitHub (Feb 3, 2026): @CrazyWolf13 I did not modify the update file. Now the update is working. Thanks.
OVERLORD commented 2026-02-05 04:52:37 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 3, 2026):

looks like something DNS shit - your lxc cant reach api.github.

curl -4 -sv https://api.github.com/ -o /dev/null

nvm, wrong path okay.

@MickLesk commented on GitHub (Feb 3, 2026): looks like something DNS shit - your lxc cant reach api.github. curl -4 -sv https://api.github.com/ -o /dev/null nvm, wrong path okay.
OVERLORD commented 2026-02-05 04:52:42 +03:00
Author
Owner
Copy Link

@apachelance commented on GitHub (Feb 3, 2026):

Sorry, my fault. The firewall was blocking it. I adjusted my comment.

@apachelance commented on GitHub (Feb 3, 2026): Sorry, my fault. The firewall was blocking it. I adjusted my comment.
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#2439
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?