Nginx-proxy-manager: Config Templates & Load Balancing

[obxjames]

Is your feature request related to a problem? Please describe.
So we have a node based dashboard that monitors a mesh network that is on several raspberry pi's with the same configurations. NPM has been a great tool, but every time we set up another pi in the network we manually add another point which is a pain but the reason of the idea.

Describe the solution you'd like
Can we save a template (or duplicate) an already set up config? IP address changes but port doesn't and neither does the URL (apart from the beginning part of sub domains

I know it's been requested a lot but like to also add my request for load balancing. Having one URL would be great!

[miguelwill]

Greetings
the use of several servers in backend is possible with NPM if you use an internal DNS service in which the necessary hosts are added to serve the same site
for example, using dnsmasq:

in /etc/hosts:
172.16.5.15 workers.site.domain
172.16.5.16 workers.site.domain

and then, in NPM proxy-host, use the name "workers.site.domain" in the field "Forward Hostname / IP*"
if the same port is kept active on both IPs, it will balance the connections between both internal IP addresses

[obxjames]

That is a genius idea! I will give it a go and report back. Thank you

[w796933]

If you can use a different port, how to solve it?

[miguelwill]

If you can use a different port, how to solve it?

in the case of a cluster, the backends should use the same port in order to use a single name and the same port
perhaps later, in the case of managing multiple backend servers, a different port could be used on each one, but it is not advisable to use different ports on systems that serve the same application

[EriksonGM]

Still waiting for this.

[miguelwill]

the function of copying a configuration to use as a template sounds very practical, especially when time is invested in preparing a functional configuration