Unable to install Zammad via Docker

[SGN]

Infos:

• Used Zammad version: 6.5.0-101
• Used Zammad installation type: Docker via Portainer with this Documentaion
• Operating system:
  • Host is Debian GNU/Linux 12 (bookworm) x86_64
  • Client is Arch Linux x86_64
• Browser + version: Firefox 140.0.4

Additional Host Infos

• Portainer Version: CE 2.27.6 LTS

Expected behavior:

• Normal, first time configuration of a new Zammad Instance (eg. Enter Admin Userdata, configure FQDN and Logo, Mailconfiguration)

Actual behavior:

• Deployment works fine

• Going to http://localhost:8080 or in my case [$Internal_IP]:8080 works fine
  

  

• Clicking the blue Button for a new System leads to Admincreation mask
  

  

• creating the User will either lead to a red errorbox saying “Internal Server Error” (forgot to screenshot…) or skip the rest of the config going straight to Dashboard an throwing so many 500s that the Background becomes black.
  

  

• clicking ok dozen of times gives you the Dashboard. When trying to access anything it’ll throw another 500
  

  

• reloading the page (F5 or Reloadbutton) results in a different Errorscreen:
  

  

Steps to reproduce the behavior:

• Install and setup Portainer CE 2.27.6 LTS
• Deploy Zammad as documented here
• Create new Instance and enter Admin Userdata

Has anyone seen this behaviour before or can reproduce it?

[MrGeneration]

What does your stacks log say…?

[SGN]

Oh sorry forgot about that…

Logs are clean so far. Nothing suspicious…

init Log has 1 Error

E, [2025-07-20T16:23:04.939215#27-7460] ERROR -- : https://geo.zammad.com/calendar: #<RuntimeError: 0/>

changing settings...

rails is waiting for connections (Edit: this ist kinda sus, isn’t it?)

waiting for init container to finish install or update...

waiting for init container to finish install or update...

waiting for init container to finish install or update...

starting railsserver... with WEB_CONCURRENCY=0

Puma starting in single mode...

* Puma version: 6.6.0 ("Return to Forever")

* Ruby version: ruby 3.2.8 (2025-03-26 revision 13f495dc2c) [x86_64-linux]

*  Min threads: 5

*  Max threads: 30

*  Environment: production

*          PID: 1

I, [2025-07-20T16:21:29.531206#1-7480]  INFO -- : Using memcached as Rails cache store.

I, [2025-07-20T16:21:29.543095#1-7480]  INFO -- : Using the Redis back end for Zammad's web socket session store.

I, [2025-07-20T16:21:29.565989#1-7480]  INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.

I, [2025-07-20T16:21:31.550157#1-7480]  INFO -- : ActionCable is configured to accept requests from (?-mix:https?:\/\/localhost:\d+), http://zammad.example.com.

* Listening on http://[::]:3000

Use Ctrl-C to stop

Postgres drops this Error

2025-07-20 14:21:00.114 UTC [73] ERROR:  relation "settings" does not exist at character 523

2025-07-20 14:21:00.114 UTC [73] STATEMENT:  SELECT a.attname, format_type(a.atttypid, a.atttypmod),

	       pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod,

	       c.collname, col_description(a.attrelid, a.attnum) AS comment,

	       attidentity AS identity,

	       attgenerated as attgenerated

	  FROM pg_attribute a

	  LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum

	  LEFT JOIN pg_type t ON a.atttypid = t.oid

	  LEFT JOIN pg_collation c ON a.attcollation = c.oid AND a.attcollation <> t.typcollation

	 WHERE a.attrelid = '"settings"'::regclass

	   AND a.attnum > 0 AND NOT a.attisdropped

	 ORDER BY a.attnum

	

2025-07-20 14:25:43.844 UTC [56] LOG:  checkpoint starting: time

Elastic is fine, just a bunch of Infos about created indexes

[SGN]

I restarted the Host.. Now I actually get Logs for the railsserver

E, [2025-07-20T16:36:55.659839#1-197300] ERROR -- :   

[01f0fa86-948a-48ed-a2fd-f251aa3eb946] Timeout::ExitException (execution expired):

[01f0fa86-948a-48ed-a2fd-f251aa3eb946]   

[01f0fa86-948a-48ed-a2fd-f251aa3eb946] lib/service/geo_ip/zammad.rb:42:in `rescue in location'

[01f0fa86-948a-48ed-a2fd-f251aa3eb946] lib/service/geo_ip/zammad.rb:17:in `location'

[01f0fa86-948a-48ed-a2fd-f251aa3eb946] lib/service/geo_ip.rb:38:in `location'

[01f0fa86-948a-48ed-a2fd-f251aa3eb946] app/controllers/application_controller/has_user.rb:81:in `session_update'

[01f0fa86-948a-48ed-a2fd-f251aa3eb946] app/controllers/application_controller/handles_transitions.rb:16:in `handle_transaction'

Seems like the lookup times out so it might be dns

[SGN]

It was indeed DNS. After fiixing it, Zammad worked again