Servers behind firewall, 1:1 NAT, does it work?

Derek

So I'm about a month into my Enhance journey. Yesterday I had my panel server (here at my location, 1:1 NAT behind my firewall) and a VPS I purchased, and all was good.

My plan is to clean off my other hosts and migrate all my sites to Enhance. Today I cleared one off, created a new VM and tried unsuccessfully to add it to Enhance 5 times. I think I finally figured out the issue:

The Panel and another server can't be on the same private subnet. If my panel is at 192.168.x.10, setting my second local server as 192.168.x.11 fails, and the panel is stuck trying to send RPC calls to the network gateway address.

However, putting the second app server on another DMZ (also on its own 1:1 NAT, so it has its own routable IP address) finally worked.

My Problem, or non problem: in the panel after install, my new server was listed as 192.168.y.11 as its IP address. I went to the server, choose the 3-dot dropdown, selected "Server IP Address," and entered the routable IP address that's mapped to this machine, and I think this will work.

I'll do more testing tomorrow, but for now, does it look like I did this as I was supposed to?

Derek

Aaand, it looks like it's working.

Added the new server in DNS, Database, and App roles
Installed cPGuard and it's running cleanly
Added the new server to the group I'm using

It seems like it took a bit before everything was integrated and running nicely, but I've created a new web site on the server and it's running cleanly. Will play more in the morning.

(Now I feel like I'm wasting space with this thread. More tomorrow after I get some sleep and get to tinker more.)

Derek

So this needs a follow-up for others who may run into this issue in the future.

Before moving to Enhance, I had things configured so all the servers I host on my own hardware shared the same network/VLAN. In Enhance I struggled to add a second server on the same network as the Panel server - instead the panel server errored out trying to communicate with the upstream gateway.

Setting up the second server on a separate network/VLAN solved this issue. So if my panel server was 192.168.1.10, setting up my second application server on the 192.168.2.x network worked fine. Once I went into the panel server the (local, non-routable) IP address of the new application server was listed, and I needed to take an additional step to specify the public IP address that the server would respond to, so that address could be added to DNS entries for client sites.

This means that if I need 4 separate locally hosted application servers that I will need a separate network for each one, but the configuration required to accomplish this isn't too terrible.

That's the way I think things are running now.

Hope this helps someone else.