23.03.2026, 17:29
Ich bekomme in RouteConverter eine Access Blocked 403 http Fehler. Kann ich da was ändern?
Ich habe OpenStreeMap (online) ausgewählt
Bei OpenStreetMap Default (online) erscheint diese Meldung nicht???
This message means OpenStreetMap has blocked the map tiles your app or website is trying to load.
From the image, the exact text is:
OpenStreetMap (OSM) allows free use of its map data, but its public tile servers have strict rules to protect their limited, donation‑funded infrastructure.
Your map request was blocked because the request did not include a required HTTP “Referer” header. OSM uses this header to know which website or application is requesting tiles. If it’s missing, they automatically block access. [wiki.opens...eetmap.org], [operations...dation.org]
Common reasons this happens
You didn’t do anything wrong.
What you can do:
OSM requires:
Why OSM does this
Even though OSM data is open, serving rendered map images costs money. The policy prevents scraping, abuse, and heavy anonymous use that would overload volunteer‑run servers. [operations...dation.org]
If you want, tell me which software or website shows this message (browser map, GIS tool, internal app, etc.), and I can explain exactly what needs to be changed or worked around in that context.
Ich habe OpenStreeMap (online) ausgewählt
Bei OpenStreetMap Default (online) erscheint diese Meldung nicht???
This message means OpenStreetMap has blocked the map tiles your app or website is trying to load.
From the image, the exact text is:
Quote:403r – Access blockedWhat that means in plain terms
Referer is required by tile usage policy of OpenStreetMap's volunteer‑run servers
osm.wiki/Blocked
OpenStreetMap (OSM) allows free use of its map data, but its public tile servers have strict rules to protect their limited, donation‑funded infrastructure.
Your map request was blocked because the request did not include a required HTTP “Referer” header. OSM uses this header to know which website or application is requesting tiles. If it’s missing, they automatically block access. [wiki.opens...eetmap.org], [operations...dation.org]
Common reasons this happens
- The application or website you are using does not send a Referer header at all
- A privacy setting or browser extension strips the Referer header
- The app uses a restrictive Referrer‑Policy like
Code:no-referrer - The software has not yet been updated to comply with OSM’s newer tile policy [wiki.opens...eetmap.org], [github.com]
You didn’t do anything wrong.
What you can do:
- Try updating the application (many tools broke when OSM tightened the policy)
- Disable privacy extensions temporarily and test again
- Use a different map background (many apps offer alternative providers)
- Inform the app’s developer that OSM tiles require Referer + User‑Agent headers [wiki.opens...eetmap.org]
OSM requires:
- A valid HTTP Referer header
- A clear User‑Agent
- Proper © OpenStreetMap contributors attribution
- No restrictive
(allowed examples includeCode:Referrer-Policy
) [operations...dation.org]Code:strict-origin-when-cross-origin
Why OSM does this
Even though OSM data is open, serving rendered map images costs money. The policy prevents scraping, abuse, and heavy anonymous use that would overload volunteer‑run servers. [operations...dation.org]
If you want, tell me which software or website shows this message (browser map, GIS tool, internal app, etc.), and I can explain exactly what needs to be changed or worked around in that context.
Grüße,
Ilmari
