Hi Stefan,
The certificate feature included in Erlang 25 only allows Erlang applications to fetch CA certificates from the operating system. In the case of the RabbitMQ management interface, you still have to provide a server certificate and key from a file, so there isn't really a benefit to fetching the CA cert from the windows cert store.
If your browser redirects you from the http:// to the https:// scheme, something must have set up that redirect outside of RabbitMQ. If you only had https configured for the RabbitMQ management plugin, visiting
http://{{MyServer}}:15672/#/queues would have resulted in a refused connection error.
The "best" work around in your case would be to automate the export of the RabbitMQ-specific certificates from the Windows cert store whenever they are updated. Exporting to PFX then converting to pem format would be required:
Export to PFX:
Convert:
Or, just don't use the Windows cert store for RabbitMQ specific certificates.
Thanks,
Luke