The intermediate certificate our server agent uses to talk with our servers will expire in November 2016. In newer agent versions since version 8, the updated certificate is already included. All older versions need to be updated.

Find out agent version

First you need to know which server agent version you are running. Go to the folder where the binary is saved and run it with option ‘-v’.

./agent -v
or on windows
agent.exe -v

Now there are 2 options:

  • The parameter is not known and not available: You have a very first version of the agent (v2 – v7)
  • You get a version returned: Versions 0 – 7 needs to be updated. If you get 8 returned you are good. Current version is 13.

If you are using Plesk

When you are on Plesk, you have to update the agent anyway. Please follow the guide below.

Update self hosted agent

  1. Download the current version of the nimbusec Server Agent for your server from nimusec Portal
  2. Unzip the archive and copy the binary over the current installed version of the server agent

Update on Plesk

Don’t want to mess with the Plesk frontend? Guide to update the server agent directly on the Plesk server.

Plesk is a little different and as we do not yet have an update button for the server agent you need these few steps to complete the upgrade:

  1. Uninstall the nimbusec Plesk extension via your Plesk panel
  2. Install the updated Plesk plugin from Plesk extensions
  3. On first tab: Insert your API key and secret (can be found in nimbusec Portal)
  4. On second tab: check if all domains are set as before -> Click ‘Save’ to create the configuration for the agent
  5. On third tab: Update cron settings and click on ‘Save’ to create the cronjob again

The uninstall has no effect on the registered domains in the nimbusec Portal. It just removes the nimbusec Server Agent from your server and the cron settings used to start the server agent.

The fresh install, downloads the current available nimbusec Server Agent from the portal and installs it in the right place on your server. Also the cronjob is freshly created.