Hi kunmyt,
In a similar setup, I found in the file /opt/zimbra/conf/nginx/includes/nginx.conf.zmlookup a line like the following:
zm_lookup_handlers http://some_ip_address:7072/service/extension/nginx-lookup http://another_ip_address:7072/service/extension/nginx-lookup;
When I changed this to the following:
zm_lookup_handlers https://mail_store1_dns_cert_name:7072/service/extension/nginx-lookup https://mail_store2_dns_cert_name:7072/service/extension/nginx-lookup;
and then:
zmproxyctl reload
I can login using a separate webmail/proxy
I am not sure if I can change this permanently or otherwise I have to perform this fix with every zimbra restart or server reboot.
I have an oss installation 8.8.15 with Zimbra packages. Not a custom build.
I noticed the same "sent invalid header in response" error message in nginx.log
In a similar setup, I found in the file /opt/zimbra/conf/nginx/includes/nginx.conf.zmlookup a line like the following:
zm_lookup_handlers http://some_ip_address:7072/service/extension/nginx-lookup http://another_ip_address:7072/service/extension/nginx-lookup;
When I changed this to the following:
zm_lookup_handlers https://mail_store1_dns_cert_name:7072/service/extension/nginx-lookup https://mail_store2_dns_cert_name:7072/service/extension/nginx-lookup;
and then:
zmproxyctl reload
I can login using a separate webmail/proxy
I am not sure if I can change this permanently or otherwise I have to perform this fix with every zimbra restart or server reboot.
I have an oss installation 8.8.15 with Zimbra packages. Not a custom build.
I noticed the same "sent invalid header in response" error message in nginx.log
Statistics: Posted by gbz — Fri Mar 07, 2025 3:27 pm