Okay thanks, it’s not there.
The developers of the software indicate its probably not an HTTPS issue after all (they acknowledge a poorly worded error message) and more likely an issue of the iframe not granting the feature policy to request access to the microphone (adding allow=“microphone *” did not help.
This is hardly critical I am more curious than anything.