Hi there!
WP Offload SES Support Team here, Thanks for reaching out with your query we would be happy to assist
Based on that error, it seems that the Access Keys are invalid. Could you please make sure that your AWS access keys are valid and that the IAM user has the “AmazonSESFullAccess” permissions.
Please let us know how that goes.
I can confirm access keys are valid and the IAM user has “AmazonSESFullAccess” permissions.
Prior the setup this site has the domain already verified on AWS and its configured to use Amazon WorkMail.
-
This reply was modified 3 years ago by
jpandino.
Hi @jpandino ,
Thanks for the additional information. If you dismiss that message, and then send another email from the site, does that error come back up?
Amazon WorkMail is different from Amazon SES. Kindly ensure that you have completed your SES account in your AWS dashboard.
https://deliciousbrains.com/wp-offload-ses/doc/quick-start-guide/
Another thing you can try is creating a new access key for the IAM user and using the new key on your site.
You can also follow our guide below for further steps in debugging the issue.
https://deliciousbrains.com/wp-offload-ses/doc/sender-verification-errors/
Yes, the errors keep happening, I am unable to instantiate the AWS SES client. I am unable to proceed after Verify Domain, when the domain is already verified on AWS. Its like its unable to authenticate, the access keys are correct, the permissions are correct. I have SES enabled on AWS.
I tried the same thing in another site on the same server and I got the same results, unable to verify the domain, it not authenticating or trying to using the access key.
I tried with a different AWS account which I am able to use without problems in another site with WP Offload SES and still didn’t work.
Hi @jpandino,
Thank you for the update. We’re sorry to hear the issue persists.
Can you please try editing your wp-config.php file on the server to replace this line:
define( 'WP_DEBUG', false );
With these lines –
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
This will cause all runtime errors, warnings, and notices to be written to /wp-content/debug.log, which will hopefully yield some better information about what’s going on.
Can you please try the process again and then send on the debug.log file if created?
More details about that at https://ww.wp.xz.cn/support/article/editing-wp-config-php/#wp_debug
Once we have finished troubleshooting, you should revert that config change and delete the debug.log file.
This was fixed in v1.6.5.
After upgrading, please dismiss the unverified email address error notice. If it comes back later, that will hopefully not be a false positive and should be looked into.
-IJ