Behind pfsense 1:1 NAT and added internal IP, now websites getting "apache is functioning properly"

[BooDaddy]

Hey all. I have been running this setup for a few years now. I am behind a pfSense router. I have 3 public ipv4's that are setup as a 1:1 NAT that all redirect to an internal IP address of the VM thats running DA. I have a single ethernet adapter on the VM, and it had a single IP on it of 172.17.0.50. In pfSense I had my 3 public IPs setup doing a 1:1 nat, and all three of those were directing to 172.17.0.50. That 1.1 looked like this, with all the externals going to a single internal:
1.2.3.0 ---> 172.17.0.50
1.2.3.1 ---> 172.17.0.50
1.2.3.2 ---> 172.17.0.50

All of this worked nicely. I was able to give 2 of my public IPs to resellers, and things worked gret.

recently, I upgraded pfsense, and now 1:1 is a bit different. It won't allow me to have 3 external IPs NAT'd to a single internal IP. The solution was to add 2 more IP's to my DA vm and then do 1:1 NAT for them. So, I added two more IPs to the VM of 172.17.0.51 and 172.17.0.52. Then I set my 1:! NAT to be as follows: (using 1.2.3.* as examples to protect my actual external IPs)

1.2.3.0 ---> 172.17.0.50
1.2.3.1 ---> 172.17.0.51
1.2.3.2 ---> 172.17.0.52

That fixed my 1:1 NAT issue, but now some of the websites are getting the "Apache is functioning normally" which seems like Apache and/or DNS doesn't like the new internal IPs assigned to my single NIC. Literally the only changes I made were to add the 172.70.0.51 and 172.70.0.52 internal IPs to the DA VM, and then setup the 1:1 nat.

What am I missing here? Do I need to do something in DA to configure this to work properly?

 

[Ohm J]

IP Link should solved this problem.

Admin -> IP Manager -> then select your first IP (.50) and after that find the IP Link button and link your other IP to current selected IPs.

Ensure you tick option like webserver and DNS before click apply to linked IPs.

 

[BooDaddy]

Thanks for the suggestion. I clicked on the first IP (.50) and then clicked the "link" button. and then added two links for the other two IPs (.51 and .52). It looks like this now:

I even selected all the check boxes for DNS, apache, etc when linking both of these IPs. I am now getting a slightly different problem on some of the websites on this machine. I am getting: "This IP is being shared among many domains. To view the domain you are looking for, simply enter the domain name in the location bar of your web browser."

While on a few others, I am getting "Apache is functionin Normally"

And then a few other websites, they are working perfectly fine.

Do I need to add the external public IPs as in this configuration as well and link them?

 

[Ohm J]

No need, it should working like the normal public IPs.

If you see in "Custom HTTPD Configuration" nginx/apache template, it should have extra IPs assign to virtualhost.