Recording Server setup

Hello Robin,

Thank you for contacting us regarding this matter.

Regarding the password server, that is the old name for Devolutions Server, it should not be displayed anymore. I will open an internal request to have it modified.

As for the server name during the installation, it is not the URL of your Devolutions Server, it is the actual name of the server hosting the recording server. You can click the Get Hostname button to get the name of the server. If it is domain joined, make sur to put the full name, including the domain as well.

You should not have to configure anything on the web page once the installation is completed, it will be filled out automatically.

As for accessing the recordings, they will be available from RDM or from the web interface, under the logs of the session. You will see a blue downward arrow in the Recording column to download the resulting webm file.

Let us know if you have any issues or need assistance, we can always have a session if needed.

Best regards,

Thanks for clarification Richard. So I did a new install and got the following summary:

---
Recording Server
Host: WIN1-MIA1
Port: 50505
Installation Path: C:\Recording_Server
Recording Output Path: C:\Recording_Server

Source: Download from the web (2022.2.8.0)

Recording Service Account
Account type: LocalService

Password Server
URL: https://devolutionserver.mydomain.com
----

So this seems to have worked, but when a remote user now tries to start an SSH session to any system in this data source , it closes with: "Unable to connect to the recording server". I opened port 50505 to be accessible and can confirm it responds by doing "telnet devolutionserver.mydomain.com 50505" from that same remote PC.

When I change Host: from WIN1-MIA1 to devolutionserver.mydomain.com in the web interface recording server settings. That error does no longer appear and I get a red dot in the title bar of the session. Unfortunately there is no recording or blue arrow in the logfile after I'll close it out on the remote users PC.

Hello Robin,

Could you uninstall the Recording Server again, and make a few modifications:

If your server is domain joined, make sure you use the FQDN (Host: WIN1-MIA1), since this, in addition to the port, is what is used to connect to the recording server.

Can you also put different paths for the installation and the output folder?

Finally, try to use the Local System account instead of Local Service, to see if it helps.

If you still cannot connect after, can you provide us with the Devolutions Server console version you are using (bottom left), as well as the version of the Devolutions Server instance and RDM?

Best regards,

Hi Richard, we are getting closer. The recordings are being made and stored in the separate folder and I can go grab the files there to replay it. However, the recordings are not accessible in Logs of RDM, nor on the web application and simply show a checkmark.



Also, is it possible that recordings only work on the Windows version of RDM? When I connect from a Mac, it does not drop a file into the output folder.

Hello Robin,

You're right we're making progress...
If I'm not mistaken, it seems like the Processor is not able to "tell" the DVLS that the recording is now available.
This should be done by a web request to DVLS. Maybe we could find traces of the issue in the Processor Logs, which is enabled in the log4Net.config of the processor App folder.
Open the file with any text editor, set the value for the File attribute, with double "\"
for instance :
<file value="C:\\Program Files (x86)\\Devolutions\\RecServer\\processor\\processor.log" />
And the level to "All"
<root>
<level value="ALL" />
...

We'll address the Mac situation afterward.

Best regards,

Hi Alex, enabled the logging and it recorded the following lines:

2022-08-23 15:36:58,833 ERROR Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Error: 
 2022-08-23 15:36:58,838 ERROR Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Detail: 
 2022-08-23 15:36:58,838 ERROR Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Unable to save recording info to DPS

Hello Alex, let me ask you this: when the recording server is hosted on a FQDN and the RDM needs to connect to it over the internet, what ports would need to be accessible in order to make this work?

Thanks,
Robin

Hello,

