Rafael

@systembell I have VPN working, but with openvpn. In order to progress further I want to setup automated CI tests, and for that I need a cloud image of the...

thanks @rudibroekhuizen, actually I did restart this. I will try to see if it still goes with the new release. I have not updated my opnsese, as I don't know...

I am seeing this problem too... multiple executions for the same message. I have verified that it is actually the same payload triggering multiple times the same workflow. I connect...

Actually this is my second MQTT workflow, but I have looked but at executions of the previous one, and I can also see 10s of executions of the workflow within...

cc @Joffcom MQTT seems to be complete broken to me, and affects the stability of n8n. Once incoming message triggers 10s of executions. I am reviewing the implementation of this...

Here is how dramatic the resource leakage by MQTT trigger is:  you can guess the blue n8n container jumped to 5GB almost and crashed its VM.

I did some additional testing with a brand new container, and I got 2 listeners to work normally, and adding a third reproduced the problem. So, @edlundin seems right, the...

I think I found the problem. @edlundin did you fill the client id in your MQTT listener settings? I did. And that causes the trouble. The issue is that according...

I think multiple connections with same client-id are basically banned by the protocol. Like 2 computers with the same IP on the same network, anything can go wrong from then...

@edlundin I mostly agree. The client ID seems of little value, other than debugging. I have checked other software and all seem to do the same, ask for it and...