It took me a while right now to find out that my Virtualmin has the following unexpected behaviour:
When I add new git repositories to a server and grant specific users access to them these users only get access to the repositories in the non-SSL website but not in the SSL version. This is even true for the virtual servers main user.
So while non-SSL config looks like something like this
<VirtualHost 10.0.1.25:80>
# other config...
<Location /git/new-git-repo.git>
Require user secondary-user main-user
</Location>
</VirtualHost>
SSL of the same site looks like this:
<VirtualHost 10.0.1.25:443>
# other config...
<Location /git/new-git-repo.git>
Require user
</Location>
</VirtualHost>
Obviously this is not good if you have only port 443 allowed in your external firewall to prohibit users from accidentally using non SSL connections to this server :p
This behaviour is guaranteed new. I have other repos on the same server and even same website which have all users also in the SSL config. These entries are approximately 1 year or older so somewhen in the past year this "bug" probably came into existence.
I'm not sure if this has something to do with the specific config of my Virtualmin server or if it is a general and reproducible bug of Virtualmin. Maybe you want to investigate this or it is helpful for someone else. In the meantime I'm content with adding users manually to the SSL config.
Best regards.