TLDR lauuu faces issues while setting up Chatwoot. v_shnu provides troubleshooting strategies such as commenting out a line in the script, passing a variable to the script, and creating a new VM, but the problems persist.
hey lauuu , what does it say at the end?
v_shnu thanks. I see this: WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... postgresql is already the newest version (12+214ubuntu0.1). postgresql-contrib is already the newest version (12+214ubuntu0.1). redis-server is already the newest version (5:5.0.7-2ubuntu0.1). The following packages were automatically installed and are no longer required: linux-headers-5.4.0-26 linux-headers-5.4.0-26-generic linux-image-5.4.0-26-generic linux-modules-5.4.0-26-generic linux-modules-extra-5.4.0-26-generic Use 'apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. adduser: The user `chatwoot' already exists.
Looks like you re-run the script? Did it fail before?
This is now failing as the user chatwoot is already present
could you comment out line 219 in the script and try again? the line that says the following ```219 configure_rvm```
it worked. Thanks a lot!
hi v_shnu I have tried to uninstall chatwoot so that I could install it again to set up the domain properly
when I try to run the script it fails and this is what the log shows
[5/5] Building fresh packages...
Done in 7.36s.
Everything's up-to-date. Nothing to do
Database 'chatwoot_production' already exists
rake aborted!
ActiveRecord::ProtectedEnvironmentError: You are attempting to run a destructive action against your 'production' database.
If you are sure you want to continue, run the same command with the environment variable:
DISABLE_DATABASE_ENVIRONMENT_CHECK=1
/usr/local/rvm/gems/ruby-3.0.4/gems/activerecord-6.1.5.1/lib/active_record/tasks/database_tasks.rb:63:in `check_protected_environments!'
/usr/local/rvm/gems/ruby-3.0.4/gems/activerecord-6.1.5.1/lib/active_record/railties/databases.rake:18:in `block (2 levels) in
could you help?
This is due to production chatwoot database being already created.
`DISABLE_DATABASE_ENVIRONMENT_CHECK=1` pass this to script when rerunning to override this
should place DISABLE_DATABASE_ENVIRONMENT_CHECK=1 inside install.sh at a specific line?
```DISABLE_DATABASE_ENVIRONMENT_CHECK=1 ./install.sh master```
you can pass variables to a process/script like this
If you are installing/uninstalling multiple times, I would recommend spinning up a new instance and doing it fresh. Will be easier.
it didn't work. I'll try creating a new VM. Thanks!
sounds good
v_shnu
sorry to bother you again. I've created a new machine, but I'm getting the same error
warning " > @storybook/[email protected]" has unmet peer dependency "css-loader@*".
warning "@storybook/vue > [email protected]" has unmet peer dependency "typescript@*".
warning "@storybook/vue > vue-docgen-api > @vue/[email protected]" has incorrect peer dependency "[email protected]".
warning " > [email protected]" has unmet peer dependency "webpack@>=1.11.0".
warning " > [email protected]" has unmet peer dependency "webpack@^4.0.0 || ^5.0.0".
[5/5] Building fresh packages...
Done in 7.57s.
Everything's up-to-date. Nothing to do
Database 'chatwoot_production' already exists
rake aborted!
ActiveRecord::ProtectedEnvironmentError: You are attempting to run a destructive action against your 'production' database.
If you are sure you want to continue, run the same command with the environment variable:
DISABLE_DATABASE_ENVIRONMENT_CHECK=1
/usr/local/rvm/gems/ruby-3.0.4/gems/activerecord-6.1.5.1/lib/active_record/tasks/database_tasks.rb:63:in `check_protected_environments!'
/usr/local/rvm/gems/ruby-3.0.4/gems/activerecord-6.1.5.1/lib/active_record/railties/databases.rake:18:in `block (2 levels) in
I tried DISABLE_DATABASE_ENVIRONMENT_CHECK=1 ./install.sh master
but it's the same
I restarted the chatwoot process and could access via port 3000
but, I wanted to set the dns domain and ssl, which doesn't look like it got done properly
lauuu
Thu, 23 Jun 2022 18:43:03 UTCthat setup log is pretty large. What exactly can i look for?