How to configure DS Gateway Recording?

Hello,

Yes, we have deprecated our previous recording server and moved that functionnality with our Devotlutions Gateway. It is something new in the last version. We are still working on the documentation and this is why we don't have an easy link yet in the message. You can have a look on that KB-Configure the Recording Server You will see in that KB that the first step is to install a Devolutions Gateway and a documentation can be found here KB-Devolutions Gateway configuration with Devolutions Server

Let us know if you need assistance in any steps, it will be a pleasure to help you.

Best regards,

I checked those KBs but I can't find anything about recording settings in Devolutions Gateway. It's just about install but you can't even set recording path.
I think there must be something but I can't find anything!

Hello,

There is nothing to configure on the Devolutions Gateway after installation. The recording feature will be enabled. The recording will be saved in %programdata%\Devolutions\Gateway\recordings by default. You can't change it during the installation. The only way for now is manually changed the file %programdata%\Devolutions\Gateway\gateway.json and add a line `RecordingPath: "<your_path>"`. You will have to restart the Devolutions Server service, but after that, your recording should be saved there. We have a ticket on our side to improve Devolutions Console to update that information via the UI.

Don't hesitate if you need more help

Best regards,

Hi,
After adding "RecordingPath": "D:\Records" into gateway.json, DevolutionsGateway service could not start and I received this Error 1067: The process terminated unexpectedly.
The path is exist and LocalSystem has full access.

Following error showed up in Application Events.
Faulting application name: DevolutionsGateway.exe, version: 2023.2.3.0, time stamp: 0x64dbc803
Faulting module name: DevolutionsGateway.exe, version: 2023.2.3.0, time stamp: 0x64dbc803
Exception code: 0xc0000409
Fault offset: 0x0000000000c18301
Faulting process id: 0x1480
Faulting application start time: 0x01d9dd51f5edd298
Faulting application path: C:\Program Files\Devolutions\Gateway\DevolutionsGateway.exe
Faulting module path: C:\Program Files\Devolutions\Gateway\DevolutionsGateway.exe

Hi,

If you don't add the "RecordingPath" property in the file, does it work ? I would suggest you to make it work first in the default folder than work to move that folder. Could you send me your gateway.json file via a private message ? And please attach the log file as well (gateway.<date>.log), it could help me to understand why your gateway doesn't start.

Best regards,

It works before adding "RecordingPath". After adding the parameter, service can't start and there is no new gateway.<date>.log

Working Config:

{
    "Id":  "***********************",
    "Hostname":  "*************",
    "ProvisionerPublicKeyFile":  "provisioner.pem",

    "Listeners":  [
                      {
                          "InternalUrl":  "http://*:7171",
                          "ExternalUrl":  "https://*"
                      },
                      {
                          "InternalUrl":  "tcp://*:8181",
                          "ExternalUrl":  "tcp://*:8181"
                      }
                  ]
}

Not Working:

{
    "Id":  "***********************",
    "Hostname":  "*************",
    "ProvisionerPublicKeyFile":  "provisioner.pem",

    "Listeners":  [
                      {
                          "InternalUrl":  "http://*:7171",
                          "ExternalUrl":  "https://*"
                      },
                      {
                          "InternalUrl":  "tcp://*:8181",
                          "ExternalUrl":  "tcp://*:8181"
                      }
                  ],
"RecordingPath": "D:\Records"
}

Windows Application Event Log:

Faulting application name: DevolutionsGateway.exe, version: 2023.2.3.0, time stamp: 0x64dbc803
Faulting module name: DevolutionsGateway.exe, version: 2023.2.3.0, time stamp: 0x64dbc803
Exception code: 0xc0000409
Fault offset: 0x0000000000c18301
Faulting process id: 0x1e60
Faulting application start time: 0x01d9e480b9c4b89c
Faulting application path: C:\Program Files\Devolutions\Gateway\DevolutionsGateway.exe
Faulting module path: C:\Program Files\Devolutions\Gateway\DevolutionsGateway.exe
Report Id: 1dbd6319-4458-4a3f-a5e2-357908cd2178
Faulting package full name: 
Faulting package-relative application ID: 

Gateway Log in working state (Default path without "RecordingPath"):

2023-09-11T07:22:55.408843Z  INFO devolutions_gateway::service: version="2023.2.3"
2023-09-11T07:22:55.408924Z  INFO devolutions_gateway: devolutions-gateway service started
2023-09-11T07:22:55.408929Z  INFO devolutions_gateway: args: ["DevolutionsGateway"]
2023-09-11T07:22:55.409193Z  INFO devolutions_gateway::service: Reading JRL file from disk (path: C:\ProgramData\Devolutions\Gateway\jrl.json)
2023-09-11T07:22:55.409335Z  INFO devolutions_gateway::listener: Initiating listener… url=http://[::]:7171/
2023-09-11T07:22:55.413573Z  INFO devolutions_gateway::listener: Listener started successfully kind=Http addr=[::]:7171
2023-09-11T07:22:55.413606Z  INFO devolutions_gateway::listener: Initiating listener… url=http://0.0.0.0:7171/
2023-09-11T07:22:55.413681Z  INFO devolutions_gateway::listener: Listener started successfully kind=Http addr=0.0.0.0:7171
2023-09-11T07:22:55.413689Z  INFO devolutions_gateway::listener: Initiating listener… url=tcp://[::]:8181
2023-09-11T07:22:55.413757Z  INFO devolutions_gateway::listener: Listener started successfully kind=Tcp addr=[::]:8181
2023-09-11T07:22:55.413763Z  INFO devolutions_gateway::listener: Initiating listener… url=tcp://0.0.0.0:8181
2023-09-11T07:22:55.413815Z  INFO devolutions_gateway::listener: Listener started successfully kind=Tcp addr=0.0.0.0:8181

Hey Hakimi

Since the config is a json file you need to escape backslashes:
"RecordingPath": "D:\\Records"

Best Regards,
Andreas

Hey Hakimi

Since the config is a json file you need to escape backslashes:
"RecordingPath": "D:\\Records"

Best Regards,
Andreas

It's my fault. Your right. Problem resolved by escaping backslash.
Thank you Andreas.

Hi,

Yeah, backslashes have to be escaped. For information, you can also use slash and this one doesn't need to be escaped.

Best regards,