Pular para o conteúdo principal

Updating Signer on Windows Server

This page shows how to update an on-premises Signer instance installed on IIS following the Windows Server setup.

Before you update​

  1. Check the installed version. Open https://<your-domain>/api/system/info in the browser. The productVersion field shows the version.
  2. Read the changelog of every version between yours and the new one. Look for the versions marked as changing the database model.
  3. If you are moving from 2.x to 3.x, also follow Updating to 3.x. Version 3.0.0 requires the .NET 10.0 Hosting Bundle. Install it before you replace the binaries.
  4. Update the staging environment first. Test sending and signing documents before you update production.
  5. Pick a low-usage time. On the first startup, the application updates the database when the new version changes the model.
warning

If you have more than one server, only one of them must update the database. Stop the other servers, update one server and wait for it to start. Then update the others. Alternatively, on every server but one, set General:AutoUpdateDatabase and General:ProcessBackgroundJobs to false in appsettings.iis.json.

Backup​

  1. Stop the site in IIS Manager.
  2. Back up the database in SQL Server.
  3. Copy the site folder (for example, C:\inetpub\Signer). The copy includes appsettings.iis.json.

Update​

  1. Download the new version package: https://cdn.lacunasoftware.com/signer/signer-<version>.zip. The links for each version are in the changelog.
  2. Extract the package to the site folder and overwrite all files.
  3. Make in appsettings.iis.json the changes the changelog asks for.
  4. Start the site in IIS Manager.
note

The package has no appsettings.iis.json file, so your configuration does not change. The package does have a web.config. If you changed web.config (for example, the IIS upload limit), apply the change again after you extract the package. See Upload size limit.

Check the update​

  1. Open https://<your-domain>/api/system/info and check that productVersion shows the new version.
  2. Open the log file (set in Serilog, for example C:\Logs\Signer.log) and look for startup errors. The database update can take a few minutes.

If the site does not start and the log shows PKI SDK License was not loaded successfully, the application did not load the PKI SDK license (missing, invalid or expired). Ask Lacuna for an updated license and set it in PkiSuite:SdkLicense.

If IIS shows error 500.31 right after an update to 3.x, check that the .NET 10.0 Hosting Bundle is installed.

If something goes wrong​

If the new version has a problem, contact Lacuna support first. If you must go back to the previous version, follow the version rollback. To restore only the binaries, stop the site and restore the copy of the site folder.

See also​

View as Markdown