Cloudron Forum

Package update is out.

nothing but depreciated errors. weird thing is, I've rebuilt the site using a backup from all-in-one wp migration tool to www.website.com and redirected website.com to it. site is still standing. Attacks happening to root domain?

So I think I've found the solution. Modify the Proxy Host config > Advanced and paste the following: set_real_ip_from 03.21.244.0/22; set_real_ip_from 103.22.200.0/22; set_real_ip_from 103.31.4.0/22; set_real_ip_from 104.16.0.0/13; set_real_ip_from 104.24.0.0/14; set_real_ip_from 108.162.192.0/18; set_real_ip_from 131.0.72.0/22; set_real_ip_from 141.101.64.0/18; set_real_ip_from 162.158.0.0/15; set_real_ip_from 172.64.0.0/13; set_real_ip_from 173.245.48.0/20; set_real_ip_from 188.114.96.0/20; set_real_ip_from 190.93.240.0/20; set_real_ip_from 197.234.240.0/22; set_real_ip_from 198.41.128.0/17; #use any of the following two real_ip_header CF-Connecting-IP; #real_ip_header X-Forwarded-For; this will allow True Client IP Address to be passed to Cloudron.

So here’s the thing, my router has dual WAN. Recently, my primary has not been very stable and would failover to my secondary. I could see that Cloudron has picked up the new public IP Address but hasn’t updated the DNS records for the apps. Thanks, every 10 mins would be a lot better than 5 mins past the hour.

Updated package is out.

@girish said in Issue with the API to change MemoryLimit: --data-raw '{"memoryLimit":973078528} Thanks! this bit helped.

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.

when going to https://192.168.1.20:8000, it'll redirect me to a login on /webman/index.cgi

@joseph Hey, I'll provide a link here, where the exact details of the package are given. I think there should be no problem. https://packages.ubuntu.com/oracular/nut-client

Are you talking about https://docs.cloudron.io/apps/#data-directory or some other directory for data within Wordpress?

@alwynispat thanks, updated.

A new app package is already out

@alwynispat we have some resources on that topic at https://docs.cloudron.io/packaging/tutorial/ as well as a forum section https://forum.cloudron.io/category/96/app-packaging-development

@alwynispat actually, https://forum.cloudron.io/topic/8321/forwarding-the-true-client-ip-address/ is the feature request . Let's continue there.

@girish ok that clarifies it then.

@girish great that works! remember to rebuild the feeds and redeploy elasticsearch if that's in use.

BTW (back to the topic of this thread): Mastodon 4.1.1 has just been released.

@alwynispat sure of course: Puma export WEB_CONCURRENCY=4 # number of worker processes export MAX_THREADS=5 # the number of threads per process Streaming API export STREAMING_CLUSTER_NUM=2 # number of worker processes Sidekiq export SIDEKIQ_THREADS=4 export DB_POOL=25 # must be at least the same as the number of threads

While there are no mastodon specific notes on importing, there is one guide at https://docs.cloudron.io/guides/import-postgresql/ for importing postgres apps (which mastodon uses). For exporting, one can make a backup of the app and will have the db dump part of the backup together with all other data.

@nebulon i've identified the issue and it was my S3 configuration. The endpoint and hostname should never have the bucket name. S3_ENDPOINT=https://s3.us-west-001.example.com S3_HOSTNAME=s3.us-west-001.example.com