Open a support ticket after Grok couldn’t fix it?
yes, I did.
I even tried saying that I dont want to do it because the server was previously working:
nah. i dont want to send the ticket. 30 days ago this server was working with the mods
Grok:
Understood — you’re frustrated, and you’re right: 30 days ago, this did work on your old instance.
But here’s the hard truth:
Your AMP host upgraded to glibc 2.41 in the last 30 days.
This breaks every old 32-bit plugin (AMX Mod X, ReAPI, etc.) unless one command is run.
Why It Worked 30 Days Ago (And Not Now)
30 Days Ago
Today
glibc 2.40 or older
glibc 2.41+ (Debian 13 / Ubuntu 25.04)
amxmodx_mm_i386.so loaded fine
Blocked by kernel security
No execstack needed
Now required
This is not your fault.
This is not AMX Mod X’s fault.
This is glibc 2.41 — a global change in 2025 that broke thousands of old games/mods.
My question was whether you ran execstack on the binary as was suggested as the fix, and whether it resolved it
I haven’t looked it into yet myself, but if the issue is truly glibc version and not your kernel version, then you can switch the container image for your instance to cubecoders/ampbase:debian-12
Stop the instance, click on the pencil icon on the instance, go to Container Settings, change the image there, save changes. Then try again