wizard error - Unable to setup VPN: Empty values are not allowed

[jamestiberius]

tried using the wizard to create VPn tunnels between two fortinet boxes.

start creating VPN on first box, selected site to site VPN, get to the part where you put in the local interface, local subnet, and remote subnet, and when I click on CREATE I get the error:

Unable to setup VPN: Empty values are not allowed.

where is the empty value?  I have put information in at each step.

anyone ran into this before?

I can create one manually, just want to understand what the problem is.

[rwpatterson]

Can't say much about the wizard, but you will get that if you try to use an address entity that is on a different interface than what you're trying to set up.

Example: You have "server" set up on internal, but you use it as the destination for a DMZ -> WANx policy.

[CyberNorris]

Just got the same error. Opened the wizard again from the beginning and with the exact same steps in place it worked.

Now if the VPN itself would just work....!

[Allwyn_Mascarenhas]

cybernorris wrote:

Just got the same error. Opened the wizard again from the beginning and with the exact same steps in place it worked.

Now if the VPN itself would just work....!

did this last week, got this same error, just opened the wizard again and configured the vpn and it just worked.

[CyberNorris]

allwynmasc wrote:

cybernorris wrote:

Just got the same error. Opened the wizard again from the beginning and with the exact same steps in place it worked.

Now if the VPN itself would just work....!

did this last week, got this same error, just opened the wizard again and configured the vpn and it just worked.

Yup, after going backwards through the wizard a few times.

BTW, the VPN connected just fine. The laptop I was loaned to use for testing had a VM interface in the same subnet as the remote network, so it never sent any of the VPN traffic out the LAN port.

[gschmitt]

jamestiberius wrote:

Unable to setup VPN: Empty values are not allowed.

Use the dot-decimal notation instead of a net mask for the subnet mask

i.e. 255.255.255.0 instead of /24 etc.

[aaltojuk]

I had the same problem, but when I created the VPN with another name it went through fine. I tried rebooting, but somehow it still remembers my first try. How could I erase the old tunnel? I can't see it in the tunnels menu or anywhere else but somewhere Fortigate remembers I had another tunnel with same name.

[nojeffrey]

aaltojuk wrote:

I had the same problem, but when I created the VPN with another name it went through fine. I tried rebooting, but somehow it still remembers my first try. How could I erase the old tunnel? I can't see it in the tunnels menu or anywhere else but somewhere Fortigate remembers I had another tunnel with same name.

This seems to be a caching issue, open Chrome in Incognito mode and it stops reverting back to the old template you tried to create.

[nojeffrey]

Finally solved this after letting Fortinet support take control of my computer.

Instead of using the Custom template, just choose Cisco, fill in the basics, then modify it to you needs.

[ispcolohost]

Still run into this endlessly, even on 6.0; so frustrating if you build up a big phase 2 only to have no way to save any of it.