Fresh install: Can login, but nothing else works

[herzkerl]

Dear community,

I’ve just finished installing TRMM on a fresh server (VM) running Debian 11. The install script ran without any errors, and after first logging in I needed to create a client and a site, which I did.

Unfortunately, nothing else works, i.e. no menu item does seem to do anything.

Any ideas?

[dinger1986]

Hello, probably best to reinstall using a logged install

[herzkerl]

Will do, I’ve just reinstalled without logging, didn’t see any errors. troubleshoot_server.sh gives the following output (redacted):

tactical@trmm:~$ ./troubleshoot_server.sh
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
Enter the subdomain for the backend (e.g. api.example.com): api.tactical.example.com
 Verified api.tactical.example.com

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

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

Enter yourdomain used for letsencrypt (e.g. example.com): tactical.example.com
 Checking IPs

dig: couldn't get address for '': not found
 Locally Resolved:  Remotely Resolved: 11.22.33.44

 Your Local and Remote IP for api.tactical.example.com all agents will require non-public DNS to find TRMM server

dig: couldn't get address for '': not found
 Locally Resolved:  Remotely Resolved: 11.22.33.44

 echo Your Local and Remote IP for rmm.tactical.example.com all agents will require non-public DNS to find TRMM server

dig: couldn't get address for '': not found
 Locally Resolved:  Remotely Resolved: 11.22.33.44

 Your Local and Remote IP for mesh.tactical.example.com all agents will require non-public DNS to find TRMM server

 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 mongod Service is running

 Success postgresql Service is running

 Success redis-server Service is running

 Checking Open Ports

 WAN IP is 11.22.33.44

trmm.tactical.example.com [11.22.33.44] 443 (https) open
 HTTPs Port is open

 Checking For Proxy

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

 No Proxy detected using Certificate

 No Proxy detected using IP

 Checking SSL Certificate is up to date

Saving debug log to /var/log/letsencrypt/letsencrypt.log
 SSL Certificate for tactical.example.com is fine

Saving debug log to /var/log/letsencrypt/letsencrypt.log

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
  Certificate Name: tactical.example.com
	Serial Number: 123456789012345678901234567890
	Key Type: RSA
	Domains: *.tactical.example.com
	Expiry Date: 2023-04-08 13:18:20+00:00 (VALID: 89 days)
	Certificate Path: /etc/letsencrypt/live/tactical.example.com/fullchain.pem
	Private Key Path: /etc/letsencrypt/live/tactical.example.com/privkey.pem
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 Getting summary output of logs    raise exc
  File "/rmm/api/env/lib/python3.10/site-packages/rest_framework/views.py", line 506, in dispatch
	response = handler(request, *args, **kwargs)
  File "/rmm/api/env/lib/python3.10/site-packages/rest_framework/decorators.py", line 50, in handler
	return func(*args, **kwargs)
  File "/rmm/api/tacticalrmm/core/views.py", line 97, in dashboard_info
	"default_date_format": get_core_settings().date_format,
  File "/rmm/api/tacticalrmm/core/utils.py", line 78, in get_core_settings
	raise CoreSettingsNotFound("CoreSettings not found.")
core.utils.CoreSettingsNotFound: CoreSettings not found.


2023/01/08 15:35:02 [error] 33173#33173: *10 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 55.66.77.88, server: api.tactical.example.com, request: "PATCH /alerts/ HTTP/1.1", upstream: "uwsgi://unix:////rmm/api/tacticalrmm/tacticalrmm.sock:", host: "api.tactical.example.com", referrer: "https://rmm.tactical.example.com/"
2023/01/08 15:35:02 [error] 33174#33174: *15 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 55.66.77.88, server: api.tactical.example.com, request: "GET /clients/ HTTP/1.1", upstream: "uwsgi://unix:////rmm/api/tacticalrmm/tacticalrmm.sock:", host: "api.tactical.example.com", referrer: "https://rmm.tactical.example.com/"
2023/01/08 15:35:02 [error] 33172#33172: *14 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 55.66.77.88, server: api.tactical.example.com, request: "GET /core/dashinfo/ HTTP/1.1", upstream: "uwsgi://unix:////rmm/api/tacticalrmm/tacticalrmm.sock:", host: "api.tactical.example.com", referrer: "https://rmm.tactical.example.com/"
2023/01/08 15:35:02 [error] 33174#33174: *18 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 55.66.77.88, server: api.tactical.example.com, request: "GET /core/version/ HTTP/1.1", upstream: "uwsgi://unix:////rmm/api/tacticalrmm/tacticalrmm.sock:", host: "api.tactical.example.com", referrer: "https://rmm.tactical.example.com/"

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

[silversword411]

Are you using a real domain name?

[herzkerl]

Yes, although used a wildcard A entry for *.tactical.example.com, but that shouldn’t matter. I can dig all three subdomains without any issues.

[herzkerl]

I re-created the whole VM and it works now. So either something went wrong with the VM installation or 0.15.7 fixed it. :)