Hello,
I couldn't find many things about that, but I have a second NIC attached to my two PMGs public VPS servers.
On Configuration->Interfaces I added on each of them a static ip: 192.168.0.3 and 192.168.0.4.
If I create a cluster, it always uses the public IP NIC. I can't choose the second one. Is there a way to achieve that?
In the documenation I just found on the one hand: ( https://pmg.proxmox.com/pmg-docs/pm...mgproxy_proxmox_mail_gateway_api_proxy_daemon )
But on the other hand also: (https://pmg.proxmox.com/pmg-docs/pm...mgproxy_proxmox_mail_gateway_api_proxy_daemon)
I know, PMG uses VPN to connect clusters to each other, but I want to keep the public open ports as low as possible an want to route the traffic just internal. The webinterface still need to be accessible from public.
I couldn't find many things about that, but I have a second NIC attached to my two PMGs public VPS servers.
On Configuration->Interfaces I added on each of them a static ip: 192.168.0.3 and 192.168.0.4.
If I create a cluster, it always uses the public IP NIC. I can't choose the second one. Is there a way to achieve that?
In the documenation I just found on the one hand: ( https://pmg.proxmox.com/pmg-docs/pm...mgproxy_proxmox_mail_gateway_api_proxy_daemon )
Code:
LISTEN_IP can be used to restrict the socket to an internal interface, thus leaving less exposure to the public internet, for example:But on the other hand also: (https://pmg.proxmox.com/pmg-docs/pm...mgproxy_proxmox_mail_gateway_api_proxy_daemon)
Code:
The nodes in a cluster need access to pmgproxy for communication, possibly across different subnets. It is not recommended to set LISTEN_IP on clustered systems.I know, PMG uses VPN to connect clusters to each other, but I want to keep the public open ports as low as possible an want to route the traffic just internal. The webinterface still need to be accessible from public.