Google earth enterprise An error occurred while accessing flat file q2-0-q.1.


We have a google earth enterprise server 5.1 running in our local network with at

In the sandbox when we run cesium locally at localhost:8080 on the server itself the globe is visible in cesium.

We use the following code :

var geeMetadata = new Cesium.GoogleEarthEnterpriseMetadata({

url : ‘’,

proxy : new Cesium.DefaultProxy(’/proxy/’)


var viewer = new Cesium.Viewer(‘cesiumContainer’, {

baseLayerPicker: false,

imageryProvider : new Cesium.GoogleEarthEnterpriseImageryProvider({

metadata : geeMetadata



When re want to run on remote machine we use the same code but get an error :

An error occurred in “GoogleEarthEnterpriseImageryProvider”: An error occurred while accessing

Also in sandcastle - Failed to load resource: the server responded with a status of 503 (Service Unavailable) - http://localhost:8080/proxy/?http%3A%2F%2F192.168.1.5%2F3ds%2Fflatfile%3Fq2-0-q.1

We can access online in sandcastle.

Typing and running request directly in web browser downloads the flat file .

We are stuck and please provide a solution.

Thanks for the help

+1, I get the same error

Hi there,

How are you hosting Cesium? Are you using the development server? Are you running it with the --public option then trying to access it from another machine? In any case, if you control the Google Earth server, you should definitely enable CORS on it and remove the proxy form your own code – this will make things faster and possibly fix the issue.

Hope that helps,

  • Rachel


This happened to me as well, where my WMS providers were all working fine, but GEE was having trouble with the flatfiles when using a proxy.

The culprit in my case was that a library I used to build my proxy was automatically appending a "Content-Encoding: gzip" header to ALL content. After fixing this, your flatfiles should load just fine. Alternatively, assuming it's an option, just don't use a proxy and instead modify the Access-Control-Allow-Origin property on the GEE server, as Rachel suggests.

Steps to debug: check out the network tab in Chrome and compare the response headers you get through your proxy vs. the ones you get normally.

Hope that helps.