• Resolved beardo

    (@beardo)


    Error authenticating with this Client ID – please create a new one. [Error executing wp_remote_post: Connection timed out after 10000 milliseconds]

    I have set this up in the past and never had this issue – Basically once I fill in the client ID and client secret – it tells me to authenticate and then I get the error above. Any thoughts?

    https://www.ads-software.com/plugins/postman-smtp/

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Jason Hendriks

    (@jasonhendriks)

    Go into the Google dev console, delete the Client ID/Client Secret and create a new one.

    Why? Wrong user logged into Google, or wrong redirect URL, or a new Gmail address that has never been logged into, or Google is just having a bad day.

    Thread Starter beardo

    (@beardo)

    I tried creating a new client ID and got the same result. I went into incognito mode and created another gmail address and setup everything and still encountered that error. There were no other gmail accounts logged into at the time. Could this be a server setting on my end?

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    I’m going to try it right now..

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    You know, re-reading your initial post… you had a timeout. Which is not an error, but Google just taking longer than usual. The plugin waited 10 seconds and then gave up.

    If you’re 100% sure you have no problems reaching https://accounts.google.com from this server, try increasing the Connection Timeout to 30 seconds in the Postman advanced settings.

    is this a new host? Possible firewall issues?

    Thread Starter beardo

    (@beardo)

    This is a new server – and we upgraded our firewall – Here is the most recent error after changing the time to 30 seconds. [Error executing wp_remote_post: Failed to connect to https://www.googleapis.com port 443: Connection timed out]. If you think this is a firewall issue Ill get out server admin to take a look – Thanks!

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    Yes, looks like a firewall. What does the Connectivity Test say?

    Thread Starter beardo

    (@beardo)

    Port 587 is the only one open – all the other ports are closed

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    443 (the secure web port) is closed as well? That explains why you can’t authenticate with Google. Unfortunately you’ll have to use password authentication if you can’t get 443 open.

    Thread Starter beardo

    (@beardo)

    It was that easy ?? opened up that port and everything worked properly! Thanks for instruction.

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    Great!! ??

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Error When Authenticating through Gmail’ is closed to new replies.