R82 to R82.10 - VPN Issues

[Wayne_Hammond]

Hi,

Had a weird issue that has never happened before. Upgrading caused a weird VPN issue going from R82 to R82.10

Upgrade worked fine, running tests, last one VPN failed - when testing with Capsule via Android, IOS or Windows I got capsule conenctions failing - message either malfomed reply from site or SSL error - failed to read data from site

Logs showed certificate mismatch 

When connecting - VPN is connecting to fw2.*******.com, but gateway present default certificate 

CN = ****** VPN Certificate

No matter what I do to state use fw2 cert, still fails

Any thoughts or ideas greatly appreciated

Currently rolled back snapshot so I can get VPN's working

Regards

Wayne

[Lesley]

Did you install a recent jumbo update after the R82.10 installation? Otherwise you will encounter:

PRJ-66998, PRJ-67000, PRJ-67034, PMTR-124920, PRHF-44366

VPN, Internal CA

Starting March 1st, 2026, newly created certificates and newly generated CRL may fail validation. Refer to sk184766.

[Wayne_Hammond]

Cheers, so the 15th Jun R82.10 build doesnt include the CRL validation HF?

[emmap]

If you upgraded using the combined R82.10 / JHF take 24 package, then yes that fix was included. 

[Wayne_Hammond]

yes i used - R82.10 Security Gateway + JHF T24 for Appliances and Open Servers

So still a bit confused

[PhoneBoy]

Aside from the cert thing @Lesley mentioned, just confirming you installed policy AFTER upgrading to R82.10?
Installing policy with the gateway object set to the correct version is a necessary post-upgrade step.

[Wayne_Hammond]

I pushed policy

[Wayne_Hammond]

As a follow up i built an lab test R82 open server in VMware - configured it, this time just using default certificate - VPN works from test laptop.  Took a snapshot - upgraded to R82.10 - changed build, pushed policy - VPN fails - so something else is happening I think?

[PhoneBoy]

Best to get TAC involved here.