Separate MeshCentral Agent + Web Console ports

[joeldeteves]

We've discussed this previously in Discord, and I think it's time to open an issue for it.

As the description says, I am requesting that the MeshCentral Agent + Web Console ports be separated.

This is to allow for more fine-grained control and better security of the bundled MeshCentral instance.

For example, if the Agents run on their own port, we can proxy in front of the web console while still allowing agents to communicate, set firewall rules only allowing access from certain IPs to the Mesh Console, etc.

Happy to help out with this one on the Docker side - unsure what, if anything needs to change on the TRMM side.

Thank you,

EDIT: Here is an explanation from Ylian on how this works:

[joeldeteves]

Just a FYI, I found a workaround on this.

I was able to use Path on my Traefik reverse proxy to exclude the agent paths.

However, for users who want to use another method e.g. firewall/vpn, it would be good to have the ports separated.

[Trapulo]

Can you explain what did you do?
I'm using HAProxy as reverse proxy + SSL offloading behind the Tactical docker env.