Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

To update the Link using Docker you must: 

  1. Check the current version of the server (in the left low corner of the Login page in the Link web interface). 

  2. In the repository check if there are no update peculiarities for the version you want to install. If there is, read the attached manual and complete the instructions.

  3. Login to your server via SSH.

  4. Login as a superuser: sudo su, and enter the same password one more time.

  5. Follow the directory where your Link is:

    cd/home/link/

  6. Choose the correct type of Link server. If you use the Link:

    1. with SIP, but not using the domain name (e.g. http://176.215.90.19, http://3.111.25.45) perform:

      cd with-sip

    2. with SIP, and with domain name (e.g. https://preview.intercom.team) perform: 

      cd with-sip/with-web-proxy

    3. without SIP, and without domain (simply management features) perform:

      cd without-sip

    4. without SIP, but with domain (simply management features + SSL) perform:

      cd without-sip/with-web-proxy

If you use the Link with-web-proxy, make sure, that the .env file in the current directory still contains your changes: vi .env
HTTPS_DOMAIN='your domain'
HTTPS_MODE=production
IMAGE=latest

If there are no changes, please, write down your data.

  1. In case of updating from the Link version lower than 1.2.126, please, copy the .env file (as described in Step 4) and make changes after that: cp .env.example .env

  1. Stop the current Link server with the command:

 docker-compose down

 It should be run in the directory with the corresponding type that you are use.

 8. Update installation images from which the new Link version will be deployed:

docker-compose pull

  1. Start your updated Link server in some seconds: docker-compose up -d

docker-compose up -d

  1. As a result new version will start functioning. Make sure that all of your containers are started and running properly:

docker ps

  1. Login to the Link using the previous IP/domain.

(warning) If you have trouble running the Pull command because of the file on the machine with modifications that are not in Git, it is necessary to remove these changes and only then pull the update.

Try the following options:

  • in this directory, run the following command with a dot at the end followed by a space. This will clean up any changes

    git checkout.

  • for force reset perform: 

    git reset --hard


  • No labels