SignServer In Place Upgrade

This guide upgrades a single node from SignServer Enterprise version 7.7.0 to SignServer Enterprise 7.8.0.  In this example, the SignServer host has an IP Address of 172.16.17.130.  Change this IP address to be the IP Address that matches the SignServer node being upgraded.

Download the SignServer binary file from your customer download folder or obtain a copy from support at https://support.keyfactor.com/.

  1. Copy the upgrade package to the SignServer node using one of the following methods:

    1. Using the CLI:
      If using a Mac or Linux-based computer, run the following command to copy the file to the host. Ensure to specify the user as ec2-user with your SSH key.

      scp -i ~/.ssh/ssh-key.pem ~/Downloads/signserver-ee-7.8.0-bin.zip ec2-user@172.16.17.130:/opt/dist/
      
    2. Using a program such as WinSCP or CyberDuck:
      Click Open Connection.

      image2020-5-15_14-17-40.png?version=1&modificationDate=1605836959000&cacheVersion=1&api=v2&width=110&height=71

      Enter the host credentials and click connect.

      image2020-5-15_14-18-14.png?version=1&modificationDate=1605836959000&cacheVersion=1&api=v2&width=427&height=250

      Select the /opt/dist directory.

      image2020-5-15_14-29-33.png?version=1&modificationDate=1605836959000&cacheVersion=1&api=v2&width=408&height=250

      Drag and drop the file to the SignServer host in the /opt/dist directory.

  2. SSH to the SignServer host as user ec2-user with an authorized private key.

    ssh -i ~/.ssh/ssh-key.pem ec2-user@172.16.17.130
    
  3. Use sudo to switch to the root user.

    sudo su
    
  4. Change directory to the /opt directory.

    cd /opt
    
  5. Unzip the upgrade file into the /opt/ directory.

    unzip dist/signserver-ee-7.8.0-bin.zip
    
  6. Ensure the file is extracted into the /opt/ directory by doing a directory listing.

    [root@ip-172-16-1-105 opt]$ ls -la
    total 64
    drwxr-xr-x. 12 root     root       239 Jul 16 21:56 .
    drwxr-xr-x. 19 ec2-user ec2-user   253 Dec 17  2025 ..
    drwxr-xr-x.  8 wildfly  wildfly    137 Dec 17  2025 PrimeKey
    drwxr-xr-x.  6 root     root     16384 Dec 16  2025 apache-ant
    drwxr-xr-x.  4 root     root        33 Dec  3  2025 aws
    drwxr-xr-x.  8 root     root        76 Dec 16  2025 cloudhsm
    drwxr-xr-x.  6 root     root        90 Dec 16  2025 dist
    drwxr-xr-x.  3 root     root        32 Dec 16  2025 oracle
    lrwxrwxrwx.  1 wildfly  wildfly     19 Apr 28 15:36 signserver -> signserver-ee-7.7.0
    drwx------. 10 wildfly  wildfly  16384 Dec 17  2025 signserver-ee-7.5.0-bin
    drwx------.  8 root     root       187 Apr 28 15:38 signserver-ee-7.7.0
    drwx------.  9 root     root     16384 Jul 16 21:11 signserver-ee-7.8.0
    lrwxrwxrwx.  1 root     root        25 Dec 16  2025 wildfly -> /opt/wildfly-33.0.1.Final
    drwxr-xr-x.  9 wildfly  wildfly  16384 Dec 16  2025 wildfly-33.0.1.Final
    
  7. Copy the existing config files to the new SignServer install folder, overwriting the default files with the existing files.

    /bin/cp -f signserver/conf/*.properties signserver-ee-7.8.0/conf/
    
  8. Stop WildFly.

    systemctl stop wildfly
    
  9. Remove the signserver symlink.

    rm signserver
    
  10. If prompted to remove the symbolic link, type "y" and press enter.

    rm: remove symbolic link ‘signserver’?
    

Make sure the command asks you to remove symbolic link.

  1. Create a new symbolic link.

    ln -s signserver-ee-7.8.0 signserver
    
  2. Ensure the symbolic link points to the new SignServer directory.

    lrwxrwxrwx   1 root    root     16 Jul 16 21:10 signserver -> signserver-ee-7.8.0
    
  3. Change ownership of the new SignServer files. Ensure the trailing "/" in the command below so the permissions of the directory are changed and not the symlink itself.

    chown -R wildfly:wildfly /opt/signserver/
    
  4. Change directory to the /opt/signserver directory.

    cd /opt/signserver
    
  5. Deploy SignServer.

    ant deploy
    
  6. Restart WildFly.

    systemctl start wildfly
    
  7. Access the SignServer AdminWeb UI and ensure the new version of Signserver is 7.8.0.