@girish Yes I did this (did not update the post with export) and it seems to work fine, I will watch the new "binary files" Folder. Here is from Discord: [image: 1709312526346-7144247c-6362-4924-9028-c531b7509a98-capture_240301_110102.jpg]

@girish Thanks for that link, it confirmed the conclusion I was coming to. "local" to n8n is internal (and volume mounts) to the docker container on the server that n8n is running on. I was hoping that it could connect to the local network path when running. I am starting to understand it better now. So now I am looking at ways that it connects to NextCloud and see if we can make a go of that - but the seems to be no "triggers" for NextCloud.

This was a bug. Fixed in latest package. Thanks for reporting.

@jdaviescoates It's included now I think

@girish Just tried it. Seems to work alright!

I forked the topic @parhelium what is the context? which cloudron version are you on (in the Settings page)? Looks like it is very old to not know what upstreamVersion is.

@nebulon Yes i confirmed all 4 n8n containers are updated and working thank you.

Why not use native system functionality on ios? https://gregmorris.co.uk/blog/publishing-to-wordpress/

Hi @girish , Many thanks I'll have a look at it

@yurilemes it's out now. I am guessing you mean 1.15.2.

@girish thank you problem solved

Perfect, thank you very much

Hi @girish Kindly also check this n8n team response related to this issue, in the context of Cloudron: https://community.n8n.io/t/cli-commands-not-working-in-v1-x-x/29309/3 Thanks.

Oh, you have already updated the n8n package, forgive my inattention

All good !

@zonzonzon Services view - https://docs.cloudron.io/services/#configure

Hey @alwynispat Maybe you should use the SSH node instead of the Execute Command node. From what I understand the Whois package is installed on the server, so to run it you will have to call it via ssh command. The Execute Command node executes commands inside the cloudron n8n container, which by default will run in the /app/code path of your n8n container. That is the reason why it does not find the Whois package when running the Execute Command node.

Solution (more of a workaround) : https://community.n8n.io/t/google-sheets-bug-cant-activate-workflow/27211/6 I believe it's a minor bug on the GoogleSheets Trigger Node

@Matheus-0 what is the problem? Seems to be ok here. [image: 1686033715674-fa6fd4ed-60a0-4c6a-9666-e8e89f598a7a-image-resized.png]