Google analytics connector error
I am setting up GA connector and currently getting this error
Could not retrieve authorization url from Google: Error getting HTTP response
Do I need to open a port or anything? Something else?
I noticed someone mention issues with SSL, we do have Java w/ ssl in case that matters
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Mike on 09 Jun, 2011 05:26 PM
Hi,
Does your Cascade instance have internet access? The Analytics Connector makes http/https requests to google to verify the connector as well as to retrieve analytics data. So, if the machine on which Cascade is running cannot make http/https requests to the internet, then it is not possible to import analytics data.
Are there any relevant message being output to the log file about this? You may need to enable logging for the com.hannonhill.cascade.model.dom.GoogleAnalyticsConnector class to see any messages. To enable logging, go to the System menu -> Utilities -> Logging. Then enter the class name I just listed, set the dropdown value to "DEBUG" and then submit.
2 Posted by mherzberger on 09 Jun, 2011 09:01 PM
By default we dont allow outgoing traffic from behind firewall. But I
can create exceptions by IP range. Do you per chance know the IP range
for GA? I will setup the log tomorrow.
-Matt
3 Posted by Bradley Wagner on 09 Jun, 2011 09:43 PM
We don't. We access 2 of Google's Analytics services:
https://www.google.com/analytics/feeds/data
https://www.google.com/analytics/feeds
Is it possible to open up access to a host instead?
4 Posted by mherzberger on 10 Jun, 2011 01:32 PM
K I am checking with networking. I know usually they can only add exceptions via IP not via url. So I am seeing if there is a work around. Have any other customers had this issue? Did they have a fix?
5 Posted by Bradley Wagner on 10 Jun, 2011 02:10 PM
Not so far.
There are other functions in the CMS such as external link checking that require the CMS being able to make outbound HTTP and HTTPS connections so we would generally recommend that you allow Cascade to make any port 80 and maybe port 443 requests that it wants, if possible.
Here's more info about the external link checker and our inbound/outbound port usage for the server
6 Posted by mherzberger on 14 Jun, 2011 10:16 PM
So to clarify we use ssl if I need my network team what ports are they doing it on? Is it 80 443 or 8080 8443?
7 Posted by Bradley Wagner on 14 Jun, 2011 10:20 PM
If we're talking about outbound ports from the CMS machine, it's 80 and 443.
8 Posted by mherzberger on 15 Jun, 2011 02:02 PM
OK I got it to verify then I did my first manual sync and got the following
An error occurred: Hibernate flushing: could not insert: [com.hannonhill.cascade.model.dom.AssetStats]; uncategorized SQLException for SQL [insert into cxml_assetstats (siteId, connectorId, assetId, url, shortUrl, hashedUrl, visits, visitsPercentChange, uniquePageviews, uniquePageviewsPercentChange, absoluteUniqueVisitors, absUnqVisitorsPercentChange, pageViews, pageViewsPercentChange, bounceRate, bounces, exits, bounceRatePercentChange, entrances, totalTime, averageTime, averageTimePercentChange, averageTimeOnSite, averageTimeOnSitePercentChange, timeInterval, id) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; SQL state [HY000]; error code [1366]; Incorrect string value: '\xF4\x80\x86\x9Fon...' for column 'url' at row 1; nested exception is java.sql.BatchUpdateException: Incorrect string value: '\xF4\x80\x86\x9Fon...' for column 'url' at row 1
9 Posted by Mike on 15 Jun, 2011 02:23 PM
Are you using MySQL? If so, can you please execute the following query against your database and post the result here.
Could you also attach your log file after manually syncing? (make sure the logging I mentioned in comment 2 is turned on).
10 Posted by mherzberger on 15 Jun, 2011 03:20 PM
Attached is the results out.tab
and the log is a zip
11 Posted by cpayan on 19 Jul, 2011 04:24 PM
This error appears to have existed before the existing version of 6.8 as well. We're running 6.8.2, so I guess this problem still made it into the final release of 6.8?
Support Staff 12 Posted by Tim on 24 Feb, 2012 09:16 PM
Matt,
When you have a chance, can you please execute the following query and provide us with the results?
Thanks
13 Posted by mherzberger on 13 Mar, 2012 03:51 PM
Here you go
14 Posted by chaoaj on 26 May, 2012 11:38 AM
Has this been resolved? We are having some similar flaky issues with GA connector. It was verified and pulling data previously then all of a sudden stopped.
Now when I go to reverify it just spins for a long time.
I can curl the two feed urls Bradley gave from the appserver so I don't think our issue is a network one.
15 Posted by Bradley Wagner on 29 May, 2012 02:33 PM
Alvin, are you seeing any specific errors in the log around the time that the sync stops working?
16 Posted by chaoaj on 29 May, 2012 03:25 PM
Bradley,
None that I can see. I can't get the verify going at this point. What
port / ip address guidelines can you give for verification requests does
it just need these:
https://www.google.com/analytics/feeds/data
https://www.google.com/analytics/feeds
Regards,
@lvin
------------------------
Alvin Chao IT Web
JMU - MSC 5734 - Massanutten Hall 293
Harrisonburg, VA 22807
540-568-6206
[email blocked]
http://educ.jmu.edu/~chaoaj
17 Posted by Bradley Wagner on 29 May, 2012 03:32 PM
Port 80 and 443 should be the only required ports.
I'm not having much luck tracking down a range of IP addresses for the Google Analytics service itself as I'm pretty sure Google is using some kind of round-robin DNS. Basically, I would expect the machine to need access to any of the IPs used for Google services hosted off the main domain: www.google.com.
18 Posted by chaoaj on 31 May, 2012 02:13 PM
Bradley,
Are there other ports or addresses needed for the Verify action to occur?
That's now the step I'm getting stopped at. We've opened to all
google.com ip's but only 80/443.
Regards,
@lvin
------------------------
Alvin Chao IT Web
JMU - MSC 5734 - Massanutten Hall 293
Harrisonburg, VA 22807
540-568-6206
[email blocked]
http://educ.jmu.edu/~chaoaj
19 Posted by Bradley Wagner on 31 May, 2012 02:37 PM
Alvin, when you click "verify", is the system prompting you to click verify again or is it not getting that far?
From what I can tell, all the URLs we're hitting look something like this:
so again outbound 443 to www.google.com IPs should cover it.
20 Posted by chaoaj on 31 May, 2012 02:39 PM
Not getting that far, just spins when I click verify. We have 443 and 80
open to google.com but accounts.google.com seems to be another step in the
routing.
@lvin
------------------------
Alvin Chao IT Web
JMU - MSC 5734 - Massanutten Hall 293
Harrisonburg, VA 22807
540-568-6206
[email blocked]
http://educ.jmu.edu/~chaoaj
21 Posted by Bradley Wagner on 31 May, 2012 02:57 PM
Yea, it does look like https://www.google.com/accounts/OAuthAuthorizeToken redirects to https://accounts.google.com so you may need to open up ports for that as well.
22 Posted by Ryan Griffith on 27 Aug, 2012 02:15 PM
Hi Alvin,
I was going over some older discussions and noticed this one is still open. Were you able to get your GA Connector verified and functional?
Please feel free to let us know if you have any other questions.
Thanks.
23 Posted by chaoaj on 27 Aug, 2012 02:18 PM
Ryan,
Yes, you can close my end of this one.
Regards,
@lvin
------------------------
Alvin Chao IT Web
JMU - MSC 5734 - Massanutten Hall 293
Harrisonburg, VA 22807
540-568-6206
[email blocked]
http://educ.jmu.edu/~chaoaj
24 Posted by Ryan Griffith on 27 Aug, 2012 02:34 PM
Thank you, Alvin.
mherzberger, were you able to get your GA Connector verified and functional?
Please let us know if you have any questions.
Thanks!
25 Posted by mherzberger on 27 Aug, 2012 03:15 PM
Yeah I am good
-Matt
Sent from my iPhone
26 Posted by Ryan Griffith on 27 Aug, 2012 06:01 PM
Glad to hear, thank you!
I'm going to go ahead and close this discussion, but please feel free to reply or comment to re-open this discussion if you have any additional questions.
Thanks.
Ryan Griffith closed this discussion on 27 Aug, 2012 06:01 PM.