xrdp: [ERROR] xrdp_mm_chansrv_connect: error in trans_connect chan
I am trying to use xrdp on arch linux and client on macOS ArchLinux : x86_64 MacOS : Moneterey
When I try to connect using RDP on macOS it shutdown after sometime and it shows this when I check the status of xrdp
Apr 04 11:33:38 batman xrdp[3622]: [INFO ] lib_mod_connect: connecting via UNIX socket
Apr 04 11:33:38 batman xrdp[3622]: [INFO ] lib_mod_log_peer: xrdp_pid=3622 connected to X11rdp_pid=3640 X11rdp_uid=1000 X11rdp_gid=1000 client_ip=::ffff:192.168.29>
Apr 04 11:33:38 batman xrdp[3622]: [INFO ] connected ok
Apr 04 11:33:42 batman xrdp[3622]: [WARN ] xrdp_mm_chansrv_connect: connect failed trying again...
Apr 04 11:33:46 batman xrdp[3622]: [WARN ] xrdp_mm_chansrv_connect: connect failed trying again...
Apr 04 11:33:50 batman xrdp[3622]: [WARN ] xrdp_mm_chansrv_connect: connect failed trying again...
Apr 04 11:33:54 batman xrdp[3622]: [WARN ] xrdp_mm_chansrv_connect: connect failed trying again...
Apr 04 11:33:54 batman xrdp[3622]: [ERROR] xrdp_mm_chansrv_connect: error in trans_connect chan
Apr 04 11:33:54 batman xrdp[3622]: [ERROR] SSL_shutdown: Failure in SSL library (protocol error?)
Apr 04 11:33:54 batman xrdp[3622]: [ERROR] SSL: error:14094123:SSL routines:ssl3_read_bytes:application data after close notify
the logs are mentioned below in the comment.
First when I didn’t made gateway the rdp was showing blackscreen. I tried what is mentioned in arch wiki and added gateway also then I started getting SSL error. I don’t understand where the problem lies. Thaks for the help.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 21 (8 by maintainers)
Hi, I had a very similar issue.
For me, switching in
/etc/X11/Xwrapper.configfrom"allowed_users=console"to"allowed_users= anybody"did the trick.I was having the same error on xrdp 0.9.21.1 compiled on linux mint 21.1. After changing xorg path on sesman.ini fixed the problem.
Sorry - been away for a few days.
For both of you, I cannot stress enough that there should be absolutely no need to mess with
/etc/X11/Xwrapper.configon any system. You can get the Xorg server working this way, but it’s far better to simply put the correct path to the unprivileged Xorg insesman.iniin the correct place. It’s far more secure.@ksajan - the problem @wichs describes fixes the X server not starting at all. I don’t think you have this problem. What desktop are you trying to start?
xrdp-sesman.log