Latest chatwoot update is breaking the app for me.

[joseph]

@andreasdueren so, is this an upstream bug?

[Kinzi]

Thanks @andreasdueren this worked!

Needed a minute to figure the CLI part out as I hadn't used that before (it's on your machine not on the server or the app container for everybody else)

Also make sure to fill in the password env var names in step 4.

[andreasdueren]

@joseph not sure, seems to only affect installations of a certain age. I guess upstream or Cloudron could do what I did manually. But unless more people will reach out this is an isolated issue.

[andreasdueren]

@Kinzi yes forgot to look up the correct Postgres ENV lol

[fbartels]

@andreasdueren @joseph overall the upstream project does not seem to be very good with database topics. I recently wanted to create some workflows in my older installation and first needed to fix some indexes as well before the app responded successfully.

My installation ran into this upgrade issue as well, thanks for the commands. Instead of running the last database migrations myself I just disabled the recovery mode and restarted the app.

[humpty]

I have a 2 year old installation with the same issue. I'm not sure how to do the CLI thing. Initially, I tried the code in terminal and in putty totally missing Kinzi's note at first. I'll just revert and wait for a proper package.

[andreasdueren]

@humpty Here this should work:

1. create backup of chatwoot in case something goes bad
2. put app into recovery mode
3. enter web terminal and enter

set -euo pipefail

source /app/data/env.sh

export FRONTEND_URL="${CLOUDRON_APP_ORIGIN}"
export REDIS_URL="redis://${CLOUDRON_REDIS_HOST}:${CLOUDRON_REDIS_PORT}"
export REDIS_PASSWORD="${CLOUDRON_POSTGRESQL_PASSWORD}"
export POSTGRES_DATABASE="${CLOUDRON_POSTGRESQL_DATABASE}"
export POSTGRES_USERNAME="${CLOUDRON_POSTGRESQL_USERNAME}"
export POSTGRES_PASSWORD="${CLOUDRON_POSTGRESQL_PASSWORD}"
export POSTGRES_HOST="${CLOUDRON_POSTGRESQL_HOST}"
export POSTGRES_PORT="${CLOUDRON_POSTGRESQL_PORT}"
export RAILS_ENV=production

echo "Checking for duplicate email templates..."
psql "$CLOUDRON_POSTGRESQL_URL" -v ON_ERROR_STOP=1 -c "
SELECT name, template_type, locale, account_id, inbox_id, COUNT(*)
FROM email_templates
GROUP BY name, template_type, locale, account_id, inbox_id
HAVING COUNT(*) > 1;
"

echo "Creating missing legacy index if needed..."
psql "$CLOUDRON_POSTGRESQL_URL" -v ON_ERROR_STOP=1 -c "
CREATE UNIQUE INDEX IF NOT EXISTS index_email_templates_on_name_and_account_id
ON email_templates (name, account_id);
"

echo "Running Chatwoot database migrations..."
cd /app/code
bundle exec rails db:migrate

echo "Done. Now disable Recovery Mode / Debug Mode and restart the app."

4. when prompted, take app out of recovery mode

[humpty]

My attempts didn't work as the app didn't want to start.

1- Should the app be updated to the broken 1.54 or stick with the working 1.53.1?
2- Should I paste the entire code above in one-shot? If not, then my other attempt by pasting one line at a time didn't work either? I'll try pasting in sections as they're pasted above.

Fixed.

To answer my own questions.
1- Yes, apply the code to broken package 1.54.
2- Apply code one section at a time.

App package 1.54.0 now starts as it should. Thank you @andreasdueren

[andreasdueren]

@humpty You need to update it first, then follow those steps. In theory the entire code copied and pasted into the terminal should work, but you can also paste them line by line. Unfortunately I can't test this.

[humpty]

@andreasdueren one line at a time didn't work nor pasting it whole. I pasted them one section at a time and that worked. The "export" lines were done one at a time though. But the "echo" ones had to be as one. e.g.

echo "Checking for duplicate email templates..."
psql "$CLOUDRON_POSTGRESQL_URL" -v ON_ERROR_STOP=1 -c "
SELECT name, template_type, locale, account_id, inbox_id, COUNT(*)
FROM email_templates
GROUP BY name, template_type, locale, account_id, inbox_id
HAVING COUNT(*) > 1;
"

This was pasted in one go.