The PBX is running fine otherwise. Full internet connectivity. The Sangoma-base.repo file is identical to the file on a PBX that can run yum update. The 500 error from the sangoma mirrorlist appears legitimate.
Version numbers? I have a theory that it’s using the old names and you may need to manually update the Advanced Configuration page to get them working.
readonly settings were already enabled. I know the edge mode setting is in there for modules, but I don’t see anything for package updates.
Yeah I thought maybe the AWS outage may have been the problem as well, but it’s still erroring out today. I didn’t know Sangoma was down for maintenance. Regardless, both are back up now according to their status pages.