@timconsidine Could you please pull the latest changes and try again?

BASE_URL is from the FRONTEND_URL env variable you set in .env file. Please update the .env file FRONTEND_URL value to be your Cloudron chatwoot app URL.

Yes you are right. Please use the HTTPS one without specfiying port.

@timconsidine This is resolved. Please pull the latest changes.

@nebulon awesome Thank you. Let us know if you need anything from us. I started with the Chatwoot base image to have something working quickly.

@nebulon @girish IMAP is not supported yet but it's being worked on at the moment. The email inbox setup is needed only if the user wishes to use email via Chatwoot. Regular notifications and other transactional email alerts should work with the basic SMTP setup.

For transaction/notification emails --> https://www.chatwoot.com/docs/self-hosted/configuration/environment-variables#configure-emails

For Email Channel/ Email Continuity/Email Inbox --> https://www.chatwoot.com/docs/self-hosted/configuration/features/email-channel/conversation-continuity

@girish Could you please take a look and provide some early feedback? What are the next steps to get this published to Cloudron app store ?

ref: https://github.com/chatwoot/cloudron-chatwoot

@v_shnu said in Chatwoot - Simple and elegant live chat software:

@girish Could you please take a look and provide some early feedback? What are the next steps to get this published to Cloudron app store ?
ref: https://github.com/chatwoot/cloudron-chatwoot

Hey @girish, have you had a chance to look at this ?

@nebulon Sojan's username would be sojan-official. Thank you.

@chap @nebulon My guess is this is due to the location of the .env file right now. It should be at /app/code/.env.

an MR for the same --> https://git.cloudron.io/cloudron/chatwoot-app/-/merge_requests/1

This also means env variable set using .env were not taking effect. Have there been users reporting issues related to that ?

@nebulon Sojan's username would be sojan-official. Thank you.

@nebulon @girish IMAP is not supported yet but it's being worked on at the moment. The email inbox setup is needed only if the user wishes to use email via Chatwoot. Regular notifications and other transactional email alerts should work with the basic SMTP setup.

For transaction/notification emails --> https://www.chatwoot.com/docs/self-hosted/configuration/environment-variables#configure-emails

For Email Channel/ Email Continuity/Email Inbox --> https://www.chatwoot.com/docs/self-hosted/configuration/features/email-channel/conversation-continuity

@imc67 Awesome and happy to hear that.

PS: I know that feeling - a fellow FF user.

@imc67 If this issue is still persisting for you, could you please open an issue on the Chatwoot GitHub repo?

@nebulon @girish Also it would be great if we could have access to the repo. vishnu at chatwoot dot com and sojan at chatwoot dot com.

@nebulon awesome Thank you. Let us know if you need anything from us. I started with the Chatwoot base image to have something working quickly.

@v_shnu said in Chatwoot - Simple and elegant live chat software:

@girish Could you please take a look and provide some early feedback? What are the next steps to get this published to Cloudron app store ?
ref: https://github.com/chatwoot/cloudron-chatwoot

Hey @girish, have you had a chance to look at this ?

BASE_URL is from the FRONTEND_URL env variable you set in .env file. Please update the .env file FRONTEND_URL value to be your Cloudron chatwoot app URL.

Yes you are right. Please use the HTTPS one without specfiying port.

@timconsidine This is resolved. Please pull the latest changes.