OpenStreetMap often sends Gateway Timeout error

Question

I am using a leaflet map in program with the following code:

<style>
     <link rel="stylesheet" href="https://unpkg.com/leaflet@1.3.1/dist/leaflet.css" integrity="sha512-Rksm5RenBEKSKFjgI3a41vrjkw4EVPlJ3+OiI65vTjIdo9brlAacEuKOiQ5OFh7cOI1bkDwLqdLw3Zg0cRJAAQ==" crossorigin=""/>
    @import url(//cdnjs.cloudflare.com/ajax/libs/leaflet/0.7.2/leaflet.css);
    #map {
        width: 960px;
        height: 500px;
    }
</style>

<body>
   <div id="map"/>
   <script type="text/javascript">
        var osmUrl = 'http://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png',
            osmAttrib = '&copy; <a href="http://openstreetmap.org/copyright">OpenStreetMap</a> contributors',
            osm = L.tileLayer(osmUrl, {maxZoom: 20, attribution: osmAttrib});

        var map = L.map('map').setView([37.5, -115], 6).addLayer(osm);

</body>

However, I keep seeing some grey square on my maps at random positions and I get the following Leaflet error code in the javascript console:

http://a.tile.openstreetmap.org/6/8/25.png 504 (Gateway Timeout)

Would anyone know what's wrong and how to solve it?

IvanSanchez · Accepted Answer

A 50x error from the OpenStreetMap tile servers is a problem caused on the OSM side of things, not a problem caused by your use (or misuse) of OSM tiles in your website or application.

Judging by the specific time and date of your question, I'll make a wild assumption and say that you were hitting one of the squid proxy servers ~~during a momentary overload of the network~~ while a system-wide upgrade from squid 2 to squid 3 has been going on for the past few days (note the screenshot below is for the git repo holding the chef devops recipes for the OSM servers, and also the fact that I can see the status of the OSM servers is awesome).

Screenshot from OSMF's repo for Chef recipes

Please keep in mind that the OSM tile servers and proxy servers are maintained by a team of (awesome) volunteer system administrators and, while they do their best to keep everything up and running, the OSM Foundation can not make any guarantees about the quality of service.

Read more about this at https://operations.osmfoundation.org/ and specifically at https://operations.osmfoundation.org/policies/tiles/

Would anyone know what's wrong and how to solve it?

In general, temporarily failures of the OSMF services can be solved by:

Having patience and waiting for the sysadmins to fix things.
Lurking at the OFTC #OSM-dev IRC channel (more info here) to know specifically what's wrong and politely asking. If you do so, do not be a nuisance to the people there; it will only slow things down.
Donating money to the OSMF so it can increase its operational capabilities.
Volunteering to be a part of the OSMF Operations Working Group, or contributing with hardware for mirror servers or the like.

If you do not want to be bound by the limitations of the OSMF, there are a couple common alternatives:

Use a commercial tile provider (some of the providers are listed here)
Host your own tiles (more information here)
Cache the tiles. Unlike most commercial vendors, OSM allows you to store, proxy, and cache the tiles in pretty much whatever way you want. In fact, anything that will lessen the load on the OSMF servers is encouraged, as long as you take a modicum of care (i.e. do not seed your cache, which would trigger bulk downloads).

OpenStreetMap often sends Gateway Timeout error

Tags:

javascript

leaflet

openstreetmap

LBes

1 Answers

IvanSanchez

Recent Activity

Donate For Us

OpenStreetMap often sends Gateway Timeout error

Tags:

javascript

leaflet

openstreetmap

LBes

1 Answers

IvanSanchez

Related questions

Recent Activity

Donate For Us