[MapProxy] Mapproxy 6 - Openseamap not loading

getafix4kix getafix4kix at gmail.com
Wed Feb 4 02:11:01 PST 2026


Hi,

We have upgraded to a new release for Mapproxy and for some weird reason
the tiles for openstreetmap are loading, but not the tiles for openseamap.

In the mapproxy log-file this is shown , where the openseamap GET does not
have a 200-response.

[2026-02-04 10:50:08,789] mapproxy.source.request - INFO - GET
https://c.tile.openstreetmap.org/4/6/6.png 200 1.2 56

[2026-02-04 10:50:08,800] mapproxy.source.request - INFO - GET
https://c.tile.openstreetmap.org/4/7/6.png 200 12.3 40

[2026-02-04 10:50:08,805] mapproxy.source.request - INFO - GET
https://t1.openseamap.org/seamark/4/6/6.png - - 72

[2026-02-04 10:50:08,837] mapproxy.source.request - INFO - GET
https://t1.openseamap.org/seamark/4/7/6.png - - 77

[2026-02-04 10:50:08,843] mapproxy.source.request - INFO - GET
https://c.tile.openstreetmap.org/4/8/6.png 200 16.0 34

[2026-02-04 10:50:08,880] mapproxy.source.request - INFO - GET
https://c.tile.openstreetmap.org/4/9/6.png 200 21.7 39

[2026-02-04 10:50:08,881] mapproxy.source.request - INFO - GET
https://t1.openseamap.org/seamark/4/8/6.png - - 72

[2026-02-04 10:50:08,917] mapproxy.source.request - INFO - GET
https://t1.openseamap.org/seamark/4/9/6.png - - 76

[2026-02-04 10:50:08,922] mapproxy.source.request - INFO - GET
https://c.tile.openstreetmap.org/4/10/6.png 200 19.7 37

[2026-02-04 10:50:08,956] mapproxy.source.request - INFO - GET
https://t1.openseamap.org/seamark/4/10/6.png - - 71

[2026-02-04 10:50:08,961] mapproxy.source.request - INFO - GET
https://c.tile.openstreetmap.org/4/5/7.png 200 9.5 41

[2026-02-04 10:50:08,991] mapproxy.source.request - INFO - GET
https://t1.openseamap.org/seamark/4/5/7.png - - 71

[2026-02-04 10:50:08,992] mapproxy.source.request - INFO - GET
https://c.tile.openstreetmap.org/4/6/7.png 200 1.0 33

[2026-02-04 10:50:09,036] mapproxy.source.request - INFO - GET
https://c.tile.openstreetmap.org/4/7/7.png 200 16.0 41

[2026-02-04 10:50:09,052] mapproxy.source.request - INFO - GET
https://t1.openseamap.org/seamark/4/6/7.png - - 92

[2026-02-04 10:50:09,080] mapproxy.source.request - INFO - GET
https://t1.openseamap.org/seamark/4/7/7.png - - 85

[2026-02-04 10:50:09,103] mapproxy.source.request - INFO - GET
https://c.tile.openstreetmap.org/4/8/7.png 200 20.1 48

[2026-02-04 10:50:09,132] mapproxy.source.request - INFO - GET
https://c.tile.openstreetmap.org/4/9/7.png 200 19.4 48

[2026-02-04 10:50:09,134] mapproxy.source.request - INFO - GET
https://t1.openseamap.org/seamark/4/8/7.png - - 79

[2026-02-04 10:50:09,171] mapproxy.source.request - INFO - GET
https://t1.openseamap.org/seamark/4/9/7.png - - 87

Anybody seen this type of behaviour before ?

When linking directly to a tile he server shows it in the browser, example
https://t1.openseamap.org/seamark/11/1056/670.png

Any lead into fixing this is appreciated.

Vincent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy/attachments/20260204/6ad6e2be/attachment.htm>


More information about the MapProxy mailing list