Skip to main content
YHC
Explorer
January 21, 2025
Question

Unable to connect Website after changing server's private IP

  • January 21, 2025
  • 6 replies
  • 1412 views

Dear Sir,

 

We have a almalinux server running a website. This server has a dedicated Public IP.

We want to change its private IP address from 192.168.3.A to 192.168.3.B.

Before changing the private IP, we have duplicated all relate Fortigate firewall policies for the new IP 192.168.3.B.

 

However, we found that we still cannot connect the website after changing the private IP.

The sever is connected to the internet because we can ping outside from the server, and we can also ping the server from other computer in the same subnet.   We feel the problem is due to the firewall policy but we don't know where it is.

 

Can anyone advise us what settings can cause this problem?

Thank you.

 

6 replies

AEK
SuperUser
SuperUser
January 21, 2025

Hi

Did you change the VIP as well?

AEK
YHC
YHCAuthor
Explorer
January 21, 2025

Yes, I have changed VIPs in the duplicated policies.

AEK
SuperUser
SuperUser
January 21, 2025

But did you remove the old VIPs. If you keep them then they will still map to the old IP:Port.

On the other hand, try run the debug flow command and share the output to see if the traffic is correctly mapped and if it is blocked by some rule.

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Debug-flow-tool/ta-p/213238

 

AEK
Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!