New CORS related issue

Questions
1

I’ve been running n8n on my Synology NAS via Cloudflare for a year or two and never had this problem. Same n8n docker config and same Cloudflare config. I’ve included my docker compose below in case that needs some tweaking.
I’ve just come back to n8n after several months away from it and now I’m getting some weird CORS issue and have no idea what’s going on.

Can someone please help with this and/or offer some suggested fixes?
Thanks heaps in advance

Errors I’m seeing in console log are -

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015. (Reason: CORS request did not succeed). Status code: (null).

None of the “sha512” hashes in the integrity attribute match the content of the subresource at “https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015”. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”. workflows
Loading module from “https://n8n.mjcsyn.com/assets/polyfills-JGObYAeq.js” was blocked because of a disallowed MIME type (“text/html”).
workflows
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015. (Reason: CORS request did not succeed). Status code: (null).

None of the “sha512” hashes in the integrity attribute match the content of the subresource at “https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015”. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”. workflows
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015. (Reason: CORS request did not succeed). Status code: (null).

None of the “sha512” hashes in the integrity attribute match the content of the subresource at “https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015”. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”. self-install
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015. (Reason: CORS request did not succeed). Status code: (null).

None of the “sha512” hashes in the integrity attribute match the content of the subresource at “https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015”. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”. self-install
Cookie “dmn_chk_019a6128-89dd-76cd-b440-43682e39f0a0” has been rejected for invalid domain.
  • n8n version: 1.118.2
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Linux

Docker compose -

version: "3.9"

networks:
  cftunnels_default:
    external: true

services:
  db:
    image: postgres:16.4
    container_name: n8n-DB
    hostname: n8n-db
    networks:
      - cftunnels_default
    security_opt:
      - no-new-privileges:true
    user: 1026:100
    healthcheck:
      test: ["CMD", "pg_isready", "-q", "-d", "n8n", "-U", "n8nuser"]
      timeout: 45s
      interval: 10s
      retries: 10
    volumes:
      - /volume1/docker/n8n/db:/var/lib/postgresql/data:rw
    environment:
      PUID: 1026
      PGID: 100
      TZ: Asia/Bangkok
      POSTGRES_DB: n8n
      POSTGRES_USER: n8nuser
      POSTGRES_PASSWORD: <password>
    restart: on-failure:5

  n8n:
    image: docker.n8n.io/n8nio/n8n
    container_name: n8n
    hostname: n8n
    networks:
      - cftunnels_default
    security_opt:
      - no-new-privileges:true
    ports:
      - 5678:5678
    volumes:
      - /volume1/docker/n8n/data:/home/node/.n8n:rw
      - /volume1/docker/n8n/files:/files:rw
    environment:
      PUID: 1026
      PGID: 100
      N8N_HOST: n8n.<DOMAIN>.com
      N8N_PORT: 5678
      N8N_PROTOCOL: https
      NODE_ENV: production
      N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS: true
      N8N_RUNNERS_ENABLED: true

      EXECUTIONS_DATA_PRUNE: TRUE
      EXECUTIONS_DATA_MAX_AGE: 96
      EXECUTIONS_DATA_PRUNE_MAX_COUNT: 50000

      WEBHOOK_URL: https://n8n.<DOMAIN>.com
      GENERIC_TIMEZONE: Asia/Bangkok
      TZ: Asia/Bangkok
      DB_TYPE: postgresdb
      DB_POSTGRESDB_DATABASE: n8n
      DB_POSTGRESDB_HOST: n8n-db
      DB_POSTGRESDB_PORT: 5432
      DB_POSTGRESDB_USER: n8nuser
      DB_POSTGRESDB_PASSWORD: <password>
    restart: on-failure:5
2

ok turns out it was a community node causing the problem.
all good again in the land of n8n

1 Like
3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.