Merge pull request #189 from silversword411/main

Clarifying DNS names, other misc stuff

docs/faq.md

@@ -127,6 +127,14 @@ Type "help", "copyright", "credits" or "license" for more information.
 >>> User.objects.exclude(is_installer_user=True).filter(agent__isnull=True)
 ```
 
+## How do I make another superuser for logging into `rmm.`
+
+```sh
+cd /rmm/api/tacticalrmm/
+source ../env/bin/activate
+python manage.py createsuperuser
+```
+
 ## I am locked out of the web UI. How do I reset my password?
 
 SSH into your server and run:
@@ -179,6 +187,9 @@ sudo systemctl start meshcentral.service
 
 to reset Mesh password for user.
 
+!!!warning
+    Resetting the default admin in mesh will break agent installs if you don't also update the mesh connection into in Settings > General > Meshcentral and make sure [it's working](troubleshooting.md#agents-not-installing-or-updating)
+
 ## Help! I've been hacked and there are weird agents appearing in my Tactical RMM!
 
 No, you haven't.

docs/install_server.md

@@ -133,7 +133,8 @@ ufw enable && ufw reload
 We'll be using `example.com` as our domain for this example.
 
 !!!info
-    The RMM uses 3 different sites. The Vue frontend e.g. `rmm.example.com` which is where you'll be accessing your RMM from the browser, the REST backend e.g. `api.example.com` and MeshCentral e.g. `mesh.example.com`
+    The RMM uses 3 different sites. The Vue frontend e.g. `rmm.example.com` which is where you'll be accessing your RMM from the browser, the REST backend e.g. `api.example.com` and MeshCentral e.g. `mesh.example.com`<br>
+    `rmm.` `api.` and `mesh.` are what we recommend, but you can use whatever you want if they're already in use.
 
 1. Get the public IP of your server with `curl https://icanhazip.tacticalrmm.io`
 2. Open the DNS manager of wherever the domain you purchased is hosted.

docs/troubleshooting.md

@@ -307,3 +307,5 @@ Write-Output "Path after changing the type:", $path
 3. Add in your api, rmm and mesh urls on the line for 127.0.1.1 in the hosts file
 4. Save the hosts file
 5. Restart services or run `update.sh --force`
+
+54 year agents in the dashboard can be a sign of this NATS problem