Admin wants to deploy a new VM in VMware and deploy FortiWeb-VM_PAYG.
FWB-PRO-01 # get system status
International Version: FortiWeb-VM_PAYG 7.6.7,build1111(GA.M),260204
Serial-Number: FVBOS10069e78238
Bios version: 04000002
Log hard disk: Available
Hostname: FWB-PRO-01
Operation Mode: Reverse Proxy
FIPS-CC mode: disabled
System Uptime: [0 day(s) 0 hour(s) 35 min(s)]
Current HA mode: active-passive, primary
HA member:
Serial-Number Priority HA-Role
FVBOS10069e78238 5 primary
FVBOS10069e77ed6 8 secondary
Database Status: Available
Security Level: 1
Firmware Signature: GA Certified
The packet sniffer is set to filter and collect all traffic to the virtual server, and observe that FortiWeb only resets the connection.
#diagnose network sniffer any "host 172.20.52.11" 4
interface=[DMZ-UAT]
3.793078 172.20.52.20.59519 -> 172.20.52.11.443: syn 2656285529
interface=[DMZ-UAT]
3.793094 172.20.52.11.443 -> 172.20.52.20.59519: rst 0 ack 2656285530
interface=[DMZ-UAT]
4.111521 172.20.52.20.63616 -> 172.20.52.11.443: syn 2059415498
interface=[DMZ-UAT]
4.111541 172.20.52.11.443 -> 172.20.52.20.63616: rst 0 ack 2059415499
If the admin tries to verify that the proxyd process is running, no information is displayed.
FWB# fn pidof proxyd
The issue is related to the wrong firmware FortiWeb-VM_PAYG was deployed. FortiWeb-VM_PAYG only works with FortiManager.
The right firmware FortiWeb-VM64 must be selected, and the VM needs to be redeployed.
 | 
