Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum
Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Chatwoot
  3. Chatwoot 1.36.1 Upgrade Issue

Chatwoot 1.36.1 Upgrade Issue

Scheduled Pinned Locked Moved Solved Chatwoot
15 Posts 7 Posters 307 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    mazarian
    wrote last edited by
    #6

    I am having a similar error in my logs, but it's happening well after the upgrade.

    Mar 18 10:06:07 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:06:17 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:06:23 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:06:33 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:06:43 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:06:53 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:06:54 => Sourcing /app/data/env.sh
Mar 18 10:06:54 => Starting chatwoot
Mar 18 10:06:54 => Upgrading existing db
Mar 18 10:06:56 I, [2025-03-18T17:06:56.956461 #10] INFO -- : [rake ip_lookup:setup] IP_LOOKUP_API_KEY empty. Skipping geoip database setup
Mar 18 10:06:57 2025-03-18T17:06:57Z
Mar 18 10:06:57 (See full trace by running task with --trace)
Mar 18 10:06:57 /app/code/db/schema.rb:134:in `block in <main>'
Mar 18 10:06:57 /app/code/db/schema.rb:134:in `block in <main>'
Mar 18 10:06:57 /app/code/db/schema.rb:13:in `<main>'
Mar 18 10:06:57 /app/code/db/schema.rb:13:in `<main>'
Mar 18 10:06:57 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
Mar 18 10:06:57 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
Mar 18 10:06:57 /app/code/lib/tasks/db_enhancements.rake:18:in `each'
Mar 18 10:06:57 /app/code/lib/tasks/db_enhancements.rake:18:in `each'
Mar 18 10:06:57 /app/code/lib/tasks/db_enhancements.rake:22:in `block (3 levels) in <main>'
Mar 18 10:06:57 /app/code/lib/tasks/db_enhancements.rake:22:in `block (3 levels) in <main>'
Mar 18 10:06:57 ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (ActiveRecord::StatementInvalid)
Mar 18 10:06:57 Caused by:
Mar 18 10:06:57 PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (PG::ConnectionBad)
Mar 18 10:06:57 Tasks: TOP => db:chatwoot_prepare
Mar 18 10:06:57 This probably means the server terminated abnormally
Mar 18 10:06:57 This probably means the server terminated abnormally
Mar 18 10:06:57 before or while processing the request.
Mar 18 10:06:57 before or while processing the request.
Mar 18 10:06:57 rails aborted!
Mar 18 10:07:07 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:07:17 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:07:26 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:07:33 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:07:43 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:07:43 BoxError: Unknown install command in apptask:error
Mar 18 10:07:43 BoxError: Unknown install command in apptask:error
Mar 18 10:07:53 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:07:57 => Starting chatwoot
Mar 18 10:07:57 => Sourcing /app/data/env.sh
Mar 18 10:07:57 => Upgrading existing db
Mar 18 10:08:00 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.185:3000
Mar 18 10:08:00 I, [2025-03-18T17:08:00.416259 #10] INFO -- : [rake ip_lookup:setup] IP_LOOKUP_API_KEY empty. Skipping geoip database setup
Mar 18 10:08:00 rails aborted!
Mar 18 10:08:00 ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (ActiveRecord::StatementInvalid)
Mar 18 10:08:00 This probably means the server terminated abnormally
Mar 18 10:08:00 before or while processing the request.
Mar 18 10:08:00 /app/code/db/schema.rb:134:in `block in <main>'
Mar 18 10:08:00 /app/code/db/schema.rb:13:in `<main>'
Mar 18 10:08:00 /app/code/lib/tasks/db_enhancements.rake:22:in `block (3 levels) in <main>'
Mar 18 10:08:00 /app/code/lib/tasks/db_enhancements.rake:18:in `each'
Mar 18 10:08:00 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
Mar 18 10:08:00 2025-03-18T17:08:00Z
Mar 18 10:08:00 Caused by:
Mar 18 10:08:00 PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (PG::ConnectionBad)
Mar 18 10:08:00 This probably means the server terminated abnormally
Mar 18 10:08:00 before or while processing the request.
Mar 18 10:08:00 /app/code/db/schema.rb:134:in `block in <main>'
Mar 18 10:08:00 /app/code/db/schema.rb:13:in `<main>'
Mar 18 10:08:00 /app/code/lib/tasks/db_enhancements.rake:22:in `block (3 levels) in <main>'
Mar 18 10:08:00 /app/code/lib/tasks/db_enhancements.rake:18:in `each'
Mar 18 10:08:00 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
Mar 18 10:08:00 Tasks: TOP => db:chatwoot_prepare
Mar 18 10:08:00 (See full trace by running task with --trace)
Mar 18 10:08:17 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:08:27 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:08:33 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:08:43 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:08:53 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:09:01 => Starting chatwoot
Mar 18 10:09:01 => Sourcing /app/data/env.sh
Mar 18 10:09:01 => Upgrading existing db
Mar 18 10:09:03 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.185:3000
Mar 18 10:09:03 I, [2025-03-18T17:09:03.629615 #10] INFO -- : [rake ip_lookup:setup] IP_LOOKUP_API_KEY empty. Skipping geoip database setup
Mar 18 10:09:04 rails aborted!
Mar 18 10:09:04 ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (ActiveRecord::StatementInvalid)
Mar 18 10:09:04 This probably means the server terminated abnormally
Mar 18 10:09:04 before or while processing the request.
Mar 18 10:09:04 /app/code/db/schema.rb:134:in `block in <main>'
Mar 18 10:09:04 /app/code/db/schema.rb:13:in `<main>'
Mar 18 10:09:04 /app/code/lib/tasks/db_enhancements.rake:22:in `block (3 levels) in <main>'
Mar 18 10:09:04 /app/code/lib/tasks/db_enhancements.rake:18:in `each'
Mar 18 10:09:04 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
Mar 18 10:09:04 2025-03-18T17:09:04Z
Mar 18 10:09:04 Caused by:
Mar 18 10:09:04 PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly (PG::ConnectionBad)
Mar 18 10:09:04 This probably means the server terminated abnormally
Mar 18 10:09:04 before or while processing the request.
Mar 18 10:09:04 /app/code/db/schema.rb:134:in `block in <main>'
Mar 18 10:09:04 /app/code/db/schema.rb:13:in `<main>'
Mar 18 10:09:04 /app/code/lib/tasks/db_enhancements.rake:22:in `block (3 levels) in <main>'
Mar 18 10:09:04 /app/code/lib/tasks/db_enhancements.rake:18:in `each'
Mar 18 10:09:04 /app/code/lib/tasks/db_enhancements.rake:18:in `block (2 levels) in <main>'
Mar 18 10:09:04 Tasks: TOP => db:chatwoot_prepare
Mar 18 10:09:04 (See full trace by running task with --trace)
Mar 18 10:09:17 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:09:27 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 18 10:09:33 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:09:43 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:09:53 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000
Mar 18 10:10:03 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.185:3000

    I tried recovering from backup and cloning and am getting the following error:

    An error occurred during the clone operation: Addons Error: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/e2f314e0-389e-4c1b-8e80-9852e13db8e3/postgresqldump to http://172.18.30.2:3000/databases/dbe2f314e0389e4c1b8e809852e13db8e3/restore?access_token=b637659aed0a708f188d2902fc267163718b8c6777cd722433926b0654ff03c7c2fc782f7c39a559f0d1954f031c7215eb96ebf6bc759500e2419d84607396d249c157dc7a7db537926351f20ae6a23261db0a55c93e07a278161db6c2e7f4fdd04756ff7cc1cd30bd67096101d9b83b643ebf91abf5f2e3a2026dbd93d1ae6b&username=usere2f314e0389e4c1b8e809852e13db8e3: status 500 complete false

    Any help would greatly be appreciated!

    1 Reply Last reply
    0
    • nebulonN Away
      nebulonN Away
      nebulon
      Staff
      wrote last edited by
      #7

      Is your postgres service up and running? Since it returned a 500 status code during database import, it should have error messages in its logs.

      1 Reply Last reply
      0
      • M Offline
        M Offline
        mazarian
        wrote last edited by
        #8

        I'm not quite sure how to check - I am only able to get into recovery mode and when going into the terminal and pressing the Postgres button, I see this:

        root@fa89594f-7176-4a81-9c25-1686af1e50da:/app/code# PGPASSWORD=${CLOUDRON_POSTGRESQL_PASSWORD} psql -h ${CLOUDRON_POSTGRESQL_HOST} -p ${CLOUDRON_POSTGRESQL_PORT} -U ${CLOUDRON_POSTGRESQL_USERNAME} -d ${CLOUDRON_POSTGRESQL_DATABASE} 
psql (14.9 (Ubuntu 14.9-0ubuntu0.22.04.1), server 16.6 (Ubuntu 16.6-0ubuntu0.24.04.1))
WARNING: psql major version 14, server major version 16.
         Some psql features might not work.
Type "help" for help.

dbfa89594f71764a819c251686af1e50da=>
        andreasduerenA 1 Reply Last reply
        0
        • M mazarian

          I'm not quite sure how to check - I am only able to get into recovery mode and when going into the terminal and pressing the Postgres button, I see this:

          root@fa89594f-7176-4a81-9c25-1686af1e50da:/app/code# PGPASSWORD=${CLOUDRON_POSTGRESQL_PASSWORD} psql -h ${CLOUDRON_POSTGRESQL_HOST} -p ${CLOUDRON_POSTGRESQL_PORT} -U ${CLOUDRON_POSTGRESQL_USERNAME} -d ${CLOUDRON_POSTGRESQL_DATABASE} 
psql (14.9 (Ubuntu 14.9-0ubuntu0.22.04.1), server 16.6 (Ubuntu 16.6-0ubuntu0.24.04.1))
WARNING: psql major version 14, server major version 16.
         Some psql features might not work.
Type "help" for help.

dbfa89594f71764a819c251686af1e50da=>
          andreasduerenA Offline
          andreasduerenA Offline
          andreasdueren
          wrote last edited by
          #9

          @mazarian Go to https://my.tld.com/#/services and increase memory if necessary and/or reboot that service

          M 1 Reply Last reply
          0
          • andreasduerenA andreasdueren

            @mazarian Go to https://my.tld.com/#/services and increase memory if necessary and/or reboot that service

            M Offline
            M Offline
            mazarian
            wrote last edited by
            #10

            @andreasdueren and @nebulon thank you both for your replies!

            I just looked at my services, and things looked ok. Graphite was at 84% and I doubled the memory. I also doubled my Postgres memory and Redis memory (for the affected Chatwoot app) but none of those things seemed to help.

            cefff62e-2183-4385-97eb-fa7a62bb8e65-image.png

            1 Reply Last reply
            0
            • M Offline
              M Offline
              mazarian
              wrote last edited by
              #11

              It's also odd- when I try switching between recovery mode off and on, Redis throws errors and I have to restart the service. But doing so doesn't allow me to start the application outside of recovery mode and still in the error logs, I see the same PG errors.

              1 Reply Last reply
              0
              • M Offline
                M Offline
                mazarian
                wrote last edited by
                #12

                Just wanted to add - it seems like I am having to restore from backup for many of my apps. All of the restores are working except for Chatwoot. It seems like something went wrong after the upgrade to Cloudron 8.3.

                S 1 Reply Last reply
                1
                • J Online
                  J Online
                  joseph
                  Staff
                  wrote last edited by
                  #13

                  @mazarian if you can write to support@cloudron.io, we can take a look . it seems a few hit this issue with restoring chatwoot on the recent postgres. however, we haven't been to reproduce it.

                  1 Reply Last reply
                  0
                  • M mazarian

                    Just wanted to add - it seems like I am having to restore from backup for many of my apps. All of the restores are working except for Chatwoot. It seems like something went wrong after the upgrade to Cloudron 8.3.

                    S Offline
                    S Offline
                    stevespaw
                    wrote last edited by
                    #14

                    @mazarian said in Chatwoot 1.36.1 Upgrade Issue:

                    Just wanted to add - it seems like I am having to restore from backup for many of my apps. All of the restores are working except for Chatwoot. It seems like something went wrong after the upgrade to Cloudron 8.3.

                    Same issue here!

                    1 Reply Last reply
                    0
                    • S Offline
                      S Offline
                      stevespaw
                      wrote last edited by
                      #15

                      8.3.1 seems to have fixed this issue! Thanks team Cloudron!

                      1 Reply Last reply
                      0
                      • nebulonN nebulon marked this topic as a question
                      • nebulonN nebulon has marked this topic as solved
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes

                      • Login
                      • Don't have an account? Register
                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Bookmarks
                      • Search