WalterH WalterH Minutes ago I verified this on an Debian 11 system. Debian 11 have exactly the same layout as the appliance. I assume, you have some configuration files in the wrong location.
weini No definitely not! As I wrote above, I had the old log folder in /etc/nginx/conf.d/grommunio.conf and I´m quite certain that this file was skipped from being updated because I modified it. I now manually adjusted the log paths in this file and it is all good.
WalterH weini Would be great if the packages could be adjusted so that at least dpgk-new files dpgk-new files will only be created, if the configuration file was modified by an admin and a new configuration file exists. In this case, there is now new configuration file for /etc/nginx/conf.d/grommunio.conf.
weini Sure, this was the /etc/nginx/conf.d/grommunio.conf before I modified the log paths manually: include /etc/grommunio-common/nginx/upstreams.d/*.conf; include /usr/share/grommunio-common/nginx/upstreams.d/*.conf; error_log /var/log/grommunio/nginx-error.log; access_log /var/log/grommunio/nginx-access.log; map $http_user_agent $filter_user_agent { default 'unknown'; ~(iPhone|iPad) ios; ~Android android; ~Linux linux; ~(Windows|MSIE|Mozilla) windows; ~Mac macos; ~(FreeBSD|OpenBSD|NetBSD) bsd; ~Outlook outlook; ~Thunderbird thunderbird; } map $http_host $this_host { "" $host; default $http_host; } map $http_x_forwarded_proto $the_scheme { default $http_x_forwarded_proto; "" $scheme; } map $http_x_forwarded_host $the_host { default $http_x_forwarded_host; "" $this_host; } map $http_upgrade $proxy_connection { default upgrade; "" close; } map $request_uri $topdir { ~(?<captured_topdir>^/[a-zA-Z0-9]+/[a-zA-Z0-9]+)[/] $captured_topdir; } server { listen 20080; listen [::]:20080; server_name _; return 301 https://$host$request_uri; include /usr/share/grommunio-common/nginx/traffic_status_params*.conf; } server { server_name _; listen [::]:20443 ssl http2; listen 20443 ssl http2; #use real id and not from apache2 reverse proxy real_ip_header X-Forwarded-For; set_real_ip_from 127.0.0.1; include /etc/grommunio-common/nginx/ssl_*.conf; include /usr/share/grommunio-common/nginx/ssl_params.conf; include /usr/share/grommunio-common/nginx/proxy_params.conf; include /usr/share/grommunio-common/nginx/security.conf; include /usr/share/grommunio-common/nginx/brotli-params*.conf; include /usr/share/grommunio-common/nginx/traffic_status_params*.conf; include /etc/nginx/conf.d/grommunio_custom-*.conf.include; server_tokens off; include /etc/grommunio-common/nginx/locations.d/*.conf; include /usr/share/grommunio-common/nginx/locations.d/*.conf; }
WalterH weini you have an very strange setup! My /etc/nginx/conf.d/grommunio.conf file contains only one line: cat /etc/nginx/conf.d/grommunio.conf include /usr/share/grommunio-common/nginx.conf; I assume, this setup can not be supported.
WalterH Please show the content of /usr/share/grommunio-common/nginx/upstreams.d/ with: ls -l /usr/share/grommunio-common/nginx/upstreams.d/
weini Now I understand! You are fully right, it was me tweaking my setup and causing the issue. When adjusting my configuration, I moved some content from /usr/share/ into the conf files residing in /etc as I needed to do some modification due to my reverse proxy setup in front of nginx. So it is obvious why my configuration was not updated. So sorry for stealing your time and many thanks for pointing me to the issue.
FelixVictor Thanks, @WalterH , for providing this information. Very much appreciated. BTW: why did the developers decide to use non-specfic file names such as nginx-access.log instead of package specific names such as grommunio-access.log? My server is not just running grommunio. Can I rise this issue somewhere?
WalterH This commit clarifies how to enable EWS: https://github.com/grommunio/gromox/commit/6e623631ccc32226fd1019add12e08aba2eb8e17 for testing.
mwilliams WalterH TL;DR: Set ews_beta = 1 in /etc/gromox/ews.cfg. More details will be in the release notes tomorrow. @WalterH : The dependency (php-intl) is in the packages since 2023-11-08, no need anymore to adopt the dependency or manually install as in your article.
THE_FRICKLER Na dann bin ich auf die Release-Notes gespannt. Konnte aber trotzdem nicht warten! Die neuen Icons im "Breeze"- Thema der WEB-GUI sind super. Auf meinem Mac konnte ich ein Apple-Mail Konto einrichten, aber Apple Mail stürzt jedes Mal nach ca. 2 Sekunden ab. Kurz kann man einen gefüllten und aktuellen Posteingang erblicken, dann folgt der Absturz. Das warten wir mal wie gesagt ab!
WalterH THE_FRICKLER I have the same issue, Mail app crashes immediate. macOS Big Sure 11.2.3. I will update to 11.7.10 and test again.
THE_FRICKLER meine ews.cfg hat nur: ews_beta=1 #ews_experimental=1 #ews_log_filter=* #ews_pretty_response=yes #ews_request_logging=yes #ews_response_logging=1 #ews_debug=1 #smtp_server_ip=::1 #smtp_server_port=25
WalterH THE_FRICKLER Development was able to reproduce this issue. I assume the release will be shifted for some days.
WalterH Meine ews.cfg hat mehr Einträge ändert aber nichts. ews_pretty_response=1 ews_request_logging=1 ews_response_logging=1 #ews_debug=1 ews_experimental=1 # ab 10.11.2023: ews_beta=1
491810 The release came out a few days ago and the issue is still there. Or did anyone find a fix/workaround?