I’m running OpenHamClock v26.5.0 on a Raspberry Pi.
Beginning around August 26–27, 2026, the Dark basemap started displaying repeated:
“API KEY REQUIRED — carto.com/basemaps/apikey”
across the map.
The rest of OpenHamClock appears to be working normally. Switching the basemap from Dark to Dark (Esri) removes the message, so this appears to be related specifically to the CARTO basemap tile service.
It looks like CARTO may now require an API key for requests to:
basemaps.cartocdn.com/dark_all/...
basemaps.cartocdn.com/rastertiles/voyager/...
The current OpenHamClock source appears to use those URLs for the Dark and Streets map styles.
System:
- OpenHamClock v26.5.0
- Raspberry Pi
- Problem observed August 27, 2026
- Dark (Esri) works normally as a workaround
I’m attaching a screenshot showing the watermark.
Is there a plan to replace the CARTO tile URLs or add support for a CARTO API key?
Thanks for all the work on OpenHamClock.

I’m running OpenHamClock v26.5.0 on a Raspberry Pi.
Beginning around August 26–27, 2026, the Dark basemap started displaying repeated:
“API KEY REQUIRED — carto.com/basemaps/apikey”
across the map.
The rest of OpenHamClock appears to be working normally. Switching the basemap from Dark to Dark (Esri) removes the message, so this appears to be related specifically to the CARTO basemap tile service.
It looks like CARTO may now require an API key for requests to:
basemaps.cartocdn.com/dark_all/...basemaps.cartocdn.com/rastertiles/voyager/...The current OpenHamClock source appears to use those URLs for the Dark and Streets map styles.
System:
I’m attaching a screenshot showing the watermark.
Is there a plan to replace the CARTO tile URLs or add support for a CARTO API key?
Thanks for all the work on OpenHamClock.