My domain is: https://www.levelup-analytics.com
My web server is (include version): IIS 8.5
The operating system my web server runs on is (include version): Windows Sever 6.2
Hi,
I began having certificate errors this morning (though my certificates were still valid until the 20th), and upon renewal (or creation), everything worked fine until the last step:
[INFO] Installing certificate in the certificate store
[INFO] Adding certificate www.levelup-analytics.com 2018/12/6 13:00:42 to stor
e WebHosting
[INFO] Installing with IIS...
[INFO] Updating existing https binding :443
[INFO] Committing 1 https binding changes to IIS
[EROR] Error installing
System.IO.FileLoadException: Nom du fichier : \?\C:\windows\system32\inetsrv\co
nfig\applicationHost.config
Erreur : Impossible de valider les modifications de configuration parce que le f
ichier a été modifié sur le disque
("Error: impossible to validate the configuration modifications because the file was modified on the disk")
à Microsoft.Web.Administration.Interop.IAppHostWritableAdminManager.CommitCha
nges()
à Microsoft.Web.Administration.ConfigurationManager.CommitChanges()
à Microsoft.Web.Administration.ServerManager.CommitChanges()
à PKISharp.WACS.Clients.IISClient.Commit()
à PKISharp.WACS.Clients.IISClient.AddOrUpdateBindings(Target target, SSLFlags
flags, CertificateInfo newCertificate, CertificateInfo oldCertificate)
à PKISharp.WACS.Plugins.InstallationPlugins.IISWebInstaller.PKISharp.WACS.Plu
gins.Interfaces.IInstallationPlugin.Install(CertificateInfo newCertificate, Cert
ificateInfo oldCertificate)
à PKISharp.WACS.Program.OnRenewSuccess(ILifetimeScope renewalScope, Scheduled
Renewal renewal)
It's extremely urgent because my server is not accessible to my clients anymore - does anyone have any idea what this error is about and how to fix it?
Thanks for your quick response - I ended up rebooting the server (which I didn’t do at first because a lot of scripts are constantly running on it) as a last resort and it did the trick.
Another thing to watch out for with IIS is when you commit new bindings it can actually take a while to flush the new config to disk, so follow up attempts to change bindings may throw exceptions, this gets worse if you have many sites or many bindings. For Certify I use a combination of a c# lock, multiple retries and an added 2.5s delay on error.
