Worldmap - access blocked, error r403

General
,
1

I've just installed Node.js v20 + latest stable NodeRed v4.1.8 successfully on Windows 7 32bit OS.
I'm getting this 403r error on the map:

kép
kép544×660 76.8 KB

2

What about other base maps ?

3

Just a side-note that this is playing with fire. A dangerous OS to have connected to the Internet in the 2020's.

4

You are right, all the other maps I've checked working well,
only OSM is problematic.
But sadly OSM is what users will use mostly.

kép
kép287×264 26.5 KB

5

Good. I’ll have a look next week.

6

OFF

This is not the right topic for that, but as I've stated many many times in all forums already:

Fact is:

  • >60 % of my users are still using Win7 daily 16+ hours 360/365, without any problems! (100+ POS configured PCs in restaurants.)
  • While we have problems with Win10 64bit PCs every week !
    (Even work-breaking, shop force-closing kind of big problems.)

IMHO an OS's security level is mostly dependent: how it's configured,
(All unnecessary services disabled, proper Firewall settings, no Admin rights to users, etc.)

"Newer" does not necessarily means "better".

7

You can of course hide it from the options to set another default for your users. Hopefully this is also reproducible for me and there is a fix we can apply to get them back online.

8

I'm trying to find out myself, but I'm not a web-developer.
If I press F12 in Firefox, there are many warning listed, but no blocking errors.

It's probably not related but found a tiny bug at the function of 541. line:
(heatmap is turned off)

// Remove old markers
function doTidyUp(l) {
    if (l === "heatmap") {
        heat.setLatLngs([]); // << HERE is the problem!

(TypeError: heat is undefined
    doTidyUp worldmap.js:544

List of Warnings:

Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/sockjs.min.js
Forrástérkép webcíme: sockjs.min.js.map

A MouseEvent.mozPressure absolute. Használja helyette a PointerEvent.pressure tulajdonságot. Util.js:27:2

Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/VectorTileLayer.umd.min.js
Forrástérkép webcíme: VectorTileLayer.umd.min.js.map

Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/leaflet-rotate.js
Forrástérkép webcíme: leaflet-rotate.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/togeojson.umd.js
Forrástérkép webcíme: togeojson.umd.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/leaflet.antimeridian-src.js
Forrástérkép webcíme: leaflet.antimeridian-src.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/sockjs.min.js
Forrástérkép webcíme: sockjs.min.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/pmtiles.js
Forrástérkép webcíme: pmtiles.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/sockjs.min.js
Forrástérkép webcíme: sockjs.min.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/esri-leaflet.js
Forrástérkép webcíme: esri-leaflet.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/sockjs.min.js
Forrástérkép webcíme: sockjs.min.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/VectorTileLayer.umd.min.js
Forrástérkép webcíme: VectorTileLayer.umd.min.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/leaflet.antimeridian-src.js
Forrástérkép webcíme: leaflet.antimeridian-src.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/leaflet-rotate.js
Forrástérkép webcíme: leaflet-rotate.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/sockjs.min.js
Forrástérkép webcíme: sockjs.min.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/pmtiles.js
Forrástérkép webcíme: pmtiles.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/togeojson.umd.js
Forrástérkép webcíme: togeojson.umd.js.map
Source map error: Error: request failed with status 404
Resource URL: http://localhost:1880/wm/leaflet/esri-leaflet.js
Forrástérkép webcíme: esri-leaflet.js.map

Source map error links: Source map errors — Firefox Source Docs documentation

9

It's unlikely you find that error in the browser console.

The server side is simply blocking HTTP requests that miss the Referer header. Which is not uncommon, so these images can't be directly be linked from external sites (which causes extra traffic, can be misused, etc...).

For "normal" website browsing, the referer is set by the browser, e.g. when you click a link, the referer is set to the originating site.

So it depends on how OSM loads these tiles, I guess via some JS. So that's where I'd start looking to set that header.

Some hints are documented on their wiki:

10

The error you showed in your first post includes a link to the section of the wiki describing the problem and what needs to be done to sort it.

11

From the wiki:

If the tile mentions "Referer is required" then you were automatically blocked because your application/website is not sending HTTP Referer headers, but doing so is required by the tile usage policy. This block will resolve itself once you make the necessary changes to your application, without further intervention necessary.

For websites/web applications, this can be fixed by setting your Referrer-Policy header to any of no-referrer-when-downgrade, origin, origin-when-cross-origin, strict-origin, or strict-origin-when-cross-origin.

For more information, see the Referer article.

I think you should be able to set the Referrer-Policy header in Node-RED's settings.js file. Or, if you are using a reverse proxy to protect outbound traffic, set it in the proxy.

12

Thank you very much for this link !
It has led me to a leaflet Github issue about this problem, including ^ this (link) post.

That gave me an idea, that maybe there is a browser plugin, that may interfere...

SOLVED.

13

[SOLVED]

I just had to fine-adjust uBlock origin plugin in my Firefox browser (v115.34.1esr 32bit), and the problem is gone!

  • Simply allow "1st-party scripts" !
  • or unblock that site you are using with WorldMap (big blue On/Off icon)

kép
kép1220×570 94.1 KB

It is possible, that the root of this problem was, that I'm using the map via localhost http. (no https)
http://localhost:1880/wm/

14

Good find. Well done !
I always forget to ask users about plugins they may installed :slight_smile:

15

Which is why I have a browser profile with no addins. :smiley:

In fact I keep dev and other browsing in separate profiles as well and something separate for risky social media so that I can keep proper separation between different purposes. This really helps keep things like cookies in separate containers.

16

Did you succeed to fix the:

heat.setLatLngs([])

^ problem when heatmap is turned off?
(Also the corresponding caller routines, if they get a null as return?)