Anyone else getting connection issues after the latest update to nocodb?

[umnz]

I have some n8n automations that work with NocoDB and for the first time I'm getting weird issues when trying to read/write from nocodb after the latest update (3 days ago). I'm still investigating but just wanted to check if anyone else is having similar issues?

[umnz]

Sorry, I should be super clear:
In a single Cloudron installation I have both n8n and nocodb talking to each other. After the last update (to nocodb) I am occasionally getting ERR CONNECTION REFUSED. Which is unusual since it's internal and has never been an issue until the latest update from nocodb.

Can the Cloudron team look into this? Is it a docker issue?

[umnz]

I've raised an issue assuming it is a them problem and not a Cloudron docker networking problem.
https://github.com/nocodb/nocodb/issues/11698

[robi]

Have you tested each step manually with curl? Locally in noco and from the N8n container?

[umnz]

It may be a bug that was fixed in the very latest release according to the developer. I've built a suitable error handling workaround in n8n for now. But we need to grab the latest release and push the update to Cloudron. @girish

[girish]

Latest release is published now

[umnz]

@girish thank you, much appreciated.