It will be the same issue. The difference is GoDaddy cert would be installed manually by you, and only every couple of years.
Since it’s infrequent, just update the registry key yourself and bounce the RRAS service. Here are my notes I made for myself before using a CTW script to automate it. You have probably already done the top part (since you’re getting the disconnect problem) so jump straight to “Update SSTP to match…”
Certificate needs to be changed in IIS and also SSTP listener. Mismatching certificates causes client to connect then immediately disconnect.
Certificates in use can be checked -
netsh http show sslcert
All bindings are listed. 0.0.0.0:443 = default web site. [::]:443 = SSTP listener.
Note the existing certificate hash in case it is necessary to revert
In IIS Manager, change the certificate for the default web site (“bindings”, non-host header site on port 443)
Restart IIS Admin service. SSTP VPN will no longer stay connected. Test this from a previously-working client (to generate an event log error)
Update SSTP to match newly-installed IIS Certificate:
netsh http show sslcert
Note the changed hash for 0.0.0.0:443. This will need to be changed for the SSTP VPN listener (SHA1).
If no RRAS GUI (per WS2016E):
-
- Go to HKLM\System\CurrentControlSet\Services\SstpSvc\Parameters*
-
- Enter the “SHA1CertificateHash” key from your new certificate (old hash should match Event 6 RASMAN error)*
-
- Restart RRAS service*
-
- Test the new configuration*