Disappearing Inboxes (after v3.0 upgrade) #7744
Comments
|
@jochenstu Which version of Chatwoot were you upgrading from? Also, your OS version? |
vishnu-narayanan
added
self-hosted
|
Upgrade from Chatwoot Version: 2.18.0 I have used and always upgraded this instance for ~12 month now using cwctl. |
|
@jochenstu Thank you for letting us know. Just wanted to check whether you are upgrading from a very old version. SInce the inboxes show up, migrations/upgrade seems to have worked. Could you try a different browser or incognito window? Any error logs on browser console? |
|
+1 |
|
Sure! After clearing the site cookies the issue is gone. Thanks for the pointer. I don't know what to make off that. Should probably better be avoided, but probably not worth investigating further. |
|
Got the same issue, clearing cookies does not fix the bug. Though I get the following errors in the rails console: |
|
Same problem here. From 2.18 to 3.0.0 updated to node 16 |
|
Fixed after upgrading Ruby to 3.2.2, i was using 3.1 @jochenstu wich version do you have? |
This look like a case of migrations not being run.. also did you restart the services after running the migrations ? |
|
Yeah I ran migrations and re-created containers |
|
@JustinBack could you login to the super admin and clear the frontend cache for this account. the option will be available in accounts edit page. |
|
Hi @sojan-official I'm having the same issue after restoring a production database into a fresh updated instalation. After restoring I ran a manual update process an this errors ocurrs during migrations
I'm upgrading from a restored database backup which ran v2.14. What sould I check or fix to run correctly the migrations? Thanks |
Hi @sojan-official I've manage to solve this issue by deleting the index mentioned in the migration error. After deleting I ran again the update process and inboxes are working properly |
|
I had this same issue, fixed my heart attack by running @vishnu-narayanan this is the second time that I've had to manually run the migrations. Is there a setting or something I could check to ensure they are getting properly run when a new update boots up? Thank you |
|
@danielthedifficult Apologies for that 😅 For docker deployment method, one is expected to run the migrations after updating the image.
ref #1: https://www.chatwoot.com/docs/self-hosted/deployment/docker#upgrading |
|
Okay. So it's something I add in my own upgrade and maintenance scripts, and not in the inherent upgrade process you create for a release. Ok! Is there any downside to running the migration command "too many times" - I.e. is it idempotent ? |
|
@danielthedifficult Yes, for Linux/helm installations we handle the migration in the upgrade process. For docker, you will have to run it after every upgrade. And the migrations are idempotent. So no issues if you run it multiple times. |
|
@vishnu-narayanan sorry to keep bugging you. I've read the links you've shared, and they explain perfectly "how" to do the upgrade, but i'm not 100% sur on when to implement it. I have the following script that runs weekly to update the chatwoot service. However the db migration is not getting executed properly. I think it is because the docker exec is running before the rails container is booted, but I'm not clear on how I should go about it. Any tips you have would be welcome. |
|
@danielthedifficult Would adding a |
|
Happy to do that, it's what I was thinking. Do I need to reboot the stack again after a migration ? |
Not needed |
I had this issue after deleting an inbox and this solution worked for me! Thanks @JustinBack |
This worked for me |
Describe the bug
After upgrading to v3 and logging in, my inboxes have disappeard:
The URL after logging in reads
chatwoot.domain.tld/app/accounts/1/dashboard. Now, when I clear the path out of the URL, so it readschatwoot.domain.tld, and I press enter, everything appears to be in perfect working order:At this stage everything seems to be working fine – until after reloading the app manually, when the inboxes will be gone again.
To Reproduce
I really do not know. I upgraded to v3, ran into issues due to node 18, installed 16, recompiled – and this is where I ended up.
Expected behavior
No response
Environment
Linux VM
Cloud Provider
Other [please specify in the description]
Platform
Browser
Operating system
MacOS
Browser and version
Current Chrome
Docker (if applicable)
No response
Additional context
Hosted on Hetzner
The text was updated successfully, but these errors were encountered: