invalid redirect must end with a public top-level domain

Hi @nunyabiz

Thank you for contacting us and we’re sorry to hear that you are experiencing issues with setting up the Google Mailer.

Just to confirm, what type of Google account are you attempting to integrate with the Google SMTP?

Also, just to confirm did you follow each and every step outlined in our documentation and/or video tutorial for setting up the Google mailer?

Note:?Please be sure to sign out of all other Google accounts besides the account you’ll be using for the SMTP setup.

Also, if you’re using Google Workspace, make sure that the Google account you intend on using has permission to send emails.

I hope this helps ??

We are trying to use WP Mail SMTP to send mail from our WPEngine hosted wordpress site.  Yes, we followed the instructions here:

https://wpmailsmtp.com/docs/how-to-set-up-the-gmail-mailer-in-wp-mail-smtp/#create-app

and, yes, were logged out of all other google stuff.

but as the screenshot shows, google rejects the url we are instructed to use:

https://connect.wpmailsmtp.com/google/

Leaving us dead in the water.  Please help.

Hi @nunyabiz

Upon closer inspection, there is a typo in your screenshot.

There is a slash after “connect” where there should be a dot. So instead of https://connect.wpmailsmtp.com/google/ you inserted https://connect/wpmailsmtp.com/google/.

Please try reperforming this step with the correct redirect URI. If for some reason the wrong UTI appears on your WP Mail SMTP settings, please let us know.

Ah, thanks for catching that, but it’s immaterial. Please look at the error message:

Invalid Redirect: must end with a public top level domain (such as .com or .org).

The field was rejecting any value that didn’t end with a tld. So /google is fubar.

We tried again today with https://connect.wpmailsmtp.com/google/, no joy.

It’ll be a few days before we can get to deleting the web app and starting from absolute scratch again, but if y’all have no clue I don’t see any other option. Google is a royal pain and seems to make things many more times complicated than necessary. It’s definitely a google issue.

Since I saw that other folks have had this issue I was hopeful that there was some clue so that we didn’t have to do it all over again.

Hi @nunyabiz

Thanks for getting back to us.

I recorded a screencast demonstrating the OAuth Client ID step where the redirect URI doesn’t trigger any error messages: https://a.supportally.com/v/lDYPFD

As I mentioned in the screencast, we are not seeing a clear reason for this issue and would require more information about any differences to the steps or UI that you may be seeing on your end. It may also help to reach out to Google support in case this is an account-specific issue that only occurs every now and then.

If you are open to using a different mailer or connecting to the Google SMTP server via an alternative method, then you can either set follow the instructions in our Other SMTP mailer or one of our other mailers.

MUCH appreciated!

I think it’s going to be easier to start from scratch, so we’ll incorporate your webcast with the other directions when we do so.

I’d like this thread to remain open so I can update it with our solution to maybe help someone else down the road.

Thanks again!

Hey @nunyabiz

Thank you for understanding.

Please note that we don’t close threads. we mark them as resolved after 24 hours, but they can still be responded to. They will automatically close for good if no responses come in after 6 months.

If you ever give the Google mailer another try, we would suggest trying another browser in case a browser extension is causing the issue.

The answer for us seemed to be to go back to the default oauth name. Can’t recall what we had in there, but when we used Web client 1 we were able to enter and save the correct url – https://connect.wpmailsmtp.com/google/.

Go figure…

Hope this helps out someone else.

Hi @nunyabiz

Thank you for keeping us posted.

Just to confirm, were you able to complete the Google Mailer setup process after this?

Yes, all working fine now.