XF 1.3 Unable to Connect to ssl://accounts.google.com:443

[BassMan]

Hi!

I'm having truoble on sign in with Google account. It reports me this server error:

Error Info
Zend_Http_Client_Adapter_Exception: Unable to Connect to ssl://accounts.google.com:443. Error #110: Connection timed out - library/Zend/Http/Client/Adapter/Socket.php:235
Generated By: Unknown Account, pred 16 minutami
Stack Trace
#0 /home/.../public_html/forum/library/Zend/Http/Client.php(973): Zend_Http_Client_Adapter_Socket->connect('accounts.google...', 443, true)
#1 /home/.../public_html/forum/library/XenForo/ControllerPublic/Register.php(864): Zend_Http_Client->request('POST')
#2 /home/.../public_html/forum/library/XenForo/FrontController.php(347): XenForo_ControllerPublic_Register->actionGoogle()
#3 /home/.../public_html/forum/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#4 /home/.../public_html/forum/index.php(13): XenForo_FrontController->run()
#5 {main}
--------------------

It was working fine till yesterday or 2 days ago. Already contacted my host and they say they checked the SSL connection and it is working fine.

Anyone else have the same problem? Could this error be on Google's side?

Thanks in advance.

 

[Mike]

This is a "connection timed out" error, so it could be something on Google's end or something between your server and them (or a firewall, though if your host says it's ok then it may not be that).

Is it consistently happening every time?

 

[BassMan]

Is it consistently happening every time?

Yes, everytime for this 2 days. Maybe I need to wait a bit more.

 

[schroeffu]

Same here. It happend not everytime here. I've configured G+ Login since friday and it's 50%+ not working as it feels ~
Strange thing.

 

[BassMan]

I think it's a Google thing. It suddenly starts working on my site.

 

[schroeffu]

I do have again ~ 50% fails. Most crazy thing: Facebook & G+ Login aren't working at the same time, while Steam+Twitter SSO is running smoothly.
Any Idea? Error Log of apache is clean.

example google fail, the facebook fails it doesn't log

1.3.2 latest stable

Zend_Http_Client_Adapter_Exception: Unable to Connect to ssl://accounts.google.com:443. Error #110: Connection timed out - library/Zend/Http/Client/Adapter/Socket.php:235
Generated By: Unknown Account, 3 minutes ago
Stack Trace
#0 /home/theboard/public_html/library/Zend/Http/Client.php(973): Zend_Http_Client_Adapter_Socket->connect('accounts.google...', 443, true)
#1 /home/theboard/public_html/library/XenForo/ControllerPublic/Register.php(874): Zend_Http_Client->request('POST')
#2 /home/theboard/public_html/library/XenForo/FrontController.php(347): XenForo_ControllerPublic_Register->actionGoogle()
#3 /home/theboard/public_html/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#4 /home/theboard/public_html/index.php(13): XenForo_FrontController->run()
#5 {main}
Request State
array(3) {
["url"] => string(140) "http://steamos-forum.com/index.php?...W6MfOl05ti8ZT3ZtJE8DjAI&csrf=pF9HMj-aTE-OL1Zd"
["_GET"] => array(3) {
["register/google"] => string(0) ""
["code"] => string(62) "4/Aec0gHVWvcjt3ghxaCH8Ms_E0vZk.0gXrZ-aUW6MfOl05ti8ZT3ZtJE8DjAI"
["csrf"] => string(16) "pF9HMj-aTE-OL1Zd"
}
["_POST"] => array(0) {
}
}

 

[TPerry]

contact your host?
sounds like a problem that they need to address.

 

[schroeffu]

contact your host?
sounds like a problem that they need to address.

I am my owm dedicated host :] its just not clear for me how to raise the application debug to see more, a connection timeout could be everything.

If i am really alone with this issue i'm going to tcpdump the thing..

 

[schroeffu]

"Resolved" for mee to. It's definitively an IPv6 issue on my side. Had to deactivte IPv6 to troubleshoot later with a bit more time for it.

 

[KhaytovHit]

All options defined right! And this error very annoying me! What i do wrong? Or what?
extension=openssl.so enabled...

 

[Kerstin28]

"Resolved" for mee to. It's definitively an IPv6 issue on my side. Had to deactivte IPv6 to troubleshoot later with a bit more time for it.

Excellent observation. I had the same issue and went troubleshooting into the wrong direction...