[GH-ISSUE #1076] Take Control not connecting #2610

New issue

Closed

opened 2026-03-14 04:49:24 +03:00 by kerem · 0 comments

kerem commented

2026-03-14 04:49:24 +03:00

Owner

Originally created by @ccasalicchio on GitHub (Apr 20, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1076

Server Info:

OS: Ubuntu 20.04
Browser: chrome
RMM Version: v0.12.4

Installation Method:

Standard
Docker

Agent Info:

Agent version: Agent v2.0.2
Agent OS: Windows 10/11

Describe the bug
The agent works just fine, but when I try to run the "Take Control" it just never connects. I believe this could be a DNS/Reverse proxy issue, as we are running the RMM server behind an Nginx server.

NGINX config:

server { 
 listen 80; 
 server_name 
remotermm.site.com api.site.com rmm.site.com;
 location / { 
 proxy_pass http://xxx.xxx.xxx.xxx:80/;  
 proxy_http_version 1.1; 
 # Inform MeshCentral about the real host, port and protocol 
 proxy_set_header X-Forwarded-Host $host:$server_port; 
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
 proxy_set_header X-Forwarded-Proto $scheme; 
 } 
 } 
 # HTTPS server. In this example, we use a wildcard as server name. 
 server { 
 listen 443 ssl; 
 server_name 
remotermm.site.com api.site.com rmm.site.com;
  
 # MeshCentral uses long standing web socket connections, set longer timeouts. 
 proxy_send_timeout 330s; 
 proxy_read_timeout 330s; 
 # We can use the MeshCentral generated certificate & key 
 ssl_certificate    /www/server/panel/vhost/cert/remotermm.site.com/fullchain.pem;
    ssl_certificate_key    /www/server/panel/vhost/cert/remotermm.site.com/privkey.pem;

 ssl_session_cache shared:WEBSSL:10m; 
 ssl_ciphers HIGH:!aNULL:!MD5; 
 ssl_prefer_server_ciphers on; 
 location / { 
 proxy_pass https://xxx.xxx.xxx.xxx:443/;  
 proxy_http_version 1.1; 
 # Allows websockets over HTTPS. 
 proxy_set_header Upgrade $http_upgrade; 
 proxy_set_header Connection "upgrade"; 
 proxy_set_header Host $host; 
 # Inform MeshCentral about the real host, port and protocol 
 proxy_set_header X-Forwarded-Host $host:$server_port; 
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
 proxy_set_header X-Forwarded-Proto $scheme; 
 } 
 }

To Reproduce
Steps to reproduce the behavior:

Login
Navigate to the computer
Click "Take Control"

Pop-up opens but never connects

Expected behavior
Should open the remote screen

Screenshots

Additional context
This is a new installation, got the agents to work, but mesh is not connecting apparently

Originally created by @ccasalicchio on GitHub (Apr 20, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1076 **Server Info:** - OS: Ubuntu 20.04 - Browser: chrome - RMM Version: v0.12.4 **Installation Method:** - [X] Standard - [ ] Docker **Agent Info:** - Agent version: Agent v2.0.2 - Agent OS: Windows 10/11 **Describe the bug** The agent works just fine, but when I try to run the "Take Control" it just never connects. I believe this could be a DNS/Reverse proxy issue, as we are running the RMM server behind an Nginx server. NGINX config: ``` server { listen 80; server_name remotermm.site.com api.site.com rmm.site.com; location / { proxy_pass http://xxx.xxx.xxx.xxx:80/; proxy_http_version 1.1; # Inform MeshCentral about the real host, port and protocol proxy_set_header X-Forwarded-Host $host:$server_port; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } # HTTPS server. In this example, we use a wildcard as server name. server { listen 443 ssl; server_name remotermm.site.com api.site.com rmm.site.com; # MeshCentral uses long standing web socket connections, set longer timeouts. proxy_send_timeout 330s; proxy_read_timeout 330s; # We can use the MeshCentral generated certificate & key ssl_certificate /www/server/panel/vhost/cert/remotermm.site.com/fullchain.pem; ssl_certificate_key /www/server/panel/vhost/cert/remotermm.site.com/privkey.pem; ssl_session_cache shared:WEBSSL:10m; ssl_ciphers HIGH:!aNULL:!MD5; ssl_prefer_server_ciphers on; location / { proxy_pass https://xxx.xxx.xxx.xxx:443/; proxy_http_version 1.1; # Allows websockets over HTTPS. proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; # Inform MeshCentral about the real host, port and protocol proxy_set_header X-Forwarded-Host $host:$server_port; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } ``` **To Reproduce** Steps to reproduce the behavior: 1. Login 2. Navigate to the computer 3. Click "Take Control" Pop-up opens but never connects ![image](https://user-images.githubusercontent.com/2466879/164310743-ad5f7e8d-1486-43bd-8c41-33a50e5e7492.png) **Expected behavior** Should open the remote screen **Screenshots** ![image](https://user-images.githubusercontent.com/2466879/164310799-298b25c9-2255-4ceb-9067-b0b50ae27088.png) **Additional context** This is a new installation, got the agents to work, but mesh is not connecting apparently