@atomicnicholas We’re fully aware that this may be a hinderance for some, but while this may seem like a years long “error”, it’s actually a welcomed protection built into the Akamai api layer. We do have documentation on how to resolve this issue. Have you tried anything on this list yet?
What a lot of folks don’t know – is that on “shared hosting”, you’re “sharing” an IP address amongst many different account owners that is being used for PHP CURL… and that IP address might be tied to something which was registered by Akamai as something to block.
Your specific domain IP might not actually be the one which is being blocked, but the PHP CURL might be using this IP address if not defined in your php constants.
We have a way to override this setting on your server so PHP CURL will actually make use of the proper ip address of your domain on the machine. This would be step 1. Insert your actual IP address into this setting, and that might actually resolve your problem.
Also – we have instructions on how to test your environment here which could end up where you get a dedicated IP address, or possibly move to another server which is dedicated to your site alone. There are many hosting options which are available that provide this type of “add on” if you’re not using a bare bones machine.
We would hope that after hearing this – that you might be able to take this information above and resolve your issues.
Let us know if we can be of any other help.