No onboarding installation shown after deploying chatwoot

[justrdk]

No onboarding installation shown after deploying chatwoot

[linear]

PR-1008 No onboarding installation shown after deploying chatwoot

[vishnu-narayanan]

@justrdk Have you been trying out the installation multiple times? Installation via helm chart provisions redis/postgres which uses persistent volumes. These volumes will persist even if you delete the helm installation and install again. Chatwoot relies on key in redis to show the onboarding page.

Could you try deleting the helm installation along with persistent volumes for both postgres and redis and try a fresh install?

[gkp1]

Having the same issue. I just installed using docker on ubuntu 22.. Main route redirects me automatically to login page instead of onboarding. Can't create first user, pruned everything from docker with system prune and volume prune before, so it is not caused by previous installations.

It does not redirect me to installation/onboarding, and the onboarding route directs me to login page. I am testing currently on serverIp:port/installation/onboarding --> serverip:port/app/login. The only thing different from the guide is that I set port '3000:3000' instead of '127.0.0.1:3000:3000' to enable testing the app with the server ip serverIP:port. But the guide itself tells me to do this if I want to test so I guess it wouldn't have caused that issue.

Not sure if it only works if I configure SSL, I will point my domain to it and point nginx and report back here if it fixes this issue (I don't think it will)

I enabled user creation and created a user through sign up.

Docker Compose version v2.25.0
Docker version 26.0.0, build 2ae903e

[iannortnau]

We were able to solve this problem by running this command directly in the Redis console.

Redis::Alfred.set(Redis::Alfred::CHATWOOT_INSTALLATION_ONBOARDING, true)

[justrdk]

@justrdk Have you been trying out the installation multiple times? Installation via helm chart provisions redis/postgres which uses persistent volumes. These volumes will persist even if you delete the helm installation and install again. Chatwoot relies on key in redis to show the onboarding page.

Could you try deleting the helm installation along with persistent volumes for both postgres and redis and try a fresh install?

Same issue for me, everytime I provisioned a new chatwoot on cluster I don't get the onboarding screen.

[vishnu-narayanan]

@justrdk Have you been trying out the installation multiple times? Installation via helm chart provisions redis/postgres which uses persistent volumes. These volumes will persist even if you delete the helm installation and install again. Chatwoot relies on key in redis to show the onboarding page.

Could you try deleting the helm installation along with persistent volumes for both postgres and redis and try a fresh install?

As @iannortnau shared, running Redis::Alfred.set(Redis::Alfred::CHATWOOT_INSTALLATION_ONBOARDING, true) on redis console should bring up onboarding screen.

[justrdk]

@vishnu-narayanan I deleted pvcs for both postgres and redis and did a fresh install and I still don't get the onboarding screen. I checked the database as well and there are no users stored in it at the time I first load the application.

[vishnu-narayanan]

@justrdk That should have worked. You could try the redis workaround for now.

After deploying the chart, once the pods are up ssh into the redis pod. Access the redis-cli and run Redis::Alfred.set(Redis::Alfred::CHATWOOT_INSTALLATION_ONBOARDING, true)

Then try loading https://your-installation-url.tld