Connection problem with palette in Docker node-red container

[yogy]

Setup a clean raspberry4
Installed docker
Created a node-red container with docker compose
Node-red runs fine in the container
Trying to use palette to install some nodes.
Get the following error after clicking manage palette

Failed to load node catalogue.
Check the browser console for more information

In the console i see the following

Error loading catalog https://catalogue.nodered.org/catalogue.json : 
(anonymous) @ red.min.js?v=:18
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
DevTools failed to load source map: Could not load content for http://192.168.1.200:1880/vendor/purify.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

When I go into the node-red container and do a ping to the catalogue adress and can reach the adress
I can reach the internet with the http request node in node red.

Question
Is there somewhere a (docker) parameter that I should use?
It is a clean container, nothing changed.

My Install:

Raspberry 4
linux aarch64 Debian GNU/Linux 11 (bullseye)
Kernel Version	6.1.21-v8+

Node-red 3.1.0: Milestone Release

Docker compose file

version: "3.7"
services:
  node-red:
    image: nodered/node-red:latest
    environment:
      - TZ=Europe/Amsterdam
    ports:
      - "1880:1880"
    networks:
      - node-red-net
    volumes:
      - /home/pi/dockerdata/nodered:/data
volumes:
  node-red-data:
networks:
  node-red-net:

[marcus-j-davies]

@yogy

ERR_BLOCKED_BY_CLIENT

Hi @yogy

This is not a problem with Docker or Node RED.

The editor (loaded by whatever browser you are using) is blocking connections to fetch the current catalogue of Nodes.

These requests are made using AJAX - and all I can assume is that your browser is blocking it.

• Browser Privacy plugins (being a little too strict)
• some other plugin that blocks AJAX calls

i.e this is a web browser/browser plugin issue - try disabling some plugins on the browser that may be suspect

Below is my browser fetching the catalogue (and succeeding)

EDIT
You can ignore the source map request

[yogy]

Thanks for replying!
Indeed that was the solution.
As you can see I have little understanding of the interactions from node-red with the browser.
Never thought of that.
Thanks again