Point-to-site configuration failed

Gary Patchcott 0

Hi, when trying to configure a P2S VPN, I get the following:

Deployment validation failed.

Additional details from the underlying API that might be helpful: The template deployment 'Microsoft.Network-20240726082904' is not valid according to the validation procedure. The tracking id is xxxxxxxxxx.

I am trying to do this in the portal.

The settings I'm using are:

Tunnel Type: IKEv2 and OpenVPN (SSL)

IPSec/IKE Policy: Default

Authentication type: Azure certificate

I have checked the activity log. There isn't anything in there that helps identify the problem.

Any help would be appreciated.

Thanks

Gary

Luis Arias 7,121 Reputation points

2024-07-26T08:25:18.79+00:00

Hi Gary,

Can you please follow this thread https://learn.microsoft.com/en-us/answers/questions/1351745/point-to-site-vpn-deployment-failure

Cheers,

Luis
KapilAnanth-MSFT 46,876 Reputation points Microsoft Employee

2024-07-26T08:30:53.1966667+00:00
@Gary Patchcott ,

From the error message,

It looks like you are trying to use a Template File (Bicep/ARM/Terraform)

Are you trying to create a new VPN Gateway with P2S Enabled or trying to update an existing gateway with P2S Configuration

Is there any reason you are not trying it with Portal?

I would suggest you first try it with Portal

And then build the template to make sure you are not facing any regional/permission issues

Cheers,

Kapil
Gary Patchcott 0 Reputation points

2024-07-26T09:17:23.9633333+00:00

Hi Kapil

No, I am not using a template. I'm doing it via the portal.

Yes, its brand new VPN Gateway, in a brand new RG.

Thanks

Gary
Gary Patchcott 0 Reputation points

2024-07-26T09:19:47.4533333+00:00

Thanks Luis. I have seen that article but I don't think it pertains to what I am doing as I'm not using a template. I'm doing it via the portal.Thanks

Gary
KapilAnanth-MSFT 46,876 Reputation points Microsoft Employee

2024-07-26T09:45:34.0166667+00:00
@Gary Patchcott ,

As next steps,

Make sure the Client Address pool is not overlapping with the VPN Gateway's VNET, peered VNETs and on prem S2S Connections (if any)

See : Root certificate public key information

Make sure that you exported the root certificate as a Base-64 encoded X.509 (.CER)

Make sure you are adding any trailing spaces before and after the "root certificate"

If the above does not help, please try recreating the certificate : Generate and export certificates for point-to-site using PowerShell

Cheers,

Kapil
Gary Patchcott 0 Reputation points

2024-07-26T10:06:26.1566667+00:00

Thanks Kapil

I will try that.

Thanks

Gary
Gary Patchcott 0 Reputation points

2024-07-26T12:52:59.0033333+00:00

Hi Kapil

I checked all of this points you mentioned. I even recreated a new cert. (making sure there are no spaces after the root cert etc.

I'm still getting the same problem.

Thanks

Gary
KapilAnanth-MSFT 46,876 Reputation points Microsoft Employee

2024-07-29T09:27:22.84+00:00
@Gary Patchcott ,

As next steps,

You can try the same using Powershell : Configure P2S Gateway certificate authentication - PowerShell

If that does not help, please share the root certificate you generated in private message which I have initiated.

NOTE : YOU CAN CHANGE THE ROOT CERTIFICATE OR USE A DIFFERENT ONE GOING FORWARD

I am only interested in checking the correctness of the certificate by doing a lab on my own

Cheers,

Kapil

Share via

Point-to-site configuration failed

Your answer