Topics created by nebulon

This is implemented in 7.2.1.

@infogulch said in Upstream dropped LDAP support with v5.7.0:

Did you happen to check whether the x-forwarded-* headers are stripped from the original request? Theres a potential impersonation vuln if we're not careful with these headers in particular.

Right... The headers are always set/cleared across all locations in the nginx proxy auth config. It's in our e2e tests as well (though they have not passed yet).

edit : actually it recovered all the workflows, my bad
now I just have to create second user and share workflow with members

this is just great.
thanks all!

App is out now, we have moved the package to use terser instead.

@robi Sadly I did not take ANY Fotos at all 😄
I hope others might have taken pictures of the food and other stuff 😬

@sparkwise

This is nice but not strictly necessary.

It is very nice indeed but being necessary or not is relative to how much features one wants to make life easier and getting nearer to what's offered by Big techs and SaaS in the like.

So, if that specific function can be fixed for that app I'd say it should be. Of course nothing is absolute lol 😆

Hi @pratik, I made the manual payment using the invoice statement, that I got on my email address...

@3246 thanks for trying Cubby, as you realized, it is still only some alpha basically and has no support for volumes yet. But it will get support for volumes. Most likely though not in the same way other apps have, but more like a volume is its own storage, to be able to have multiple data volumes for different purposes.

@jeau I started to explore OmekaS and created an instance for testing.
I just wanted to say THANK YOU for a really impressive piece of software. 👍 👏 👏 👏

@atrilahiji said in Cannot reach backend server:

So this appears to be an issue on Firefox rn that has been reported on their forum.

https://community.n8n.io/t/connection-lost/1471/49

Using a chromium based browser seems to be fine in my testing.

Edit: This post seems to have a suggested solution via the NGINX config https://github.com/n8n-io/n8n/issues/36#issuecomment-539647882
@nebulon @girish

The mentioned fix is already active.
See https://git.cloudron.io/cloudron/n8n-app/-/blob/master/pkg/nginx.conf#L64
But the issue persists.

Additional information: There is no API_Secret in the ENV file in the standard app package. Depending on your thousands of clients, it takes some time to migrate. For me, it was done in less than 5 minutes.

The only moment of confusion was: when installing IN v. 5. you have to fill in the name of the company in a modal frame. After the migration it took me a few seconds to realise that there is a multi-company option in IN v. 5 and I had to switch to the "other" (migrated) company (which has the same company name).

It looks like everything has migrated well.

ah great thanks for the explanation and details. Good for other users if they hit the same issue/question.

@imc67
yep, @girish fixed in seconds, like a superhero! was an issue with the system link in rsync, and I discovered the output of the error was on the app log file, not on the container that's why we couldn't find anything on the log in Cloudron initially.

If you have a Dockerfile, you can package custom apps for deploying on Cloudron. No need to add/change nginx entries etc. Please see https://docs.cloudron.io/custom-apps/tutorial/