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]

@ericdrgn you can also check the du size on the server for the appdata.

@girish https://forum.cloudron.io/topic/9021/capability-to-tweak-reverse-proxy-config-of-an-app

@girish I thought I had to activate the SSL/TLS toggle because of STARTTLS. I deactivated it and now it works.

@Lanhild happy to merge your change, push away.

@darsh_parsana said in How to increase Disk I/O: disk should be showing more than 250 kb Only because the y axis ends at 250 kB/s does not mean that this is the limit. The table dynamically grows, so if you have something that would cause more disk i/o the scale would adapt.