Yes, there is a reverse proxy (Apache) setting a number of headers including a "microphone 'none'"...
Guacamole is piggybacking on a primarily Nextcloud server for which the headers were configured. Removing the header enables the microphone so my problem is now solved as a web server configuration problem, not a Guacamole issue. Thanks for the questions leading to uncovering the configuration settings!! On Mon, 2022-11-14 at 20:03 -0800, Michael Jumper wrote: > On Mon, Nov 14, 2022, 7:09 PM Leslie Mann <[email protected]> > wrote: > > I see a number of 'Feature-Policy' unrecognized feature errors and > > a 'AudioContext was not allowed to start' error. > > > > Here is the console log: > > > > Error with Feature-Policy header: Unrecognized feature: > > 'ambient-light-sensor'. > > This is interesting and not a header that Guacamole sets... > > Do you have a reverse proxy in place adding this header? What value > is it setting? Any other headers added by that proxy? > > > > > all.min.js:3 The AudioContext was not allowed to start. It must be resumed > > (or created) after a user gesture on the page. https://goo.gl/7K7WLu > > getAudioContext @ all.min.js:3 > > Guacamole.RawAudioPlayer.getSupportedTypes @ all.min.js:8 > > You can ignore this. This is Guacamole trying to get access to audio > output. The browser will block some of these attempts, particularly > Chrome. It'll keep trying and eventually succeed. In Chrome, that'll > typically happen after some user interaction with the page. > > This probably has no bearing on audio input. > > - Mike > >
