503 Error (Service Unavailable) after new installation

Infos:

  • Used Zammad version:
  • Used Zammad installation type: docker-compose
  • Operating system: Debian 11.11
  • Browser + version: Chrome 128.0.6613.138

Expected behavior:

  • Installed new setup

Actual behavior:

Steps to reproduce the behavior:

Addendum to the post:

Had a similar issue, check the Log of the Nginx container if it started up correctly or if it stuck in a wait for finish of init container loop

Thanks for the tip where can I find this log file?

No offense, but if you don’t know on how to view the log output of docker compose, you may want to consider a package installation instead. Docker administration can be challenging.

docker compose logs and docker compose logs -f is your friend.

If you’re using Portainer directly in the container, otherwise you may have to take a look to the docs, since I don’t know exactly.
I guess the easiest way would be logging into the container and take a look on the files in /var/logs/

Yes, there is a folder “zammad” and there are also two files “production.log” and “searchindex-rebuild.log” in there.

Here is the link to the log file.

In the " docker compose logs" I only see information and no errors or warnings …

You’re using the Setup from the zammad-docker-compose repo, right?

This seems to be the log of the scheduler-container.
More interesting would be the output of the init container and the nginx container.

I installed the compose stack via Portainer (what I guess would be a good way for you too, since it makes the handling a bit easier).
For me it’s docker logs zammadgit_zammad-nginx-1 where “zammadgit” is the stack-prefix.

Maybe this helps you

Yes, that’s right, I use the zammad-docker-compose repo.
Thanks for the information.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.