-
Notifications
You must be signed in to change notification settings - Fork 603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No sure if this is a feature or config change #3911
Comments
Try adding this to the domain section of the config.json:
This will create MeshCentral Router HTTP and HTTPS links at the bottom of the device "General" tab. One click will invoke MeshCentral Router and open the browser to the web page. Let me know if that works, I may add it as a default. |
Hi Ylian, Thank you for providing this config. This works, but I think I didn't explain my request correctly; I thought the new feature might bypass using the mesh router since we are now using a relay agent on the website. In our scenario, we are unable to use meshrouter due to company policies but we can use the mesh central web server and agents. If the relay option works just like mesh router where we can add Esxi or other web management devices, it will be a great option. Thank you for this awesome product. |
I see. The relay feature allows the MeshCentral server to access new devices by using existing agents as relays, it does not change anything on the user side. If you are looking to access HTTP/HTTPS web pages without MeshCentral Router, I could work on this but it would require that MeshCentral have an additional HTTPS port (like port 444). I could sent a cookie to the browser and open a new browser window to the HTTPS/444 port and all requests would be redirected to the target. Using this system, you can't open many web site in the same browser at the same time (one cookie and one port 444 at any given time) but it would work without a router. |
This will be a nice addition to managing other web-based apps without a VPN connection using the relay option on the web. I feel like the second option will be best since you already have a lot of features such as a web application to connect, recording, sharing guest links, etc which can be used. Regards, |
hi @dani717, I think your first request is to have Mesh Agent behave as a proxy for HTTP/S pages. i.e. the Agent will make the HTTP request and then act as the http/s server to share it back to the user. There are many open source software that perform this kind of function, Apache webserver can be configured as a reverse proxy for example. @Ylianst is suggesting a Mesh Agent port mapping for the HTTP/S page similar to how the Mesh Router performs this function. @dani717 The second option you proposed is App sharing, similar to remote desktop but limited to an application window/s, This would require the Mesh Agent to focus on the App only (perhaps run as User 0 and perform background app rendering I assume) which is different to Capturing full screen/s. Citrix has ways to do this for multiple users, so it is possible. However to support multiple users, the server machine must be logged in different profiles to do this securely. |
@si458 not likely to be implemented |
correct this wont be implemented, |
Hello Team,
Is it possible to add HTTP or HTTPS with IP and Port from the drop-down just like web rpd and web ssh
I use a mesh router to access other devices that use HTTPS such as ESXi and I thought maybe it would be possible now that we have a relay option. I might be wrong :)
Thanks
The text was updated successfully, but these errors were encountered: