[GH-ISSUE #190] Document handling of /etc/hosts for mesh domain #342

Open
opened 2026-03-14 07:46:56 +03:00 by kerem · 4 comments
Owner

Originally created by @NiceGuyIT on GitHub (Aug 21, 2023).
Original GitHub issue: https://github.com/amidaware/trmm-docs/issues/190

Commit 716c0fe introduced the "management" of /etc/hosts to handle the scenario of cloud init files. This change assumes a reverse proxy is not used and will cause problems for people using MeshCentral with reverse proxies.

In my environment, mesh.example.com points to the reverse proxy to get the TLS cert, not 127.0.0.1. Since $meshdomain is included in the checks/fix, updating might "break" the (unsupported) reverse proxy configuration.

I don't expect the code to be updated to account for unsupported configurations. This issue is to update the documentation.

Originally created by @NiceGuyIT on GitHub (Aug 21, 2023). Original GitHub issue: https://github.com/amidaware/trmm-docs/issues/190 Commit [716c0fe](https://github.com/amidaware/tacticalrmm/commit/716c0fe9794f15ef100eb398ebb5fe9b9ac81a71) introduced the "management" of `/etc/hosts` to handle the scenario of cloud init files. This change assumes a reverse proxy is not used and will cause problems for people using MeshCentral with reverse proxies. In my environment, `mesh.example.com` points to the reverse proxy to get the TLS cert, not `127.0.0.1`. Since `$meshdomain` is included in the checks/fix, updating **might** "break" the (unsupported) reverse proxy configuration. I don't expect the code to be updated to account for unsupported configurations. This issue is to update the documentation.
Author
Owner

@NiceGuyIT commented on GitHub (Aug 21, 2023):

The "symptom" is the Connect greyed out in MeshCentral. journalctl reports the following.

Aug 21 07:27:44 ns-v18-tactical meshcentral[2486]: Agent bad web cert hash (Agent:e583a0455e != Server:1a57156b69 or 1a57156b69), holding connection (127.0.0.1:36028).
Aug 21 07:27:44 ns-v18-tactical meshcentral[2486]: Agent reported web cert hash:e583a0455e0e7378449c502f4431fe8ddda4cd86f24bbe0b806cb3eef713ebd094aec202b4744692daf2f91040a2f5aa.
<!-- gh-comment-id:1686190874 --> @NiceGuyIT commented on GitHub (Aug 21, 2023): The "symptom" is the Connect greyed out in MeshCentral. `journalctl` reports the following. ```text Aug 21 07:27:44 ns-v18-tactical meshcentral[2486]: Agent bad web cert hash (Agent:e583a0455e != Server:1a57156b69 or 1a57156b69), holding connection (127.0.0.1:36028). Aug 21 07:27:44 ns-v18-tactical meshcentral[2486]: Agent reported web cert hash:e583a0455e0e7378449c502f4431fe8ddda4cd86f24bbe0b806cb3eef713ebd094aec202b4744692daf2f91040a2f5aa. ```
Author
Owner

@silversword411 commented on GitHub (Aug 22, 2023):

How would you suggest documenting it? Disclaimer in the unsupported first page?

<!-- gh-comment-id:1687437091 --> @silversword411 commented on GitHub (Aug 22, 2023): How would you suggest documenting it? Disclaimer in the unsupported first page?
Author
Owner

@LastStopITSolutions commented on GitHub (Sep 24, 2023):

My PR essentially addresses this issue. The error isn't mentioned per se but if users follow my writeup to a T they shouldn't see this error.

<!-- gh-comment-id:1732455610 --> @LastStopITSolutions commented on GitHub (Sep 24, 2023): My PR essentially addresses this issue. The error isn't mentioned per se but if users follow my writeup to a T they shouldn't see this error.
Author
Owner

@silversword411 commented on GitHub (Dec 6, 2023):

My PR essentially addresses this issue

Which PR?

<!-- gh-comment-id:1843566625 --> @silversword411 commented on GitHub (Dec 6, 2023): > My PR essentially addresses this issue Which PR?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/trmm-docs#342
No description provided.