On Fri, Aug 4, 2023 at 8:33 AM Maciej Konigsman <[email protected]> wrote: > > Hello, > > I'm running Guacamole in containers (version 1.5.3). > I can't make work sessions recording. > I enabled recording extension (guacamole-history-recording-storage-1.5.3.jar) > by setting env var RECORDING_SEARCH_PATH in guacamole/guacamole container. > The other recording parameters are not implemented in the start.sh script. > > So, I see that the extension is loaded but the sessions are not recorded. > 16:26:32.049 [localhost-startStop-1] INFO o.a.g.extension.ExtensionModule - > - [recording-storage] "Session Recording Storage" > (/home/guacamole/.guacamole/extensions/guacamole-history-recording-storage-1.5.3.jar) > > I configured the sessions recording with variables and a literal path. Both > don't work. > > > > I even updated the start.sh script to include other recording parameters but > without success. > Here are parameters configured in guacamole.properties file: >> >> recording-search-path: /home/guacamole/recordings >> recording-path: /home/guacamole/recordings >> create-recording-path: true >> recording-include-keys: true > > > Any idea what might be wrong?
It sounds like you're running in Docker containers? There are several things to be aware of with the recording extension, and they become a little more complex when using containers: * The actual recording of the sessions is done by guacd (if you're using containers, the guacamole/guacd) container. So, the guacd container, and the user/UID under which it is running, will need write access to the path where you want to store the recordings. * The display of the recordings in the Guacamole web interface is done by Guacamole Client (the guacamole/guacamole container). So, this container, and the user/UID under which it is running, will need read access to the path where you have stored the recordings. * If you're using containers, you'll need to have a shared location that both the guacamole/guacd and guacamole/guacamole containers can access. This is generally done by specifying a volume for both containers to use, and mounting that volume at the same location on both containers. You'll also need to make sure the security of that volume/location is such that 1) guacd can write files, and 2) guacamole can read the files. -Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
