"Connection Lost" warning

[Valerian_Lebert]

Hi

I have the warning “Connection Lost” when editing a workflow. Can’t find the save button anymore. However, is I click on “workflows” to go home I have the popup asking me to save and it is working properly.

I recently upgraded from beta to 1.3.1, is it a known bug ?

Cheers

Information on your n8n setup

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

[EmeraldHerald]

Hi @Valerian_Lebert Thanks for reporting this, and sorry you’re experiencing it

This is indeed something our engineering team is looking into - I’ll let them know you’re seeing it too, and be back with you as soon as I have an update.

[Valerian_Lebert]

@EmeraldHerald
Thanks for your answer

Are there any workaround ? Currently, to save my workflow I have to go back to the workflow list. Are you aware of any other trick to be able to save current workflow ?

[EmeraldHerald]

HI @Valerian_Lebert I’m unfortunately not aware of any workaround on this one at the moment You’ll be sure to know when there’s an update around this, though!

[Valerian_Lebert]

Hi @EmeraldHerald

I realized that this issue is more criticat than I thought : I can’t create a new webhook trigger for example.

When clicking “listen for events” I have the error connection lost to the server. Impossible to initialize the webhook trigger

[Valerian_Lebert]

I could fix my issue thanks to this post

I updated n8n to 1.5 im getting connection lost

After going down a huge rabbit hole… This fixed it for me! THANK YOU! [Nginx-Proxy-Manager]

I had change my nginx conf for websocket support

    location / {
        proxy_pass http://localhost:5678;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade; # websocket support
        proxy_set_header Connection "Upgrade";  # websocket support
        proxy_set_header Host $host;
        chunked_transfer_encoding off;
        proxy_buffering off;
        proxy_cache off;
    }

[EmeraldHerald]

HI @Valerian_Lebert - so sorry that you were having such a critical issue, but thank you so much for posting your solution!