Fatal error: Uncaught exception 'Google_IO_Exception' with message 'Couldn't resolve host 'accounts.google.com''

Sometimes, Google library can return the following error:
Fatal error: Uncaught exception 'Google_IO_Exception' with message 'Couldn't resolve host 'accounts.google.com''

This error appear because the server is failing to resolve the accounts.google.com

To correct this, change your resolvers to level3 or comodo, something that is independent from google. Example, put the following in /etc/resolve.conf file:
Once done, restart all the application that was using the google library. If you were using a web version of a php script, restart your apache. If you were using your own app, restart that app by either killing it manually or using your command line tools. This has to be done, is because Linux process will cache the resolver information from the start of it's creation to it's lifetime. Until it restarts, the old resolver information won't reset to the new.

  • resolver, google, google_io_exception
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

R1soft Backup Error - Failed To Backup LVM/MD Configuration

It looks like R1Soft manages it's own lvm.static file to process lvm backups. But sometimes it...

Does R1Soft work with LVM?

It does. But it is not fully supported as of 28th November, 2017. If you have a solid logical...

Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)

CentOS 7 / CloudLinux 7 / RHEL 7 may show the following error while restarting Apache/Exim or...

[957833.048873] EXT4-fs warning (device dm-0): ext4_dx_add_entry:2016: Directory index full!

A dedicated server customer came with an error of failed WHM login. When I tried to enter, I...

lfd on ***.***.***: ModSecurity persistent IP database size alert

LFD was throwing the following error for sometime in a server: ModSecurity persistent IP...