XRDP Connection Issues - Not Able to Reconnect

Rocky Linux General
1

I’ve been encountering some persistent issues with my XRDP setup, and I’m seeking your expertise and guidance to help me resolve them. The problem centers around reconnecting to XRDP sessions, and I’m seeing several error messages in my logs. I’ve included the log entries below for your reference (I can include the actual log files as well):

[20231018-00:15:51] [ERROR] libxrdp_force_read: header read error
[20231018-00:15:51] [ERROR] [ITU-T X.224] Connection Sequence: CR-TPDU (Connection Request) failed
[20231018-00:15:51] [INFO ] Security protocol: configured [SSL|RDP], requested [SSL|HYBRID|HYBRID_EX|RDP], selected [SSL]
[20231018-00:15:51] [ERROR] xrdp_sec_incoming: xrdp_iso_incoming failed
[20231018-00:15:51] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20231018-00:15:51] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20231018-00:15:51] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20231018-00:15:51] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[20231018-00:16:10] [ERROR] SSL_read: Failure in SSL library (protocol error?)
[20231018-00:16:10] [ERROR] SSL: error:0A000126:SSL routines::unexpected eof while reading
[20231018-00:16:10] [ERROR] libxrdp_force_read: header read error
[20231018-00:16:10] [ERROR] Processing [ITU-T T.125] Connect-Initial failed
[20231018-00:16:10] [ERROR] [MCS Connection Sequence] receive connection request failed
[20231018-00:16:10] [ERROR] xrdp_sec_incoming: xrdp_mcs_incoming failed
[20231018-00:16:10] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20231018-00:16:10] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20231018-00:16:10] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20231018-00:16:10] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed

I can successfully connect via RDP, but when I close the RDP window to my server, I lose all connectivity, and both SSH and Cockpit become inaccessible. However if I have an ssh session and leave it open while connecting it will not disconnect, but if I close it out I won’t be able to access it.

If anyone has encountered similar problems or has expertise in XRDP, I’d greatly appreciate any suggestions, recommendations, or solutions you can provide. I’m particularly interested in understanding what these log entries mean and how to resolve them.

2

Have you tried restarting the xrdp service? Does that have any effect?

It sounds like a known issue in which the MS Terminal Server Client fails to properly close the session, leaving it stuck in a limbo state of sorts. This also can happen if other programs attempt to scan or connect to port 3389 incorrectly, as well.

Check out neutrinolabs’ github project page for xrdp for issues 2714 and 2040, for a start.

3

I did restart the service after closing the RDP window and was able to log back in but it went to a black screen. Kind of strange behavior, also thank you for the github issues. I think I may just look at other options, any advice on what to use that is opensource?

4

I used to like xrdp, and it worked quite well most of the time–at least for a single user. Once I deployed a multi-user dual-EPYC box I started to have more issues than expected, and we switched that one to NoMachine… I think it used to be completely free and open, but at some point moved to a free-but-closed model, selling support and things for an extra fee.

Honestly, it’s really hard to beat – but it’s not open source, unfortunately.

Perhaps with a little time this particular issue with xrdp will be resolved. Here’s hoping! :grinning:

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.