Got gray answer and loading animation

Questions
1

Hey,

After I run node, I got an answer, but text is gray and loading animation keep loading until I refresh the page.

image
image1543×762 26.2 KB

image

What am I doing wrong?

@EDIT

I tested it also with different API and see that it’s return nothing when it should return sth. So I am not sure if it’s not just getting data for so long time, Is it possible that loading data can take like 5 minutes or more?

2

Hey @Shirobachi,

How are you running n8n? There seems to be a problem with your instance. Did you try running any other nodes except the YouTube node (you can try the HackerNews node, you don’t need to create credentials for the node)?

3

So I tried YT and notion, I checked now your suggestion and after few seconds I got answer, but loading animation was still there

image
image1596×844 67.8 KB

I checked google console, and it says that I used API, so n8n connected with Google.

I run it on docker, self-hosted with nginx, I run it with following command

sudo docker run -d --restart always --name n8n -p 127.0.0.1:5678:443 -e N8N_BASIC_AUTH_ACTIVE=true -e N8N_BASIC_AUTH_USER=simon -e N8N_BASIC_AUTH_PASSWORD="******" -e N8N_HOST="n8n.hryszko.dev" -e N8N_PORT=443 -e N8N_PROTOCOL="https" -e WEBHOOK_TUNNEL_URL="https://n8n.hryszko.dev/" -e VUE_APP_URL_BASE_API="https://n8n.hryszko.dev" -v ~/n8n:/var/www/n8n.hryszko.dev n8nio/n8n

And this config in nginx

server {
  listen 0.0.0.0:443 ssl http2;
  server_name n8n.hryszko.dev;

  ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
  ssl_ciphers 'ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS';

  server_tokens off;

  gzip on;
  gzip_buffers 4 32k;
  gzip_types text/plain text/css application/x-javascript;
  gzip_vary on;

  location / {
    proxy_pass http://127.0.0.1:5678;
    add_header Access-Control-Allow-Origin *;
  }

    ssl_certificate /etc/letsencrypt/live/n8n.hryszko.dev/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/n8n.hryszko.dev/privkey.pem; # managed by Certbot
}

Thanks for help ^^

4

Sounds like an issue with Server-Sent Events. Please check the following nginx configuration and add missing ones to make them work correctly:

5

Yes, I added missed locations and listen, and it’s working by now.

Lovely, thanks!

1 Like
6

Great to hear! Have fun!

1 Like