Fresh Install Agent count always at zero (Unsupported Proxy used)

[crocobc]

Server Info (please complete the following information):

• OS: [e.g. Debian 12]
• Browser: [e.g. chrome, brave, firefox, edge, opera]
• RMM Version (as shown in top left of web UI): v0.19.3

Installation Method:

• Standard
• Standard with --insecure flag at install (I only have 1 Public IP available...)
• Docker

Describe the bug
Agent count always stays at zero...

To Reproduce

• Standard Installation with insecure flag.
• Installation is behind pfsense + Haproxy
• I followed step to install here https://github.com/ninjamonkey198206/T-RMM-PFSense-HAProxy-config
  and here https://docs.tacticalrmm.com/unsupported_proxies/#haproxy

Expected behavior
Show normal agent count

Additional context
I check for similar problem and saw that it maybe related to daphne.

Output of service daphne status:

service daphne status
● daphne.service - uvicorn daemon v1
     Loaded: loaded (/etc/systemd/system/daphne.service; enabled; preset: enabled)
     Active: active (running) since Tue 2024-10-08 16:23:59 +04; 16h ago
    Process: 2254 ExecStartPre=rm -f /rmm/daphne.sock (code=exited, status=0/SUCCESS)
    Process: 2255 ExecStartPre=rm -f /rmm/daphne.sock.lock (code=exited, status=0/SUCCESS)
   Main PID: 2256 (uvicorn)
      Tasks: 6 (limit: 4621)
     Memory: 108.5M
        CPU: 1min 10.723s
     CGroup: /system.slice/daphne.service
             └─2256 /rmm/api/env/bin/python3.11 /rmm/api/env/bin/uvicorn --uds /rmm/daphne.sock "--forwarded-allow-ips=*" tacticalrmm.asgi:application

oct. 09 00:49:30 rmm uvicorn[2256]: INFO:     connection closed
oct. 09 00:49:32 rmm uvicorn[2256]: INFO:     ('10.X.X.X', 0) - "WebSocket /ws/dashinfo/?access_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" [accepted]
oct. 09 00:49:32 rmm uvicorn[2256]: INFO:     connection open

No error in /rmm/api/tacticalrmm/tacticalrmm/private/log/ (only access.log with 200 requests other are empty.)

Troubleshoot Script

./troubleshoot_server.sh
-------------- mer. 09 oct. 2024 06:49:02 CEST --------------
Enter the subdomain for the backend (e.g. api.example.com):
api.domain.com
 Verified api.domain.com

Enter the subdomain for the frontend (e.g. rmm.example.com):
rmm.domain.com
 Verified rmm.domain.com

Enter the subdomain for meshcentral (e.g. mesh.example.com):
mesh.domain.com
 Verified mesh.domain.com

Enter yourdomain used for letsencrypt (e.g. example.com):
domain.com

 Checking IPs

 Success api.domain.com is Locally Resolved: PublicIP Remotely Resolved: PublicIP
 Success rmm.domain.com is Locally Resolved: PublicIP Remotely Resolved: PublicIP
 Success mesh.domain.com is Locally Resolved: PublicIP Remotely Resolved: PublicIP

 Checking Services

 Success RMM Service is Running
 Success daphne Service is Running
 Success celery Service is Running
 Success celerybeat Service is Running
 Success nginx Service is Running
 Success nats Service is running
 Success nats-api Service is running
 Success meshcentral Service is running
 Success postgresql Service is running
 Success redis-server Service is running

 Checking Open Ports

 WAN IP is PublicIP

xxxxxxxxxxxxxx-xxxxxxxxxxxxxx [PublicIP] 443 (https) open
 HTTPs Port is open

 Checking For Proxy

 ......this might take a while!!

 Proxy detected using Certificate

 No Proxy detected using IP

 Checking SSL Certificate is up to date

sudo: certbot : Command not found
 SSL Certificate for domain.com is fine

sudo: certbot : Command not found
 Getting summary output of logs

You will have a log file called checklog.log in the directory you ran this script from

Check TRMM connection to MeshCentral

tactical@rmm:~$ /rmm/api/env/bin/python /rmm/api/tacticalrmm/manage.py check_mesh
Mesh site: https://mesh.domain.com
Mesh username: xxxxxxxx
Mesh token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Mesh device group: TacticalRMM
Auth token ok:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Mesh url ok:
ws://127.0.0.1:4430/control.ashx?auth=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Mesh device id ok: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

PING

tactical@rmm:~$ ping api.domain.com -c 1
PING rmm.home (127.0.1.1) 56(84) bytes of data.
64 bytes from rmm.home (127.0.1.1): icmp_seq=1 ttl=64 time=0.030 ms

--- rmm.home ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.030/0.030/0.030/0.000 ms
tactical@rmm:~$ ping mesh.domain.com -c 1
PING rmm.home (127.0.1.1) 56(84) bytes of data.
64 bytes from rmm.home (127.0.1.1): icmp_seq=1 ttl=64 time=0.026 ms

--- rmm.home ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.026/0.026/0.026/0.000 ms
tactical@rmm:~$ ping rmm.domain.com -c 1
PING rmm.home (127.0.1.1) 56(84) bytes of data.
64 bytes from rmm.home (127.0.1.1): icmp_seq=1 ttl=64 time=0.021 ms

--- rmm.home ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.021/0.021/0.021/0.000 ms

I understand it's not a supprorted configuration but it's fresh install and i cannot see any erros anywhere....
Aside from that, all the features are working fine...

Any help would be appreciate.

[dinger1986]

Covered in #1778, but no resolution, if you can find a reason let us know but it does seem an odd way to do it installing with insecure then using a proxy. Better to install properly and then convert to using another proxy!

[crocobc]

Hi there,

I resolve it but i do not know why or how.... i do not understand.

I shutdown the VM with insecure installation.
(i was thinking that as soon as you're behind a reverse proxy you are obliged to install with --insecure.... my bad)

I create a LXC with same IP, Mask etc...an then make a normal installation.

It worked immediately (agent count).

I shutdown the LXC, reboot original VM with insecure installation.
I rsync letsencrypt from LXC to VM, change Nginx configuration ==> ALL IS WORKING !

Regards