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

Gotify latest release filename changed - No asset matching 'gotify-linux-amd64.zip' found #1616

New Issue
Closed
opened 2026-02-05 01:46:29 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 01:46:29 +03:00
Owner
Copy Link

Originally created by @c-murgrabia on GitHub (Sep 13, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Gotify

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

8.4.12

📝 Provide a clear and concise description of the issue.

Hello. First things first: thank you all for the good work here!
And to the point: it seems that gotify changed the file names in their releases. Deployment script can't find newest release in GH. I don't know if there's something to be done in helper script or should I wait for gotify to properly name release files.

Cheers,
Cezary

🔄 Steps to reproduce the issue.

Step 1: Use script for gotify automatic deployment

❌ Paste the full error output (if available).

✖️ No asset matching 'gotify-linux-amd64.zip' found

[ERROR] in line 16: exit code 0: while executing command return 1

[ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

🖼️ Additional context (optional).

Gotify latest release: https://github.com/gotify/server/releases - inconsistent filenames vs previous releases.

Originally created by @c-murgrabia on GitHub (Sep 13, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Gotify ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/gotify.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 8.4.12 ### 📝 Provide a clear and concise description of the issue. Hello. First things first: thank you all for the good work here! And to the point: it seems that gotify changed the file names in their releases. Deployment script can't find newest release in GH. I don't know if there's something to be done in helper script or should I wait for gotify to properly name release files. Cheers, Cezary ### 🔄 Steps to reproduce the issue. Step 1: Use script for gotify automatic deployment ### ❌ Paste the full error output (if available). ✖️ No asset matching 'gotify-linux-amd64.zip' found [ERROR] in line 16: exit code 0: while executing command return 1 [ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)" ### 🖼️ Additional context (optional). Gotify latest release: https://github.com/gotify/server/releases - inconsistent filenames vs previous releases.
OVERLORD added the bug label 2026-02-05 01:46:29 +03:00
OVERLORD commented 2026-02-05 01:46:38 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 13, 2025):

When did you running the Script? Directly at new Version? Sometimes the tarballs Missing at First minutes. All Look good. Script and there repo

@MickLesk commented on GitHub (Sep 13, 2025): When did you running the Script? Directly at new Version? Sometimes the tarballs Missing at First minutes. All Look good. Script and there repo
OVERLORD commented 2026-02-05 01:46:40 +03:00
Author
Owner
Copy Link

@c-murgrabia commented on GitHub (Sep 13, 2025):

I've tried to install it like 30 minutes ago and it seems it was a very unfortunate timing 🥲 Now I see there are all build files in gotify repo and the script is working like a charm.
Thanks!

@c-murgrabia commented on GitHub (Sep 13, 2025): I've tried to install it like 30 minutes ago and it seems it was a very unfortunate timing 🥲 Now I see there are all build files in gotify repo and the script is working like a charm. Thanks!
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
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#1616
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?