Manage and Update

Running the start script (sudo ./ubuntu-start.sh on Ubuntu, ./rhel-start.sh on RHEL) starts the Link-Live server, which persists through subsequent runs of the script.

Ensure you access Link-Live Private via the exact hostname/IP entered when you ran the start script.

NOTE
The start script is OS-specific. Use sudo ./ubuntu-start.sh on Ubuntu and ./rhel-start.sh on RHEL.
All other scripts live in the toolkit/ folder and have plain names. Run them with sudo on Ubuntu and without sudo on RHEL.
See Script Naming and Usage.

Keyfile Management

After installation, log in with your superuser account credentials, and upload your keyfile. (Contact NetAlly Support if you have trouble acquiring yours.)

To update your keyfile later (due to renewal of your Link-Live Private license subscription or purchase of AllyCare Pro), use the Super Tools available to the superuser account to replace the existing file: open the left-side menu and navigate to (Super Tools) > Keyfile Management.

NOTE: The downloadable keyfile is refreshed daily. Wait 24 hours after purchasing your Link-Live Private Subscription or AllyCare Pro Support before downloading and importing a new keyfile.

Updating Link-Live Private

When a new version of Link-Live Private is released, we recommend the following steps:

  1. Back up your existing data/volumes (see Backup and Restore).

  2. Download the update bundle for your operating system. On the Software Downloads page, select Install / Update, then Update an existing installation. See Install and Start-Up for the full download procedure.

    NOTE: One update bundle covers every supported Ubuntu version, so the dialog does not ask which version you are running.

  3. Extract the update bundle. Unlike an installer bundle, it extracts to a folder matching the tar.gz file name:

    Ubuntu: sudo tar -xvzf link-live_<version>_ubuntu_update.tar.gz -C /opt

    RHEL: tar -xvzf link-live_<version>_rhel_update.tar.gz -C ~

  4. Move into the extracted folder. For example:

    Ubuntu: cd /opt/link-live_<version>_ubuntu_update

    RHEL: cd ~/link-live_<version>_rhel_update

  5. Run the start script with the update option to update your version of Link-Live Private. All of your previous configurations will persist.

    Ubuntu: sudo ./ubuntu-start.sh update

    RHEL: ./rhel-start.sh update

    NOTE: On RHEL, the boot service is automatically re-pointed at the new bundle directory as part of the update. No action is needed.

  6. Check the new version on the About page in your Link-Live Private instance: click the Support button at the bottom of the left-side navigation menu and select About.

  7. Optionally, delete the old Link-Live Private installation directory. Your data remains safe.

NOTE: When upgrading to a new version of Link-Live Private:

  • Any database migrations that the new version requires are performed automatically. The migration scripts are in the db-migrations folder of the bundle, and each is named for the version that introduced it.

  • No user input is required.

  • Additional informational messages appear during the update process.

Updating Specific Configurations

If a specific area of configuration needs to be updated, use any combination of the following options with the start script to only update those parts.

Arguments can be combined. For example, sudo ./ubuntu-start.sh mail cert updates mail settings and SSL certificates, and sudo ./ubuntu-start.sh host auth updates the host address and the superuser credentials.

NOTE: Your previously saved environment variable must be loaded to update specific parts.

Variable

Action

signup

Enable or disable users' ability to create a new account from the login page.

mail

Update mail settings.

serial

Change your PVT serial.

host

Change the host IP or name.

auth

Change the superuser or superuser password.

lic

Update the expiring license notification type.

cert

Change which certificates Link-Live Private uses.

jwt

Change the authentication keys.

NOTE: All users will be logged out and all units unclaimed.

update

Update to a newer version, keeping all previous configurations.

restart

Restart Link-Live Private with the existing configuration.

Command-Line Options

The start script also accepts the following options:

  • -h, --help – Show usage information.

  • -v, --verbose – Show detailed output during installation. NetAlly Support may ask you to run the start script with this option if an installation fails.

Stopping Link-Live Private

To stop the Link-Live Private containers, run the command for your operating system from inside the installation directory:

Ubuntu: sudo docker compose -p linklive stop

RHEL: podman-compose -p linklive stop

On RHEL, you can instead stop the service that manages the containers:

systemctl --user stop linklive.service

CAUTION! The commands sudo docker stop $(docker ps -aq) and podman stop $(podman ps -aq) stop every container on the machine, not only Link-Live Private. Use them only if Link-Live Private is the sole container application on the server.