Pular para o conteúdo principal

Updating Signer on Azure App Services

This page shows how to update an on-premises Signer instance installed on an App Service following the Azure App Services setup.

Before you update​

  1. Check the installed version. Open https://<your-domain>/api/system/info. 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. On a Windows App Service, the .NET version setting must be .NET 10 (LTS).
  4. Update the staging App Service 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 the App Service Plan runs more than one instance, only one must update the database. Scale the plan down to one instance (Scale out) before you update, and scale it back after the site starts.

Backup​

  1. In the Azure portal, open the Signer SQL database and check that you can do a point-in-time restore to the time before the update. If you prefer, create a copy of the database with Copy.
  2. Keep the .zip package of the installed version. You will need it if you have to restore the binaries.

The App Service settings (Configuration) and the storage account files do not change with the update.

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. In the App Service Overview, click Stop.
  3. Go to Advanced Tools and click Go to open Kudu.
  4. In the top menu, click Tools and then Zip Push Deploy.
  5. Drag the .zip package onto the file list and wait for the deploy to finish.
  6. Make in Configuration the changes the changelog asks for and click Save.
  7. In Overview, click Start.

Check the update​

  1. Open https://<your-domain>/api/system/info and check that productVersion shows the new version. The first request can take a while as the database is updated.
  2. If there is an error, check the logs in the storage account table set in Serilog__WriteTo__0__Args__storageTableName (default: SignerLog).

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 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 the binaries, publish the previous version's .zip package through Kudu.

See also​

View as Markdown