[BUG] Version 1.74.1 blank screen when accessing n8n using hostname but works with localhost

Questions
1

Since version 1.74.1+, we get a blank screen while accessing the URL using the hostname, it only works on the local machine using localhost:5678

its working fine after downgrading to 1.73.1

Information on your n8n setup

  • n8n version: 1.74.1
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system: Windows
2 Likes
2

+1, just installed the latest from template via portainer and had to downgrade.

3

Do you see any errors in the browser console?

4

Thank you, I have also reverted to version 1.73.1. There is a problem with the current version.

5

I think the problem is this:

Blockquote
The Cross-Origin-Opener-Policy header has been ignored, because the URL’s origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the ‘localhost’ origin instead. See Secure Contexts and HTML Standard.

6

I hope this issue gets resolved; all my work has been delayed because of it

7

Sorry, I have not been able to find how to downgrade to a desired version, when there are problems with an update in the self-hosted versions, specifically in the version that contains the package: self-hosted-ai-starter-kit. Can someone tell me where to find the solution. ?

Sorry if this is not the right place, but I did not want to open a new post.

Thanks

8

From now on, don’t update n8n automatically, or tasks like mine will be disrupted. Below is the Docker Compose code, it will work automatically with Portainer

version: '3.8'

services:
  n8n:
    image: docker.n8n.io/n8nio/n8n:1.73.1
    container_name: n8n
    ports:
      - "5678:5678"
    environment:
      - N8N_SECURE_COOKIE=FALSE
    volumes:
      - n8n:/home/node/.n8n
    restart: always

volumes:
  n8n:
    external: true
9

on official page, they show 1.74.1 as next but prompt us to update it, i mean if it’s not a stable version, why adding it to the latest tag in docker??

image
image1352×318 30.7 KB

10

Issue is fixed on version 1.74.3

11

When I install it with the latest tag, it doesn’t work, but it works when I install it with the 1.74.3 tag. There must be an issue with the latest tag

12

Your system likely has an older version of the latest tag.
You could try running docker pull docker.n8n.io/n8nio/n8n:latest to make sure that the local tag is up-to-date.

1 Like
13

After you mentioned it, I tried the latest tag again, and it worked. Thank you!

1 Like
14

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