Execution keeps loading

I was running into a little issue while trying to make an ai agent to chat to in while running n8n in docker in aws on ec2. When i am trying to chat to the ai agent the execution keeps loading and i don’t get an answer from the ai agent until i stop the execution … is there a solution for this one? currently i am running n8n version 1.65.2.

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

Databse : Sql lite

  • n8n EXECUTIONS_PROCESS setting (default: own, main): Default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Aws ec2

Hey @The_Cloud,

Are you using nginx as a reverse proxy at all? It kind of sounds like there is an issue with websockets not working correctly.

Yeah…i appreciate your reply it actually was an issue with the websocket i didn’t add it into my environment variables and i also had to edit nginx code a bit to finally sort it all out …

This is what my nginx code looks like now

server {
    listen 443 ssl; # managed by Certbot
    server_name thecloud.hopto.org;

    ssl_certificate /etc/letsencrypt/live/thecloud.hopto.org/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/thecloud.hopto.org/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    # Main proxy to n8n
    location / {
        proxy_pass http://localhost:5678;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
        chunked_transfer_encoding off;
        proxy_buffering off;
        proxy_cache off;
    }

    # Optional: WebSocket specific location (if applicable)
   # If you are using a specific WebSocket endpoint (e.g., /ws), you can specify it like this:
    # location /ws/ {
    #     proxy_pass http://localhost:5678;
    #     proxy_http_version 1.1;
    #     proxy_set_header Upgrade $http_upgrade;
    #     proxy_set_header Connection 'upgrade';
    #     proxy_set_header Host $host;
    #     proxy_cache_bypass $http_upgrade;
    # }

}

# HTTP to HTTPS redirect
server {
    if ($host = thecloud.hopto.org) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    listen 80;
    server_name thecloud.hopto.org;
    return 404; # managed by Certbot
}
1 Like

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