JetProxy Overview - Gateway Proxy Architecture – JetPatch

JetProxy Use-Cases

JetProxy allows you to use a single JetPatch console for managing endpoints in multiple data centers
JetProxy simplifies the deployment of JetPatch within a perimeter network (DMZ), where a special firewall rule needs to be requested for every endpoint in order to allow it to connect to the JetPatch server
Hybrid Environment Management: Manage endpoints across different environments, such as having a main JetPatch console on-premises and a JetProxy console for cloud or remote devices. For added security, it's advisable to block the login page of JetProxy to ensure all management activities are conducted through the main console.

Connectivity: Ensure connectivity between JetProxy and the JetPatch server using netcat over port 443..
Firewall Settings: Ensure firewall settings allow connections on port 443/HTTPS.
DNS Resolution: Ensure the machine can resolve the server's hostnames (if used).
WSUS Server Requirements (Optional): Ensure the necessary requirements for the WSUS server if required.

Proxy Function: JetProxy acts as a proxy to the main JetPatch console, allowing users to view and manage all endpoints through the main console.
Connector Installation: Connector installation is not possible through the proxy solution since this is a web proxy not an SSH/SMB2 proxy. For instructions on how to install the connector on the endpoint itself, see this article.
Connector Upgrades and Removal: Connector upgrades and removal can be performed through the proxy solution. Ensure you create a connector service for your proxy endpoints, which will be important for connector upgrade and service reconfiguration.
No Agent Storage: Agents are not stored on the proxy server.
Login Page Security: In a hybrid environment, blocking the login page of JetProxy enhances security by ensuring that all management activities are conducted through the main JetPatch console.