The nginx.conf issue is still occurring, but it looks like there's a new EL9 issue as well - this time a conflict between packages in the Grommunio and EPEL repos.
Attempting dnf upgrade
exits with the following error message:
Error:
Problem: package grommunio-common-27.db4a83f-49.7.x86_64 from @System requires (nginx-module-vts if nginx), but none of the providers can be installed
- cannot install both nginx-mod-vts-0.2.4-1.el9.x86_64 from epel and nginx-mod-vts-0.2.3-13.9.x86_64 from @System
- cannot install both nginx-mod-vts-0.2.3-13.11.x86_64 from grommunio and nginx-mod-vts-0.2.4-1.el9.x86_64 from epel
- cannot install the best update candidate for package nginx-mod-vts-0.2.3-13.9.x86_64
- cannot install the best update candidate for package nginx-2:1.20.1-20.el9.x86_64
- cannot install the best update candidate for package grommunio-common-27.db4a83f-49.7.x86_64
It looks like the EPEL repo has a newer (0.2.4-1) version of nginx-mod-vts than the Grommunio repo (0.2.3-13.11), so it's trying to upgrade to the EPEL version.
The EPEL version's spec file says it provides nginx-mod-vts. The Grommunio version says it provides both nginx-mod-vts and nginx-module-vts. The latter seems to be what grommunio-common specifies as a requirement, judging by the error; so the newer version provided by EPEL doesn't satisfy it.
The documentation says Grommunio requires the EPEL repo. If there's a need for a Grommunio-specific version of the nginx-module-vts package, perhaps it could be named a little differently from the EPEL package to avoid the potential for conflict?