Changing FQDN in Zammad leads to 404

[shakalandy]

Infos:

• Used Zammad version: 6.3.1-1727070698.30e843fa.focal
• Used Zammad installation type: Package
• Operating system: Ubuntu 20.04.6 LTS
• Browser + version: Chrome

Expected behavior:

• Zammad FQDN Change possible

Actual behavior:

• Zammad FQDN Change results in 404 of nginx. URL was changed in " settings > System > Fully Qualified Domain Name" as described here: Rename Zammad server and change url - #3

Steps to reproduce the behavior:

• change the FQDN to a new domain (in that case a new sub-domain) - setting.fqdn
• restart zammad
• restart nginx

Zammad still works under the old Domain and delivers a 404 on the new domain.

Anybody had this problem?
Is there any cache working that still has the FQDN setting?

Thanks!

[datenschuft]

did you change (or append) the new server_name in the nginx-configuration ?

[shakalandy]

yes sure, nginx routes the request into the correct vhost, but the application seems not to feel itself responsible for it.

Could the setting be cached somewhere?
How can I check which setting is active in Zammad?