|
I'm using the tileserver https://{s}.tiles.wmflabs.org/bw-mapnik/{z}/{x}/{y}.png in leaflet for a project. I'm getting the following error on some of the tiles:
It appears that the error only occurs on tiles loaded from the b subdomain. The error can be reproduced by replacing {s} in the link above with a, b, c and open the urls in a browser. The b url will raise the error, and the a and c urls will not. For now I bypassed the problem by using the url "https://tiles.wmflabs.org/bw-mapnik/{z}/{x}/{y}.png". |
|
You'll need to talk to the people in charge of that server (Wikimedia, not OpenStreetMap). A relevant help article is here. Wikimedia have tried to use a wildcard certificate, but it's not working for sub-sub-domains. OpenStreetMap does it correctly for local tiles - here's an example (click on the "lock" icon to get to the certificate details). OSM is just using a regular certificate for "tile.openstreetmap.org", which works fine. Other reasons why you might not want to use these tiles include that they are very old (from 2015). Also note that all of "a", "b" and "c" have the same problems for me - I suspect that you've accepted an exception for 2 of them. EDIT: Wikimedia have now removed these old tiles completely. Thank you for your answer. I think I switch back to the default osm tileserver and use css to make the tiles black and white.
(12 Mar '19, 07:55)
mvbaalen
1
Looks like Wikimedia have readded those tiles. I saw they were gone for a while, but now they are back.
(19 Mar '19, 14:42)
kwkelly
1
I still wouldn't use them. https://b.tiles.wmflabs.org/bw-mapnik/9/266/170.png/status says "Tile is clean. Last rendered at Fri Apr 10 09:00:52 2015". Newer tiles sources are available.
(19 Mar '19, 14:49)
SomeoneElse ♦
|
