Comment 16 for bug 1893906

I checked, even adding [global] before the includes (when keeping them later in the config) will make them work. As then the include is "bInGlobalSection" and followed.

The workaround for current users would be to place includes into the global section if it is intended that the includes shall be able to set global config (like the one used for clients).

IMHO that is an upstream bug - includes should always be processed (as they could add the new sections), but that is a report to be done after this is confirmed here.

@Sebastian - could you check if your "include" statements are themselves in the [global] section. If not the clients will not have a chance to reach them. In that case move the includes there OR re-open the [global] section before the include.
Does that get your "client min protocol" set as you'd expect then?