As @joseph mentioned, we can only give support for the part of Cloudron we build, which is the platform itself and the app packaging. For app internal issues, the upstream app devs/community are the experts.

How did you contact support? I can't find any ticket via email related to this topic, nor ones which we haven't at least reacted to.

@vishalw3villa you have to ask this question in the upstream Chatwoot forum - https://github.com/orgs/chatwoot/discussions . This is the Cloudron forum for Chatwoot package.

@girish said in New user emails dont work:

@xboxhaxorz cloudron only supports STARTTLS for relay. So, you have to use port 587 and not port 465 .

Great, its all working now

Thanks

@fbartels said in Move Chatwoot:

How did the move go?

Well it has not happened yet. The client decided wait until other issues are resolved. But it is still on the roadmap. I will post when it comes back around.

Yes, 95$ month sorry. They does 30% if you qualify for their "startup" discount. They also have a free plan, which is free btw. And a pro plan for 25$ per month, unlimited number of agents.

I've noticed they says the issue is fixed on Github, and there's another user says it's still experiencing the issue.

@clendeninc thanks, but can you provide the doc link where you read that? Atleast, I cannot find it be searching for your text in their docs.

@jfrere Did you figure this out? Can you tell me some steps to reproduce this, so I can check if this is a package issue?

This is the answer I've got from Github : https://github.com/chatwoot/chatwoot/issues/8228

This is expected. You would have to manually move everything to local storage. The system won't automatically copy everything over to the local machine.

@jfrere Did you ask in the upstream issue tracker or forum about this? The docs are a bit lacking/suspect here for us to debug this.

@nennogabriel please be 100% sure you did not run into this issue: https://forum.cloudron.io/topic/7763/chatwoot-storage-bloat-bug-with-mail-inbox

It's out now.

The reason here was, that the changelog mentioned some potential 3rdparty integration testing, so we waited for a bit to give those time to catch up ideally. Given your reminder I now pushed the update though as anyways 2 weeks passed.

Apparently there was a typo or missing quotes in the env.sh maybe @shivamkb17 could share those details for others.

@girish Amazing! Updating now. Thank you!

Nevermind -- looks like just a stale session. New one worked fine!

@girish Is there an estimated timeline for 7.5's release? I'm waiting for an upstream fix in 2.18.0 of chatwoot and it sounds like that's blocked on the cloudron update then?

Also, the app logs will help.