[GH-ISSUE #1225] Feature: Meshcentral WebRelay enabled by default on new installs and upgrades #754

New issue

Closed

opened 2026-03-02 02:18:47 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 02:18:47 +03:00

Owner

Originally created by @johnnyq on GitHub (Jul 27, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1225

Is your feature request related to a problem? Please describe.
MeshCentral now allows you to connect through an agent to connect to an agent-less client on the network the agent resides on. Hence you can connect to a router, printer, pbx web interface.
Meshcentral uses port 453 to do the relaying or can use a subdomain like relay.domain.com port 443 to do this type of web relay.
Tactical uses Nginx as proxy and this would need to be configured to work with Meshcentral to forward the new port and/or subdomain

Describe the solution you'd like
I would like this to configured by default on new install and upgrades. It would also be nice to add the Agentless clients the Tactical Interface as well.

Describe alternatives you've considered
none

Additional context
More info on the WebRelay Feature of MeshCentral here

https://meshcentral2.blogspot.com/2022/07/meshcentral-web-relay-per-account-ssh.html

https://meshcentral2.blogspot.com/2022/04/meshcentral-device-groups-with-relay.html

and a video demonstration here

https://www.youtube.com/watch?v=GU7MQjkPSd8

Originally created by @johnnyq on GitHub (Jul 27, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1225 **Is your feature request related to a problem? Please describe.** MeshCentral now allows you to connect through an agent to connect to an agent-less client on the network the agent resides on. Hence you can connect to a router, printer, pbx web interface. Meshcentral uses port 453 to do the relaying or can use a subdomain like relay.domain.com port 443 to do this type of web relay. Tactical uses Nginx as proxy and this would need to be configured to work with Meshcentral to forward the new port and/or subdomain **Describe the solution you'd like** I would like this to configured by default on new install and upgrades. It would also be nice to add the Agentless clients the Tactical Interface as well. **Describe alternatives you've considered** none **Additional context** More info on the WebRelay Feature of MeshCentral here https://meshcentral2.blogspot.com/2022/07/meshcentral-web-relay-per-account-ssh.html https://meshcentral2.blogspot.com/2022/04/meshcentral-device-groups-with-relay.html and a video demonstration here https://www.youtube.com/watch?v=GU7MQjkPSd8

kerem

2026-03-02 02:18:47 +03:00

closed this issue
added the
wontfix
label

kerem commented

2026-03-02 02:18:47 +03:00

Author

Owner

@silversword411 commented on GitHub (Oct 26, 2022):

Since this is a meshcentral specific feature, and would require additional port forwarding, and more complex setup installation instructions it's unlikely to be something TRMM will support. Same argument could be said for AMT auto-configuration by TRMM...and that's another port, and more complexity. It's a rabbit hole without a bottom ;)

I'm going to list this as a won't fix...but if you want to add some notes in the docs for pointers (maybe Unsupported or meshcentral etc) that could be an option I can help with.

@silversword411 commented on GitHub (Oct 26, 2022): Since this is a meshcentral specific feature, and would require additional port forwarding, and more complex setup installation instructions it's unlikely to be something TRMM will support. Same argument could be said for AMT auto-configuration by TRMM...and that's another port, and more complexity. It's a rabbit hole without a bottom ;) I'm going to list this as a won't fix...but if you want to add some notes in the docs for pointers (maybe Unsupported or meshcentral etc) that could be an option I can help with.