Welcome to Microsoft Q&A!
Thank you for taking the time to provide the detailed error messages and the troubleshooting you have already performed.
Based on the symptoms and the timing, I would first focus on validating the certificate chain presented by Windows Server rather than the xxx.remotewebaccess.com name itself.
When a client establishes a TLS connection, it must be able to build a valid certificate path from the server certificate, through the required intermediate CA certificate(s), to a trusted root CA.
If the required intermediate certificates are not configured correctly on an IIS server, clients might be unable to authenticate the server. It also specifically notes that when an SSL certificate is renewed, the relevant intermediate issuing certificates should be reviewed and updated as necessary.
This is consistent with what you are seeing: after renewal, the certificate is now issued through GoDaddy TLS Intermediate CA DV - R1v1, while the client reports a trust problem with the certificate chain.
The fact that the issuing intermediate changed after renewal does not, by itself, mean that the new certificate is invalid. What needs to be confirmed first is whether Windows Server has the correct certificate chain and is presenting it correctly to clients.
The renewed certificate may be using a different GoDaddy certificate chain, but the Windows Server might not currently have the required intermediate certificate installed or available in the appropriate certificate store.
I would not recommend importing all of the certificates from the GoDaddy repository simply to make the warning disappear. Only the certificates required for the actual chain should be involved. And I would also avoid selecting Continue or permanently trusting the certificate warning as a workaround until the chain has been validated.
On the Windows Server:
- Open
certlm.msc.
- Browse to
Certificates (Local Computer) > Personal > Certificates and open the renewed server certificate.
- On the Details tab, verify the Subject, Issuer, Thumbprint, validity dates, and intended purpose.
- On the Certification Path tab, verify the complete certificate path and check whether Windows reports any problem with the root or intermediate CA.
Manage Certificate Stores in Windows Server recommends checking the complete certification path before making certificate-store changes. It also advises verifying the expected issuer and thumbprint before importing a certificate.
If the required GoDaddy intermediate certificate is missing, obtain the applicable certificate directly from GoDaddy and install the required intermediate certificate under:
Certificates (Local Computer) > Intermediate Certification Authorities > Certificates
This is a recommendation installing required intermediate certificates in the Intermediate Certification Authorities store of the local computer. IIS then uses the local computer certificate chain when determining what should be provided to clients during TLS negotiation.
Please be cautious about manually adding a certificate to Trusted Root Certification Authorities just to remove the warning. Changing this store changes which certificate authorities the server trusts, and Microsoft warns that incorrect changes can weaken the security of the system.
Before importing any downloaded CA certificate, verify its Issuer, Subject, Thumbprint, and validity information against the values published by the certificate provider.
Then, after validating or correcting the certificate chain, test https://xxx.remotewebaccess.com again from Windows and the iPhone.
The important result is that the clients should be able to validate the certificate without displaying a certificate trust warning.
For the Windows VPN side, also confirm that the appropriate server certificate is being used by the Microsoft server components. Windows Server certificate deployment guidance includes RRAS among the server roles that use server certificates to prove their identity during authentication.
If the certificate is trusted correctly through the Microsoft/Windows components but SSTP Connect continues to report an error, please understand that this is where the scope of Microsoft Q&A becomes limited.
SSTP Connect is a third-party application and GoDaddy is the certificate provider. Microsoft Q&A can help with the Windows Server configuration and how a third-party certificate integrates with Microsoft components, but I cannot validate or troubleshoot the internal behavior of the SSTP Connect application or GoDaddy's certificate issuance and trust implementation.
If the issue remains specific to SSTP Connect after the Windows Server certificate chain has been validated, please contact SSTP Connect support for further investigation. If there is a question about the certificate or CA chain supplied by GoDaddy, please contact GoDaddy support.
If either vendor identifies a specific compatibility or configuration issue involving a Microsoft component, you are welcome to return with those details. Otherwise, I would unfortunately not be able to provide further troubleshooting for the third-party product itself through Microsoft Q&A.
References: Manage Certificate Stores in Windows Server | Microsoft Learn
Configure intermediate certificates in Internet Information Services (IIS) - Internet Information Services | Microsoft Learn
Server Certificate Deployment Overview | Microsoft Learn
If you find it useful, please click Accept Answer.
Thank you for choosing Microsoft Q&A.