Is it possible for you to enable the log debug information on the server (https://helpserver.devolutions.net/webinterface_logging.html) , reproduce the issue and send us your server logs (https://kb.devolutions.net/dvls_viewdatasourcelogs.html)?

Best regards,

Sorry to respond so late. I tried what you suggested and set the checkmark for "log debug information" . After that I ran a connection and was looking for a log in reports, but can't find anything. There are only two lines:

DateTitleUsernameType9/2/2022 9:16 PMLogUtils.LogFileNameDPS ServerInformation
9/2/2022 9:16 PMApplication_StartDPS ServerInformation

Hello,

After a session is completed, it will send a task to the processor service to create the webm file, and once completed, it send a web request to the Devolutions Server (DVLS) to notify it the file is completed and ready for download.

In your case, it seems it is that last step that is failing, the processor service is unable to communicate to DVLS. Can you make sure the outgoing port 443 is open from that server?

If the port is open, I would recommend having a support session in order to review your configuration and troubleshoot the issue. Simply write to service@devolutions.net and mention this thread.

Best regards,

Hello,

We found the issue with Robin's configuration; it was caused by an extra / in the DPSURL in the processor.cfg file. By removing the / and restarting the recording collector and processor services, the file was available for download from RDM once the recording is completed.

Best regards,

Unfortunately, I have to pick this up again. -sorry! :(

The recording server is recording fine, and it also uploads those recordings to the remote Devolutions Server Instance. They can be accessed in c:\devolution_output of that server and the RDM software on user's computers also show a green checkmark in the " Recording" column of the logs. The only thing missing is the download link and icon, so users are not able to get a recording.

We had the missing icon earlier in the Mac version of RDM, but it was just a visual problem (link was still there, just hidden because no icon has been displayed). Now we don't have the download link in the Mac or Windows version.

Hello,

Could you make sure that the Application Pool identity (in IIS) can reach the output folder of your recordings (c:\devolution_output)? If it is installed on the same server that is hosting your Devolutions Server, go to IIS > Application Pool > Advanced Settings, of the Devolutions Server app pool, and verify what identity is used.

Then, go to c:\devolution_output and make sure that account has the rights to read from it.

Also, in the Processor.cfg file, make sure the DPSURL is still correct (no / or space at the end)


Then, stop both the Collector and Processor services, and start them back (collector first). Reconnect to your data source in RDM (File > Data Sources > OK) and then verify if you have the blue download button.

Best regards,

Hi Richard, did all that but unfortunately it didn't change anything.

Thanks,
Robin

Hello,

Is it possible you are using a self-signed certificate on your Devolutions Server, or a certificate that is not trusted? An issue as been discovered recently that prevents RDM and the web interface to download the recordings that looks similar to ours.

To be certain, you can enable the logging in log4Net.config (I believe we already enabled it during our session). You will need to change the line 4 and 13:

<file value="C:\\path\\collector.log" />
<level value="ALL" />

Stop the collector and processor service, start them again, and try to do a recording. Go in the log file and it should show an SSL error if the above is the cause. If so, the engineering team is investigating the issue already.

If this is not the case, can you verify if there are any error in the log file and provide it to us? You can also send the log file to service@devolutions.net if you prefer.

Best regards,

Hi Richard, the certificate is a real one from Geotrust and working over the internet (SSL Checker). We also saw those download icons not too long ago, but it appears something has changed since.

With logging level set to ALL in the collectors log4net, I get:

2022-10-30 17:55:25,008  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: Awaiting new connection...
 2022-10-30 17:55:25,018  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received metadata ConnectionID.
 2022-10-30 17:55:25,018  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received metadata RepositoryID.
 2022-10-30 17:55:25,018  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received metadata ConnectionLogID.
 2022-10-30 17:55:25,018  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received metadata ConnectionType.
 2022-10-30 17:55:25,039  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 187.
 2022-10-30 17:55:26,516  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 43.
 2022-10-30 17:55:26,641  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 42.
 2022-10-30 17:55:26,800  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 42.
 2022-10-30 17:55:26,926  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 43.
 2022-10-30 17:55:26,944  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 53.
 2022-10-30 17:55:27,090  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 1076.
 2022-10-30 17:55:27,101  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 666.
 2022-10-30 17:55:28,399  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 48.
 2022-10-30 17:55:28,452  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 1980.
 2022-10-30 17:55:30,017  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received KeepAlive.
 2022-10-30 17:55:30,256  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 70.
 2022-10-30 17:55:30,259  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 67.
 2022-10-30 17:55:31,556  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 43.
 2022-10-30 17:55:31,782  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 42.
 2022-10-30 17:55:31,908  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 42.
 2022-10-30 17:55:32,110  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 42.
 2022-10-30 17:55:32,317  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received payload of size 51.
 2022-10-30 17:55:32,396  INFO Devolutions.Recording.CollectionService.? [?] - MESSAGE: [e0de765f-0a62-4e53-9492-a404f7c5dff4] Received end of stream.

But the processors log with it being set to ALL, looks more revealing:

2022-10-30 17:55:34,455  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: New file, C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.rfi, detected.
 2022-10-30 17:55:34,455  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Waiting for processor to be available...
 2022-10-30 17:55:34,455  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Processing C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap
 2022-10-30 17:55:34,456  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Initialize C:\Devolution_Output\e0de765f-0a62-4e53-9492-a404f7c5dff4.trp
 2022-10-30 17:55:34,456  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 197).
 2022-10-30 17:55:34,456  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 171).
 2022-10-30 17:55:34,457  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:0 length:197
 2022-10-30 17:55:34,458  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 9).
 2022-10-30 17:55:34,458  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 27).
 2022-10-30 17:55:34,458  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:197 length:9
 2022-10-30 17:55:34,459  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 9).
 2022-10-30 17:55:34,459  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 26).
 2022-10-30 17:55:34,459  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:206 length:9
 2022-10-30 17:55:34,460  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 9).
 2022-10-30 17:55:34,460  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 26).
 2022-10-30 17:55:34,461  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:215 length:9
 2022-10-30 17:55:34,461  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 10).
 2022-10-30 17:55:34,461  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 27).
 2022-10-30 17:55:34,461  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:224 length:10
 2022-10-30 17:55:34,462  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 21).
 2022-10-30 17:55:34,462  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 37).
 2022-10-30 17:55:34,462  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:234 length:21
 2022-10-30 17:55:34,463  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 4103).
 2022-10-30 17:55:34,463  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 1060).
 2022-10-30 17:55:34,463  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:255 length:4103
 2022-10-30 17:55:34,464  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 2919).
 2022-10-30 17:55:34,464  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 650).
 2022-10-30 17:55:34,465  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:4358 length:2919
 2022-10-30 17:55:34,465  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 14).
 2022-10-30 17:55:34,465  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 32).
 2022-10-30 17:55:34,465  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:7277 length:14
 2022-10-30 17:55:34,466  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 7018).
 2022-10-30 17:55:34,466  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 1964).
 2022-10-30 17:55:34,467  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:7291 length:7018
 2022-10-30 17:55:34,467  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 39).
 2022-10-30 17:55:34,467  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 54).
 2022-10-30 17:55:34,467  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:14309 length:39
 2022-10-30 17:55:34,467  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 43).
 2022-10-30 17:55:34,467  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 51).
 2022-10-30 17:55:34,468  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:14348 length:43
 2022-10-30 17:55:34,468  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 9).
 2022-10-30 17:55:34,468  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 27).
 2022-10-30 17:55:34,468  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:14391 length:9
 2022-10-30 17:55:34,468  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 9).
 2022-10-30 17:55:34,468  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 26).
 2022-10-30 17:55:34,469  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:14400 length:9
 2022-10-30 17:55:34,469  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 9).
 2022-10-30 17:55:34,469  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 26).
 2022-10-30 17:55:34,469  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:14409 length:9
 2022-10-30 17:55:34,470  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 9).
 2022-10-30 17:55:34,470  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 26).
 2022-10-30 17:55:34,470  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:14418 length:9
 2022-10-30 17:55:34,470  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reading next record (size: 18).
 2022-10-30 17:55:34,470  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Record appears to be zipped (zipped size: 35).
 2022-10-30 17:55:34,470  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Writing start:14427 length:18
 2022-10-30 17:55:34,471  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: [C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap] Reached end of file.
 2022-10-30 17:55:34,471  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Saving recording to DPS
 2022-10-30 17:55:34,489 ERROR Devolutions.Processor.ProcessorService.? [?] - MESSAGE: System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
 ---> System.Security.Authentication.AuthenticationException: The remote certificate was rejected by the provided RemoteCertificateValidationCallback.
   at System.Net.Security.SslStream.SendAuthResetSignal(ProtocolToken message, ExceptionDispatchInfo exception)
   at System.Net.Security.SslStream.CompleteHandshake(SslAuthenticationOptions sslAuthenticationOptions)
   at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
   at System.Net.Http.ConnectHelper.EstablishSslConnectionAsync(SslClientAuthenticationOptions sslOptions, HttpRequestMessage request, Boolean async, Stream stream, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at Devolutions.Server.ApiWrapper.RDMSWebClient.RunSynchronous[T](Task`1 task) in C:\Dev\Git\dps\server\ApiWapper\RDMSWebClient.cs:line 84
   at Devolutions.Server.ApiWrapper.RDMSWebClient.SaveRecording(SaveRecordingModel model) in C:\Dev\Git\dps\server\ApiWapper\RDMSWebClient.Recording.cs:line 54
   at Devolutions.DPS.DPSClient.<>c__DisplayClass7_0.<SaveRecording>b__0() in D:\a\dps\dps\processor-base\DPS\DPSClient.cs:line 76
   at Devolutions.DPS.DPSClient.ExecuteSaveRequest(Func`1 request) in D:\a\dps\dps\processor-base\DPS\DPSClient.cs:line 54
 2022-10-30 17:55:34,489 ERROR Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Unable to save recording info to DPS
 2022-10-30 17:55:34,489  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Uninitialize C:\Devolution_Output\e0de765f-0a62-4e53-9492-a404f7c5dff4.trp
 2022-10-30 17:55:34,490  INFO Devolutions.Processor.ProcessorService.? [?] - MESSAGE: Finished processing C:\Devolution_Output\collector\e0de765f-0a62-4e53-9492-a404f7c5dff4.pcap.

Thank you for your help, Richard!
Robin

Hello Robin,

My apologies, I had meant the processor, not the collector, as you assumed.

Your certificate is valid, but you are still receiving the SSL error. I will link your issue to the internal ticket to help the engineering team with your logs. I will also ask to raise the priority of the issue.

We will update this thread once we have more details.

Best regards,

Thanks Richard, and please let me know when there is anything I can contribute to the troubleshooting.

All the best,
Robin

Hello Robin,

A fix was developed internally which should fix the issue; QA is testing it now. We will let you know once it is available.

Best regards,