then i dont understand why my server is acting up, because if i add rmm agent, it does not appear on mesh even after uploading relevant agents of mesh to rmm. which also prevents me from doing rdp through rmm
Markuz you amaze me again
so my question can I combine a Tactical RMM Docker with an existing MeshCentral instance?
Or in my case, i would feel better with a direct 2nd nethserver with a direct Tactical RMM installation or may be on the same system as MeshCentral as a direct install docker and i are still not very good friends at this moment.
Kind Regards
IIRC that’s possible but it’s preconfigured in the docker version.
The native Tactical RMM install without docker didn’t work for me.
As regards more complex projects, my experience is that it’s easier to put them into a virtualization accepting overhead and performance loss than to fight with sometimes impossible system integration.
Hi all, i’ve tried to install TacticalRMM with docker but i think that the step for the configuration are not complete: the steps for docker, espacially #nats, give me back some error:
WARNING: The CERT_PUB_KEY variable is not set. Defaulting to a blank string.
WARNING: The CERT_PRIV_KEY variable is not set. Defaulting to a blank string.
ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
services.tactical-nats.networks.proxy contains unsupported option: ‘default’
I’ve tried to setup Tactical on a Debian VM following the amidaware documentation and the site is online correctly. I’m new to Docker so i’ll try your new steps for test purpose and learning Docker. However in the #nats part of the file my setup differ a bit, maybe I have made a mistake during the configuration
Looking back at this, i am curious how these updated below, affect the installation, especially in the ports definition
Release v0.14.0
Switched to NATS websocket for agent<->server communication. This removes the need to publicly expose port 4222 TCP and now the only open port needed is 443 TCP. You must leave port 4222 open though until all your agents are updated to v2.1.0 at which point you may close port 4222 in your firewall.
Note for those running UNSUPPORTED setups or proxies (HAProxy, NPM, Traefik, Kubernetes etc. Ignore this section if you are on a traditional or docker install): NATS still listens on 4222 (for internal communication between various trmm services) but now also listens internally on localhost:9235 (websocket protocol). Agent NATS traffic now connects to nginx public port 443 which is proxy passed to localhost:9235 so you will need to implement this manually in your proxy settings. You may refer to this commit to see how a supported nginx setup implements it (make sure to only proxy pass traffic that matches the pattern https://api.example.com/natsws). You must implement this in your custom proxy before upgrading to this release.
If for whatever reason you can’t use NATS websocket or just want to keep things the way they were before this release, check out these docs on how to fall back to NATS standard.
Note for docker users: the docker-compose.yml file has changed this release so make sure to delete the old one and re-download the latest one (just copy paste from the docker update docs).
GEt Agents and Download Agents, no longer NEcessary with VErsions: 0.12.0 and above
they are automatically created. using emsh api
Removed the need to manually upload and manage mesh agents. They are now dynamically generated using meshcentral’s api. Added a new setting in Global Settings > MeshCentral to specify the meshcentral device group name for those that are not using the default device group name that tactical sets up during install.