New accessory: CP Analytics
Development and Programming
Sorry guys – I just can’t reproduce this problem with credentials not validating.
Could someone try creating a fresh Google account, hook it up to Analytics, and try that to see if it’s account-specifc (as opposed to maybe server-speciifc)?
I was able to connect to this same GA account from another EE site (hosted on another server), so I don’t think it is the Google account.
OK, that’s a start … so can you tell me what the differences are between the two server environments?
The problematic one is on a Windows Server 2003 GoDaddy dedicated server. The one that works fine is setup on a GoDaddy hosting account, Linux server. Using the same GA account, linux-served site seems to be able to authenticate fine and list available profiles, Windows-based site will not. Is there something that gets posted into the db when you submit your GA username/pw that we can check for?
In the ext_extensions table, the ‘settings’ column should contain a serialized array. If peek inside it, there should be a ‘user’ value, a ‘password’ value (which will be base64-encoded), and an ‘authenticated’ value (this is set to ‘y’ if the credentials validate when saving the settings).
It looks like the database isn’t storing the information on submission? -> After submitting (and getting the authentication error) the username and password remain blank and authenticated remains “n”. This Google account is valid and does authenticate on a linux server with same account settings.
Would you be OK with giving me CP access so I could tinker for a minute? Perhaps FTP access as well?
Hey folks – rt30000 let me in to his server to troubleshoot this, and it turns to to be a problem with Windows servers which do not have OpenSSL enabled in php.ini. Enabling OpenSSL did the trick.
I just pushed a new version with a small fix that allows longer connection time when using fopen as well, in case the connection times out. It also notes the OpenSSL requirement in the readme now.