Good I am glad my research is fixing this problem for others. Don't forget to create a ticket with Meraki and not just fix the problems the bigger the problem the sooner they will release a fix for it.

@smartkid808

I found this thread by google and I think it needs an update. If you are doing a site to site VPN on over non-Meraki VPN peers or Meraki to Meraki across two organisations because the self config does not work you will get the Missing Template ERR_CONNECT_FAIL if you have under,

Security appliance/ Content filtering - Web search filtering enabled. Disabling this option will re enable port 80 over the VPN.

This seems to only apply to Organization-wide settings and not Meraki Site-to-site VPN on the VPN side. It has also been reported on rear occasions to apply to outside DNS.

Good I am glad my research is fixing this problem for others. Don't forget to create a ticket with Meraki and not just fix the problems the bigger the problem the sooner they will release a fix for it.

@smartkid808

I found this thread by google and I think it needs an update. If you are doing a site to site VPN on over non-Meraki VPN peers or Meraki to Meraki across two organisations because the self config does not work you will get the Missing Template ERR_CONNECT_FAIL if you have under,

Security appliance/ Content filtering - Web search filtering enabled. Disabling this option will re enable port 80 over the VPN.

This seems to only apply to Organization-wide settings and not Meraki Site-to-site VPN on the VPN side. It has also been reported on rear occasions to apply to outside DNS.