Using overpass turbp, I often - but quite irregularly - receive this error message:

alt text

It says that the request is rejected due to "e.g. server not found, request blocked by browser addon, request redirected, internal server errors, etc." I checked browser settings, the query itself, ran it on different devices, checked the status of Overpass etc. Sometimes, it affects even the smallest queries, e.g. the default one when loading overpass turbo.

Here, some more information, there seems to be issues with both XML and Java. The messages are from the browser's debugging tool (F12):

alt text

Has someone experienced the same problem (No 'Access-Control-Allow-Origin' header present, Cannot read property 'getBaseLayer')? How did you solve it? It seems always to be related to turbo.4decdd916893e57ee8ff.js. Thanks for all hints!

Below, all details of the debugging messages in text format:

Access to XMLHttpRequest at '' from origin '' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
turbo.4decdd916893e57ee8ff.js:66 Uncaught TypeError: Cannot read property 'getBaseLayer' of undefined
    at Object.j.a.handlers.onDone (turbo.4decdd916893e57ee8ff.js:66)
    at e (turbo.4decdd916893e57ee8ff.js:40)
    at Object.error (turbo.4decdd916893e57ee8ff.js:40)
    at u (turbo.4decdd916893e57ee8ff.js:24)
    at Object.fireWith [as rejectWith] (turbo.4decdd916893e57ee8ff.js:24)
    at i (turbo.4decdd916893e57ee8ff.js:24)
    at XMLHttpRequest.<anonymous> (turbo.4decdd916893e57ee8ff.js:24)
j.a.handlers.onDone @ turbo.4decdd916893e57ee8ff.js:66
e @ turbo.4decdd916893e57ee8ff.js:40
error @ turbo.4decdd916893e57ee8ff.js:40
u @ turbo.4decdd916893e57ee8ff.js:24
fireWith @ turbo.4decdd916893e57ee8ff.js:24
i @ turbo.4decdd916893e57ee8ff.js:24
(anonymous) @ turbo.4decdd916893e57ee8ff.js:24
error (async)
send @ turbo.4decdd916893e57ee8ff.js:24
ajax @ turbo.4decdd916893e57ee8ff.js:24
run_query @ turbo.4decdd916893e57ee8ff.js:40
(anonymous) @ turbo.4decdd916893e57ee8ff.js:66
(anonymous) @ turbo.4decdd916893e57ee8ff.js:66
e.parse @ turbo.4decdd916893e57ee8ff.js:58
(anonymous) @ turbo.4decdd916893e57ee8ff.js:58
(anonymous) @ turbo.4decdd916893e57ee8ff.js:82
(anonymous) @ turbo.4decdd916893e57ee8ff.js:66
success @ turbo.4decdd916893e57ee8ff.js:66
u @ turbo.4decdd916893e57ee8ff.js:24
fireWith @ turbo.4decdd916893e57ee8ff.js:24
i @ turbo.4decdd916893e57ee8ff.js:24
(anonymous) @ turbo.4decdd916893e57ee8ff.js:24
load (async)
send @ turbo.4decdd916893e57ee8ff.js:24
ajax @ turbo.4decdd916893e57ee8ff.js:24
t @ turbo.4decdd916893e57ee8ff.js:66
e.get @ turbo.4decdd916893e57ee8ff.js:66
e.getBest @ turbo.4decdd916893e57ee8ff.js:66
s @ turbo.4decdd916893e57ee8ff.js:82
e.parse @ turbo.4decdd916893e57ee8ff.js:58
getQuery @ turbo.4decdd916893e57ee8ff.js:66
update_map @ turbo.4decdd916893e57ee8ff.js:66
onRunClick @ turbo.4decdd916893e57ee8ff.js:66
dispatch @ turbo.4decdd916893e57ee8ff.js:24
_.handle @ turbo.4decdd916893e57ee8ff.js:24
turbo.4decdd916893e57ee8ff.js:24 POST net::ERR_FAILED

asked 13 Sep, 16:52

G%C3%A5seborg's gravatar image

accept rate: 0%

edited 14 Sep, 13:51

The request is made on which seems to contact for executing the query. As both servers belong to a different domain, the CORS policy has to allow this. This means that the server on has to allow requests from servers from another domain. Such a CORS policy is typically in place to avoid front-ends with bad intentions from using a back-end server.

In case this does not work, it is a server configuration error. There is nothing you can do as a user of the system. Of course, you can contact the maintainers of that server to inform them about the problem.

permanent link

answered 16 Sep, 14:03

escada's gravatar image

accept rate: 20%

Thanks for your answer @escada! I am wondering whether and how one can specify the server which overpass turbo is contacting. I tried {{data:overpass,server=}} with each of the following:,, which I found on, but the query always ends up with Funny thing is that the same query on another laptop gets processed by another server and there it works.

(17 Sep, 07:39) Gåseborg

Also added the question on the issue reporting page of the French OSM team:

(17 Sep, 07:46) Gåseborg
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 13 Sep, 16:52

question was seen: 132 times

last updated: 17 Sep, 07:46

powered by OSQA