Infos:
- Used Zammad version: 6.3.1
- Used Zammad installation type: Source
- Operating system: Raspberry Pi OS 12
- Browser + version: any
Expected behavior:
- I want the web service to start automatically when the system starts.
Actual behavior:
Hello Zammad community,
I really hope that someone can help me. My installation of Zmmad was done via the source installation: Source Installation — Zammad System Documentation documentation
After restarting my Raspberry, Zammad is not accessible, although the services are running.
##########################
● zammad.service - Zammad
Loaded: loaded (/etc/systemd/system/zammad.service; enabled; preset: enabled)
Active: active (running) since Fri 2024-10-18 21:42:55 CEST; 21min ago Main PID: 878 (sleep) Tasks: 1 (limit: 9139) CPU: 3ms CGroup: /system.slice/zammad.service └─878 /bin/sleep infinity
● zammad-web.service - Zammad Web Server Loaded: loaded (/etc/systemd/system/zammad-web.service; enabled; preset: enabled) Active: (running) since Fri 2024-10-18 22:05:27 CEST; 1s ago
Main PID: 213729 (ruby)
Tasks: 1 (limit: 9139)
CPU: 1.891s
CGroup: /system.slice/zammad-web.service
└─213729 “script/rails server -b 127.0.0.1 -p 3000”
##########################
I have to manually log in as user “zammad” in the terminal and then run the command “rails s -b 127.0.0.1 -p 3000 -d” so that I can actually access Zammad. If I don’t run this command manually, I only get a 503 error when I call the Zammad domain.
Does anyone have any idea how I can fix the error so that Zammad is actually available immediately when my system is restarted?
Thank you very much for any suggestions.