Feature Requests
New / Open / Unreviewed

[Feature]: Allow multiple server URL's

What is the installation method of your PatchMon server?

Docker

What is the version of your PatchMon server?

1.4.2

Briefly describe the feature

Allow multiple server URL's

Detailed description

Use case:

PatchMon server itself lives only in internal network, accessible by majority of hosts directly. I also have hosts that don't have a leg to this internal network and can only communicate via public network. I'd like to be able to create a heavily firewalled proxy that these hosts could reach PatchMon from as i don't want to expose the PatchMon server itself to public internet.

Request:
It would be nice to be able to configure more than one server URL's to allow this, in addition i'd like to be able to choose the desired server URL in the host creation when generating the agent installation command, e.g. from a drop down menu if there are more than one server URL's. I'd like to also be able to filter these hosts based on the server URL in hosts view to see from where they are connecting from.

Yeah i know i can already kinda achieve this partially on a proxy level by modifying the request host header but i can't use the copied command directly in the UI.

Why is this useful?

Better support for varying use cases.

2 Comments

Posting anonymously

9technologygroup·4 months ago

Even though we have upgraded PatchMon to version 2.0.0 I can see how this will be beneficial especially where DNS split scoping is not in play in the network.

I will look into this further and see how best I can implement it - ideally we choose the URL PatchMon server should be communicated through, maybe it can enumerate the list from the CORS_ORIGINS listed URLs there.

If more than 1 URL is listed there (excluding http://localhost:3000) then bring the drop down to select the communication URL that the agent will use via its config.yml file & also amend the agent installation URL.

Posting anonymously

derekgzn·4 months ago

This issue is not just a problem for wan connections, it's also an issue for internal lan connections, i.e. if the installation is completed using the LAN IP address then it cannot be accessed via the FQDN and vice versa.

Posting anonymously