New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RDP does not work for any Windows clients #6051
Comments
I rebuilt MC on another Linux box (Alpine) and it works now. Any idea what the issue may have been? |
I don't know what the issue might have been but I can report that I am experiencing similar issues: I have xrdp installed on a linux VM and I can login remote using the MS Remote Desktop app (on my Mac). But I can't login via RDP from MC. MC can connect to the linix VM (there is an MC agent installed and I can connect via the agent). The MC credentials screen goes black for a moment and then comes back. RDP from MC used to work a while ago. |
I have been experiencing the same exact issue over the last couple weeks. Also using the typhonragewind Docker image on Ubuntu 22.04 behind Nginx Proxy Manager, no Cloudflare proxy. I ran the following tests (all through Nginx Proxy Manager, no Cloudflare proxy): From what I've gathered, this issue only occurs with the typhonragewind Docker image. I can't say for sure if it is a combination of other things causing it, but that is what I have found. Anyone else using the Docker image experiencing this as well? Curious what your setup looks like. |
@anthonyb800 have you tried using the offical docker github image? |
Thank you for the link @si458 ! |
I'm not using a docker image but the official npm install - if that makes a difference... |
Is it better to open my own issue? |
Describe the bug
If you navigate to any Windows client then click the RDP Connect button and enter your RDP credentials, it shows setup, then disconnects immediately, for any client.
This was working perfectly up until a couple of weeks ago and VNC and terminal sessions work fine to both Windows, Mac and Linux clients, it's just RDP that now refuses to work.
I can RDP to all affected clients directly, and there are no restrictions or firewalls blocking the connection.
My domain has been replaced with example.com in any text below.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
RDP session to client.
Server Software (please complete the following information):
Client Device (please complete the following information):
Core info for Windows 11 client:
Additional context
I have rebuilt MC completely from scratch and reinstalled Agents and the issue persists.
All intermediate firewalls have been disabled for testing including Cloudflare proxy.
No errors in the MC server log.
I don't know if it's relevant but although I have the server in WAN mode and using an FQDN, all my clients are on my LAN and I have an A record on my DNS server which points my domain example.com to the server IP.
Tracing in MC server shows:
172 is the Docker subnet.
Docker-compose:
Chrome developer network tab shows:
The NGINX proxy (Nginx Proxy Manager) points mesh.example.com to port 4430 (as this is mapped to 443 in Docker) and has HTTP/2 and websocket support enabled.
Your config.json file
I have tested with different configurations including disabling wscompression, webrtc etc.
The text was updated successfully, but these errors were encountered: