Yes I think so can confirm it works thank you.
image.png

@aestela Atleast, the very first post was rejected because it only said "I am facing same problem" or something like that. We rejected it thinking this was spam. Pretty much all the bots now post generic messages like this. I will reply to your other post.

(If you are not happy with the support, of course, just write to support@cloudron.io and we can refund as needed).

i have sent a mail

@girish I just wanted to say thank you for your help two weeks ago!

I didn't get Postgres running because of too little storage on the disk, so I had no idea in this short time how to delete the things out of Postgres.
For us this issue was very critical and I had to fix it very fast and so I just deleted the dump file which means the loss of the directus instance data, but that was okay in this case.
Again: thank you very much and best regards!

Thank you. Good idea!

I ran traceroute and discovered that example.com resolved to the IP of an old server I once used.

Checking my registrar, I found that I had left example.com and www.example.com resolving to that old server's IP.

Deleting those entries has resolved the issue. When I check example.com it shows the expected "You are seeing this page because the DNS record of example.com is set to this server's IP but Cloudron has no app configured for this domain."

Thank you for your help!

Ok. I will doublecheck this. Give me a few hours for this.
Thanks for the moment 🙂

Update: Solution work fine! Thanks a lot. 👍

@Stardenver Depends on how you use the volume.

If you use the volume to store the app's data using data directory , then it's part of backup If you set it up as a mount of the app, then it's not.

redis logs are of the format pid:role timestamp loglevel message . pid is container local.

Role is:

X sentinel C RDB/AOF writing child S slave M master

Unfortunately, there is no way to change the log format in redis (afaik). We just need the message really (others are not useful on Cloudron). See also https://github.com/redis/redis/issues/2545

@Stardenver said in Identify whats causing lags:

So the graph showing 200% is 2 cores on 100% each (or something equal like 4 cores on 50% each)?

The latter is more probable. If you really want to know, run 'htop' from the command line.

@girish said in IPv6 Cloudron Install and Update Issue:

I have been trying to debug failures in Cloudron installations (and updates) for a while now. I narrowed down the issue to IPv6 and DNS as well.

In case it helps:
I have always just used IPv4 because as you alluded to, lots of stuff doesn't work on IPv6 and my life was easier 🙂
In this environment: My cloudron first failed to update on 19th April, going from 7.3.6 to 7.4.1. "Cloudron update failed 04/19/2023 Failed to update Cloudron: Task 4248 timed out"

@simong said in n8n binary path:

Thank you very much! Because of the solution in the n8n Forum I tried writing to the /app/data/.n8n/ folder, which is not writable, but I could just use /app/data/ as the path.

Did you check that /app/data/.n8n/ the .n8n folder exists? Because if does not n8n might not create it for you.
This could have also been your issue.

@oj right, best to have another domain added on Cloudron, so you can change things quickly if required. I wasn't aware of all the recent changes, I have to read up. My primary domain is .in ccTld .

Spam filters don't block delivery status messages as they're needed for troubleshooting.

If someone else decided to use your address as the From: to spam, there isn't much you can do to stop it, only deal with it (filtering, etc) or turn off delivery to that address until the campaign is over.

Forged source headers will always bounce to the source, and yours happens to be deliverable. Sorry.

@nebulon said in Cloudron CLI:

ah. The cli is actually not built to run on Cloudron itself, but it would interact with a Cloudron via REST api.

Is there a specific use-case where you need it on the server?

I want to install the InfluxDB Package, I thought then via Cloudron CLI. So I have to install it on my Client, to install this package.

@Sam_uk I wish they were more transparent on why a site is listed 😕

@d19dotca Yes, that sounds good. We also fixed the logs view now in 7.5 to give a history of past logs. The current one is hard to work with when debugging such things.

@girish silly me sir I had my.domain proxy enabled when I turned off it works 🤣

@scooke I am out of ideas then. If you like, you can reach out on support@cloudron.io and we can debug further to see if we can resurrect the app.