This is one of our most important updates ever! The result of an extensive modernisation project to keep AMPs core fast, secure and maintainable. We’re really excited to bring this release to you, and hope everyone enjoys the improvements.
IMPORTANT NOTICE
It is important to make sure your generic templates are updated! If after updating some generic instances won’t start, update them from ADS to make sure they’re running the latest configuration for your given application.
Thank you to all the testers that helped verify the massive number of changes that went into this release! If you were someone that participated, please be sure to run the following commands to revert to mainline.
For a single instance:
ampinstmgr switch (instancename) mainline true
For all instances:
ampinstmgr switchall mainline true
Update Instructions
Please see the official guide for instructions on updating AMP to the latest version.
What’s changed?
We’ve upgraded almost every major component inside of AMP, moving to newer tooling and libraries to make AMP faster, more secure, and easier to maintain. This includes an upgrade from .NET Framework to .NET 8 and from mHTTP to Microsoft’s built-in Kestrel web server.
In terms of functionality - there have been very few changes this update other than a handful of bug fixes. This release focuses largely on internal modernisation.
Release Notes
Theme hot reloading - No need to refresh the browser
Added HTTP/3 Support
Fix application template syncing - “Ghost changes” no longer prevent pulling the latest templates from the AMPTemplates repo
Application templates are updated prior to creating an instance
Docker images are updated on instance start
Windows installs now include all C++ redistributables, DirectX, and Git to ensure smooth operation of AMP and game servers
Known Issues
Scheduled tasks getting wiped from upgrade
Windows msi outdated - Mike to address build system.
Overlays - permission denied
Overlays - Getting deleted - Fix ready to deploy
Overlays - Getting applied on each update. Not 2.6 directly but should be addressed.
RHEL can’t activate - NoMatchingMachineId
Firewall service failed/syntax error when updating firewall rules on Linux - Fix ready to deploy
We’re very close to finishing taking care of the issues found directly caused by changes in 2.6. If any issues are outstanding, please feel free to ping @IceOfWraith directly here or on Discord.
Bug Fixes and Improvements
Prevent scheduled triggers from running in suspended instances
Fix CPU and RAM usage not updating for metrics and Status tab
Fix LDAP auth not working due to a bad startup order
Add templated values to generic template regex messages
Add nested capability for templated values in generic templates
Correct handling of Direct from Controller access mode
Fix multiple issues with the Deployment Templates tab
Allow the auth provider to use X-Forwarded-For
Convert instances list new statuses to use classes rather than a computed inline style
Add logging to instance stopping to investigate instance stop failures further
Always remove the task notification when stopping an instance (stuck notifications)
Make process checking more resilient
Backups and File Manager archive creation includes retry logic and logging to account for in-use files and other file transfer failures
There will likely be one more update prior to the holidays coming up. Then, we’re planning to slow down (for our sake and yours)! The next update will wait until we have all outstanding issues resolved that were directly caused by the major 2.6 update.
IMPORTANT NOTICE
Be sure to follow the update instructions at the end of this post closely, specifically on Windows. This update includes needed changes to instance status and stopping mechanisms that requires all aspects of AMP to be on the latest version to function properly!
Bug Fixes and Improvements
AMP Instance Manager on Windows not detecting instances properly.
ampinstmgr unable to detect running or stop instances on Windows through command line.
Fixed issue where back to back SteamCMD update stages could fail.
Corrected update check logic for SteamCMD games in scheduled tasks.
Additional logging added to SteamCMD update checking.
SteamCMD update checks now verify against the right release stream.
Smart Backup Exclusions begin at the Base Directory instead of Root. Caused issues with Wine games generating backup exclusions when those directories aren’t backed up anyways.
Git LFS is added to the install scripts on Windows for more game support out of the box.
Solved an issue with iptables generating duplicate rules (up to the hundreds of thousands). This should also clean up existing duplicated rules.
The ADS and instance ports are properly added to the firewall if not bound to localhost.
Fixed an issue where stopping an instance would cause cancellation errors and sometimes fail to stop the instance.
SRCDS maps populate correctly now.
Deprecated the Dota 2 and Left 4 Dead 2 SRCDS modules in favor of the generic templates created by @Greelan
S3 backups automatically upload if set to do so.
Fixed multiple CPU usage calculation issues on Linux. This includes solving the metrics not updating properly for games that use Wine or need child process monitoring.
Added ExitMethodWindows to allow for templates that require different shut down methods based on the OS.
WaitForStartupComplete generic update stage adjusted to check for the app startup properly.
IMPORTANT NOTICE