System Information
| Field |
Value |
| Operating System |
Linux - Debian GNU/Linux 13 on x86_64 |
| Product |
AMP ‘Deimos’ v2.7.2.0 (Mainline) |
| Virtualization |
Docker |
| Application |
TeamSpeak 6 |
| Module |
GenericModule |
| Running in Container |
Yes |
| Current State |
Failed |
Problem Description
Issue
When either AMP automatically or I manually try to install newest TeamSpeak 6 version, it shows an “Unable to run” error.
In console:
bash
Download failed from GitHub. Aborting
Reproduction Steps
- Press “Update TeamSpeak 6 Instance” button.
- Wait to Update.
- Uneable to run.
Problem occurs on Arch, in Docker with a fresh installation as well.
As a temporary fix, you can try to go to instance/configuration/updates and set server updates to v6.0.0-beta8 worked for me
Annoyingly, the beta9 release files have been renamed and are in a different format, so the template will need to be updated to cater for that
Template has now been updated - until the TS devs changes stuff again…
Still got this Issue with the Update.
Yes, it was updated again a few hours ago to fix it
Still doesn’t work. 
I thought it was fixed bc the error stopped showing until the old license expired.
What exactly “doesn’t work”?
Download failed from GitHub. Aborting
Windows Server to
Whenever you install the update, it sends a message in the Bash instance log saying that the “beta9” version has been downloaded. After that, however, the update process stops, and you cannot proceed any further. If you press update again, the same thing happens.
Not sure what you are expecting to happen. If the download finishes, it is finished. If you click update again, it updates again.
What am I missing?
The download seems to have been successful, but when trying to update the instance, it simply doesn’t work. It’s the same even if I try to create a whole new instance, it just fails.
Can I offer you some kind of log other that the instance log? Because that one doesn’t say anything other that “the new version has been downloaded”.
That suggests to me you have an issue with your configuration repositories
Delete ADS01/Plugins/ADSModule/DeploymentTemplates/CubeCoders-AMPTemplates-main
Then “fetch latest” on the configuration repositories, and after that either create a new instance or click the down arrow on your TS6 instance tile to update its config
1 Like
Delete ADS01/Plugins/ADSModule/DeploymentTemplates/CubeCoders-AMPTemplates-main
Then “fetch latest” on the configuration repositories, and after that either create a new instance or click the down arrow on your TS6 instance tile to update its config
This fixed the issue for me.
I renamed the teamspeak6 Templates to .old and then stop the Instances and just click update. Done and fixed (for now).
Thanks
I’ve tried deleting the template folder and using “Fetch Latest”, but the update still fails with the same error: Download failed from GitHub. Aborting
Since the Beta 8 key is expired, my server is completely down. Any idea why the GitHub download is still failing even with fresh templates? Is there a workaround?
You may be rate-limited on GitHub. If so, just have to wait
I don’t think it’s a rate-limit issue, because I just tried creating a brand new TeamSpeak 6 instance, and it downloaded everything perfectly without any errors. The “Download failed from GitHub” error only happens when I try to update my existing instance. If it were a GitHub rate-limit, the new instance should have failed as well, right?
What could be blocking the download specifically for an existing instance even after refreshing the templates and “Fetching Latest”? Is there a specific cache within the instance folder that I should look for?
Just fetching latest doesn’t apply them to existing instances
I managed to fix it. The missing step was that I had to go back to the main Instance Overview and click the ‘Download/Update’ arrow on the instance tile itself. I was looking for the option inside the instance’s management pages, which didn’t work. Triggering it from the main menu forced the new templates to apply, and Beta 9 downloaded immediately. Thanks for pointing out that the templates don’t auto-apply!