I've hosted my own websites alongside OpenMediaVault for some time now, first using the nginx plugin on OMV4 and then with plain config files on OMV5. I'm now looking at v6 (great job by the way, very slick) and although I've got things working there I'm a bit puzzled by the differences I'm seeing. These differences are not just between v6 and v5, but also between two v6 installs that I thought I had configured similarly. Presumably there's more going on behind the scenes than I realised.
In OMV5 the openmediavault-webgui config file contains:
listen [::]:80 default_server ipv6only=off;
listen [::]:443 default_server ipv6only=off ssl deferred;
These entries are recreated if I disable/enable SSL via the web UI so I assume they don't include any manual hacks that I might have made and forgotten about. My sites work fine alongside the OMV UI with these settings, with everything listening on ports 80/443 but different hostnames set in the server blocks.
On my OMV6 installation I had these entries:
listen *:80 default_server;
listen [::]:80 default_server;
listen *:443 default_server ssl deferred;
listen [::]:443 default_server ssl deferred;
My sites aren't served with these settings - the OMV web GUI is served regardless of which hostname is used in the requests. If I change to the v5 settings (removing the ipv4 lines and adding ipv6only=off to the ipv6 lines) everything works as before. As the comment in the file makes clear though, such changes can be overwritten, so presumably this is not a good solution. I created another instance of OMV6 to have a poke around with, and was surprised to see that it has different settings:
listen 80 default_server;
listen 443 default_server ssl deferred;
... even though I tried (but presumably failed) to keep both instances the same. Presumably there's something else involved in determining the settings to use. Is there some way I could modify those rules to get OMV6 to use the v5 style settings?