Chatwoot Docker not starting after unexpected restart

[one-juru]

Chatwoot Docker outputs: Switch to inspect mode.

I restarted my server yesterday, to apply the newest Updates, and the chatwoot base container wasn't starting again and just outputting the lines "Switch to inspect mode." I tried starting it with portainer and via the command line.

To Reproduce

Steps to reproduce the behavior:

1. Restart Server
2. Try to start docker containers with portainer or command line
3. realize that the docker container instantly stops and outputs "Switch to inspect mode."

Expected behavior

Docker container should start and open webinterface

Server logs
"Switch to inspect mode." (not more)

Environment

Server: Ubuntu 20.04 with Docker and Portainer
Installed like described in the docs.

[vishnu-narayanan]

@one-juru could you please update to v1.21.1 and see if the issue persists ?
#3228

[one-juru]

I updated, but it still won't start. I'm sure that a clean installation would solve the problem, but I don't want to set it up again :(

[vishnu-narayanan]

Yeah, it shouldn't require a reinstall. Is it something related to portainer ? Could you ssh in and see if it works with docker-compose up from the cli ?

[one-juru]

I had the same Idea, so I already tried deleting all containers and deploying them from the composer file with ssh, but it's still the same result

[one-juru]

I deleted every container and every persistent storage space, and tried to set it up again - but it still fails with the same error message and stops the container. Resetting the entire VPS would definitely solve that problem (tested on another fresh Ubuntu vm), but I wouldn't like to do that. Do you have any other idea?

[one-juru]

EDIT: It seems that the web interface works, even though the chatwoot_base container is stopped and exited with code 0 ("switch to inspect mode").

Do we even need that container? The installation seems to work fine without it...

[sojan-official]

@one-juru the base container is only required to build the web and worker containers.

[one-juru]

Okay, thank you, my issue was fixed with a reinstall of chatwoot and the last edit I did was intended behavior so my issue is fixed.

I cant really explain the root cause but it was probably another program on the server that did something. I will close this issue now since the support chat is working again and will keep a closer look on my server.

Thank you :)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.