Cannot create distribution

Not able to create distribution. Get the following response on Chrome (inspect element) https://website.com/wp-admin/admin-ajax.php?action=wpaac_create_cdn&domain=website.com&accessid=<accessid>&secretkey=<secretkey>&cachepolicy=4135ea2d-6df8-44a3-9df3-4b5a84be39ad&tlsver=SSLv3&compressobject=false&priceclass=PriceClass_100&subfolder=&awsid=&certarn=NA&custom=No&customdomain=<website>&nonce=21b2a2df55&referrer=https%3A%2F%2Fwebsite.com%2F%3Fpage%3Dwpa-aws-setup Status Code: 500 internal server error The user created on AWS has correct permission. (CloudfrontFullAccess and AWS CertificateManagerFullAccess). Using nginx server on AWS Linux 2023. (php v8.1) I have done this setup on multiple websites without issues. Help appreciated. Server rebooted. Cache cleared. Tried defining access id and secretkey in wp-config.php, but no joy. Hello @shezad Can you check the nginx logs on the server and lmk whats causing the Status Code: 500 internal server error Nginx Access.log 172.xx.xxx.xxx - - [24/Oct/2023:11:43:41 +0700] "GET /wp-admin/admin-ajax.php?action=wpaac_create_cdn&domain=domain.com&accessid=ACCESSID&secretkey=SECRETKEY&cachepolicy=4135ea2d-6df8-44a3-9df3-4b5a84be39ad&tlsver=SSLv3&compressobject=false&priceclass=PriceClass_100&subfolder=&awsid=&certarn=NA&custom=No&customdomain=cdn.domain.com&nonce=5bc7f2a949&referrer=https%3A%2F%2Fdomain.com%2F%3Fpage%3Dwpa-aws-setup HTTP/1.1" 500 166 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36" "244.xxx.xx.xxx" 172.xx.xxx.xxx - - [24/Oct/2023:11:44:06 +0700] "POST /wp-admin/admin-ajax.php HTTP/1.1" 200 78 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36" "244.xxx.xx.xxx" This reply was modified 2 years, 7 months ago by shezad . This reply was modified 2 years, 7 months ago by shezad . Error.log 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http request line: "GET /wp-admin/admin-ajax.php?action=wpaac_create_cdn&domain=domain.com&accessid=ACCESSID&secretkey=SECRETKEY&cachepolicy=4135ea2d-6df8-44a3-9df3-4b5a84be39ad&tlsver=SSLv3&compressobject=false&priceclass=PriceClass_100&subfolder=&awsid=&certarn=NA&custom=No&customdomain=cdn.domain.com&nonce=6cec46b618&referrer=https%3A%2F%2Fdomain.com%2F%3Fpage%3Dwpa-aws-setup HTTP/1.1" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http uri: "/wp-admin/admin-ajax.php" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http args: "action=wpaac_create_cdn&domain=domain.com&accessid=ACCESSID&secretkey=SECRETKEY&cachepolicy=4135ea2d-6df8-44a3-9df3-4b5a84be39ad&tlsver=SSLv3&compressobject=false&priceclass=PriceClass_100&subfolder=&awsid=&certarn=NA&custom=No&customdomain=cdn.domain.com&nonce=6cec46b618&referrer=https%3A%2F%2Fdomain.com%2F%3Fpage%3Dwpa-aws-setup" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http exten: "php" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 posix_memalign: 0000AAAAE230A530:4096 @16 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http process request header line 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "Host: domain.com" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "Connection: Keep-Alive" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "accept-encoding: gzip, br" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "X-Forwarded-For: 244.xxx.xx.xxx” 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "CF-RAY: 81afcbab9ed8272e-BKK" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "X-Forwarded-Proto: https" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "CF-Visitor: {"scheme":"https"}" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "sec-ch-ua: "Chromium";v="118", "Google Chrome";v="118", "Not=A?Brand";v="99"" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "accept: */*" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "x-requested-with: XMLHttpRequest" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "sec-ch-ua-mobile: ?0" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "sec-ch-ua-platform: "macOS"" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "sec-fetch-site: same-origin" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http header: "sec-fetch-mode: cors" 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http alloc large header buffer 2023/10/24 12:24:49 [debug] 92449#92449: *13523 malloc: 0000AAAAE20C8010:8192 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http large header alloc: 0000AAAAE20C8010 8192 2023/10/24 12:24:49 [debug] 92449#92449: *13523 http large header copy: 11 Any help would be appreciated. I experienced a similar issue with another script, which might be relevant for you. AWS sometimes blocks curl and SMTP requests for certain accounts, even when the connection originates from the same source. Interestingly, AWS may blacklist its own IP addresses or place them on a bad reputation list if the account owner has a poor account reputation. Instances like missing a payment or delayed bill payments can lead to unexpected errors on your server. It sounds unusual, but it’s true.