aaP_hzm170 and aaP_urbanbmobility
definitely not a joke people.. Didn't expect this to blow up like that. I don't have notifications turned on. I just logged back in to search something myself and just seen all these responses.
So basically what happens is, when you press the install button, aapanel downloads a bash file to your server to execute. In the execution of the script it first checks for CPU compatibility, then downloads the resources needed, and installes them. Obviously it won't pass because the CPU architecture is not matching what the script wants to see.
Basically what I did was, I press install. I find the bash script it just downloaded, edit the file. I think it was www/server/panel/install/mail_sys.sh
Search for if != "x86_64"
in the script and changed the != to == to avoid the check. I think you had to change it on two places in the script. Right at the top of the script, if I remember correctly all before the 40th / 50th line.
Basically the script says != means IF NOT. So IF CPU architecture IS NOT x86_64, THEN terminate the script. By simply changing that logic, (meaning you tell the script IF CPU Architecture is x86_64, then terminate.) But because your server CPU architecture it not x86_64 it will skip that check to terminate and go it's merry way.... It downloads the resources, installs them and does all the last configs.
After editing the file save it. Open terminal, browse to the file location, and execute the modified script manually. You can google on how to execute .sh files. Basically you'll have to chmod it and then execute it. I'd recommend you execute it with sudo permissions.
Is this enough for people?
Edit: keep in mind the update button to newer versions wont work. You'll have to do this manually each time.. Because of these headaches I decided to go to an intel architecture server. This all now works automated as intended. But if you're willing to go through all that hassle, this is a workaround...