Request Timed Out

Peter Hinton

unread,

Nov 2, 2013, 12:17:43 PM11/2/13

to google-analyti...@googlegroups.com

Hi,

I think the superproxy is exactly what I need to show my clients an overview of their Google Analytcs data, but I'm receiving a "Request Timed Out" error and I can't figure out why, nor can I find any help about this online.

A test page can be found http://www.peterhintondesign.co.uk/superproxy.html, the page is blank for about 20s then the error appears. Has anyone come across this before?

Thanks in advance,

Peter

Peter Hinton

unread,

Nov 4, 2013, 5:26:49 AM11/4/13

to google-analyti...@googlegroups.com

I think the issue is actually with appspot.com.

About 90% of the time I try and load my admin panel on appspot.com I get a blank page, the source code is:

<html><head><title>s~peterhintondesign : uncaught application failure</title><body><pre>
<br></pre></body></html>

The ~10% of the time appspot.com loads for me the Google Chart works avoiding the 'Request Timed Out' error.

Pete

unread,

Nov 4, 2013, 7:16:10 PM11/4/13

to google-analyti...@googlegroups.com

seems like there is a lot more going on that page than just a Google Chart, however it does load for me with a lot of JS errors.

If you want to check if the data request is timing out just visit the superProxy query URL directly (e.g. the url yourapp.appspot.com/query?id=query_id&format=data-table-response) and see if it is timing out, i think it's probably fine.

My suggestion is to start simple and get one chart working. If that works then keep adding. if you want to load multiple charts and you're not that familiar with JavaScript or Google Charts make sure you follow the example code.

Peter Hinton

unread,

Nov 6, 2013, 4:49:08 AM11/6/13

to google-analyti...@googlegroups.com

Hi Pete

Thanks for the response, much appreciated. I followed the example chart from the beginning and modified it to get to where I was, however in light of you're advice I started over from scratch.

Unfortunately I'm still receiving time-out errors...

I got the example pie-chart working again and then researched how to display multiple charts on one page and came across a solution on http://stackoverflow.com/questions/18084781/google-charts-load-different-charts-on-one-page. I updated my test page 2 show pie-charts that were exactly the same (including dataSourceURL) and the first chart works, yet the second chart times-out.

I'm lost as to why 1 chart works but any more than that doesn't. Any thoughts?

Pete

unread,

Nov 11, 2013, 9:06:59 PM11/11/13

to google-analyti...@googlegroups.com

there was an update to the superProxy awhile ago to fix an issue related to this (https://github.com/googleanalytics/google-analytics-super-proxy/issues/3).

Is it possible you deployed a version of the superProxy prior to this update?

If you have the latest version deployed the then also try logging into AppEngine, and for the application you've deployed, goto Memcache Viewer and flush the cache, then refresh the page.

Peter Hinton

unread,

Nov 13, 2013, 4:53:25 AM11/13/13

to google-analyti...@googlegroups.com

Many thanks Pete, the version of superProxy was up-to-date but flushing the cache seemed to work. I'm still having an issue though:

To illustrate this I've created several tests

- A page with 3 charts (piechart, linechart & table) http://www.peterhintondesign.co.uk/superproxy-all.html

- A page with just the piechart http://www.peterhintondesign.co.uk/superproxy01.html

- A page with just the linechart http://www.peterhintondesign.co.uk/superproxy02.html

- A page with just the table http://www.peterhintondesign.co.uk/superproxy03.html

All 4 pages work fine if the cache has been flushed. However if the 'all' page is refreshed a couple of times then the following error occurs (regardless of what browser I test in).

The piechart says "Not enough columns given to draw the requested chart", the linechart displays the information that the table should display, and the table displays the information the piechart should display. It seems like the data-source has changed for all charts.

I thought this would be a JS error reading the data-source, but if you then now visit the superproxy01, superproxy02 and superproxy03 pages a couple of them come up with a "Request timed out" error.

The only way to fix this issue is to flush the cache. However if I have to flush the cache every time a user views the chart it causes a major problem.

Any thoughts?

Pete

unread,

Nov 14, 2013, 6:27:56 PM11/14/13

to google-analyti...@googlegroups.com

So the solution is not to flush the cache, this was just simply to troubleshoot the problem. There is another post that describes a similar problem and I wanted to confirm what I think the issue is. There is a bug due to caching and the ReqId param that will cause the behavior you're seeing. This needs to be fixed.

I've opened an issue: https://github.com/googleanalytics/google-analytics-super-proxy/issues/17

If you're following the project then you should get an update when there is a commit that fixes this issue.

In the meantime, if you have a few charts on the page, they should work. Each visitor won't know that they might be in a different order

pete

Peter Hinton

unread,

Nov 15, 2013, 8:50:38 AM11/15/13

to google-analyti...@googlegroups.com

Thanks Pete, I'm watching the page and I look forward to a fix. It seems to be working 90% of the time.

Eric Schrepel

unread,

Dec 5, 2013, 3:02:31 PM12/5/13

to google-analyti...@googlegroups.com

We get "Request timed out" errors for charts based on Google Spreadsheets, which happen only if a user hasn't logged into some Google account. If they haven't logged in, then only Chrome and IE (Firefox is fine) throw Request Timed Out errors (visible by doing Ctrl-Shift-J, watching the Network tab, and seeing all the unresolved ServiceLogin calls at the end).

The spreadsheet is publicly shared/visible, and once a user logs into a Google account (even in another tab, and even after then logging back out again), our timeout errors disappear.

Firefox seems immune, oddly.

Wilfrid Li

unread,

Jun 30, 2014, 9:43:46 PM6/30/14

to google-analyti...@googlegroups.com

I know this is a late reply, but I've just encountered this issue recently and have a proper fix to share.

The Request Time Out error was caused by the Google Charts API sending out a specific reqId to Super Proxy, and Super Proxy have cached the previous ReqId and returned the old ReqId instead.
This caused Google Charts API to 'Timeout'.
I've fixed this in my own version of Super Proxy and I've commented on the issue in the original bug tracker link. https://github.com/googleanalytics/google-analytics-super-proxy/issues/17

srirung...@gmail.com

unread,

Mar 28, 2019, 7:31:43 AM3/28/19

to Google Analytics superProxy

เมื่อ วันเสาร์ที่ 2 พฤศจิกายน ค.ศ. 2013 23 นาฬิกา 17 นาที 43 วินาที UTC+7, Peter Hinton เขียนว่า:

ศรีรุ่ง เพียดจันทร์

unread,

Mar 30, 2019, 6:21:43 AM3/30/19

to Google Analytics superProxy

เมื่อ วันพฤหัสบดีที่ 28 มีนาคม ค.ศ. 2019 18 นาฬิกา 31 นาที 43 วินาที UTC+7, ศรีรุ่ง เพียดจันทร์ เขียนว่า:

Reply all

Reply to author

Forward