[Maps] Map layer "Thunderforest OpenCycleMap" stopped working (and problems with other layers)

[dcjkfgdjhd]

Describe the bug

When I select this layer, nothing happens, I only see the GC.com default map.

To Reproduce

See above.

Expected behavior

No response

OS

Windows

Browser

Firefox

GClh Version

0.15.8

Additional context

OpenCycleMap, tile-hosted by Thunderforest, is included as an official map layer on openstreetmap.org and works without issues.

[2Abendsegler]

I cannot reproduce the problem. At the moment the layer works for me. Maybe the layer was unavailable for a short time.

Can you please check this?

[dcjkfgdjhd]

Absolutely reproducible for me, on two computers, for months now.

[2Abendsegler]

Maybe you could try some things:

1. Can you select other layers?
2. Can you please turn off all other scripts and add-ons and then test again?
3. Can you please call the console (function key F12 and then select console)? If there are messages, please take a screenshot.

[dcjkfgdjhd]

1. Yes, but not the Thunderforest Layers:

Working:

• CyclOSM: OSM-based bicycle map
• Google Maps
• Google Maps Hybrid
• Google Maps Satellite
• OpenStreetMap Default
• OpenTopoMap
• ÖPNVMap

Not working:

• Thunderforest Landscape
• Thunderforest OpenCycleMap
• Thunderforest Transport

2. No change.

3. Yes, there are messages. The link leads here: https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content

[2Abendsegler]

Could it be that you have “HTTPS-only mode” enabled? You can find this in the settings in your browser. If so, please deactivate it and test again.

In Firefox it looks something like this in German:

[2Abendsegler]

Are you working with Chrome? I can now reproduce the problem on Chrome. But so far I haven't been able to determine what the reason is. It could be that it has something to do with the http calls.

[dcjkfgdjhd]

"HTTPS only" is not enabled.

No, I use Firefox.

[2Abendsegler]

First results: We access all layers via http. The browser then goes and upgrades to https, if it exists. All layers have an https counterpart, except the “Thunderforest” layers. Actually, it seems correct that such addresses are no longer loaded. The question is why they are still loading in my Firefox.

[2Abendsegler]

... we probably need an API key for the https calls.

[capoaira]

I can reproduce this Issue and can the three Stamen-Maps to the not working layers. With the same "mixed content" errors, (https-only is disabled)

Using Firefox in Linux Mint

It looks like the browser updates the url to https, witch is not supported by the servers.

btw: Also "CyclOSM: OSM-based bicycle map" does not for me, the request just gets no response.

[capoaira]

I change Firefox internal settings to stop Firefox updating to https:

1. Type about:config in the address bar and press Enter.

2. Click "Accept the Risk and Continue" if prompted.

3. In the search bar at the top, type mixed_content.

4. Locate security.mixed_content.upgrade_display_content.image and double-click it to set it to false.

With that, the thunderforest maps work again, but the stamen still not. But the stamen also not work, when I type it in the address bar, so they are maybe not available anymore. (Same as "Esri NatGeoWorldMap")

[dcjkfgdjhd]

CyclOSM works for me, but often unreliably (some tiles not getting delivered).

[2Abendsegler]

• [x] We should be able to solve the problem with the Thunderforest layers with an API key. With an API key we can work with https. I'll take care of that.
• [ ] Stamen seems to have entered into a cooperation with Stadiamaps. https://maps.stamen.com/stadia-partnership 200,000 views per month seem free. I don't know how far we'll get with this. I couldn't find any information on how to access the tiles. https://stadiamaps.com/pricing
• [ ] CyclOSM probably fails due to opaque response blocking. I couldn't quickly understand what this was all about and what we need to do to fix the problem. [Edit] There is an actual issue.
• [ ] Esri NatGeoWorldMap only works at Zoom Level 12 and below. [Edit] Set "maxZoom: 12" in "all_map_layers".

[2Abendsegler]

With the next version, the Thunderforest map layers will work again. We now have an API key for this.

[2Abendsegler]

I won't be working on the problems with the Stamen and CyclOSM map layer at the moment due to lack of time.

We'll leave the issue open for now for these both problems. Maybe someone will be found who has the time and desire to work on it.

As with the "Tracestack Topo" in Issue #2602, it would probably be useful to set up an API key for each user for the Stamen map layer. But the effort involved seems too great to me at the moment. There would also probably be a lot of requests from users to set up the API key. This effort also seems too great to me at the moment.