> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/connect-3.2-en/instalacion/linux_actualizacion.md). # Linux update This guide will help you update the version of **Editran Connect** in Linux, step by step. The update can be carried out to switch versions or reinstall a component of the current version. > If you are coming from a version earlier than 3.x of **Editran Connect** (not from versions of Editran Open), after completing the update you must carry out the process detailed in the section **Post-Update** found further down on this page. ## Prerequisites Before starting the update process, you must make sure that: 1. you have a version of **Editran Connect** installed before proceeding with the update. 2. If you are coming from 2.1.x or earlier, uninstall **Editran Core Connect**. This will avoid conflicts between both applications. 3. Verify that the user performing the update has administrator permissions. > It is recommended to make a complete backup of the data, folders, and files of **Editran Core Connect** before uninstalling it. Likewise, before updating **Editran Connect**, it is essential to make a complete backup. This will ensure that you can restore the information if any problem occurs during the process. ## Graphical environment installation In Linux environments with a desktop system and modern versions of KDE or GNOME, it is possible to install the software in graphical mode, using the classic installer. To keep things simple and because Linux systems are usually installed on machines without a desktop environment, we do not cover it on this site. ## Update process Below, the installation steps are described. The process is quite simple and quick to perform. Make sure you have a console or terminal environment available. ### Start 1. Assign permissions to the installation file, if necessary: ```bash sudo chmod +x EditranConnect-3.0.x-linux-x64.run ``` 2. Run the installation package. The parameter `--mode text` indicates that you want to perform the installation in text mode. It is not necessary if the system has no graphical environment: ```bash sudo ./EditranConnect-3.0.x-linux-x64.run --mode text ``` 3. If you want to view the installation parameters, you can run the following command: ```bash sudo ./EditranConnect-3.0.x-linux-x64.run --mode text ``` ## Component selection Next, you can choose which components of the application you want to install: ![Component selection](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-f8e0ad01fbae650c048a033e7734efd487b2f609%2Fupgrade_seleccion_componentes_text.png?alt=media) 1. Some components are mandatory, so they cannot be edited or selected. 2. Some components are recommended for updating, so they appear marked and enabled. 3. It is recommended to leave the default selection if you are not sure which components to select. * **Java**: Type **Y** in this component if you need to update or reinstall the Java software. * **PostgreSQL**: Type **Y** in this component if you need to update or reinstall the PostgreSQL database engine software. * **Nginx**: Type **Y** in this component if you need to update or reinstall the Nginx web server software, or if you need to change the SSL certificate. * **Signing module**: Type **Y** in this component if you need to update or reinstall the signing module. 4. Press **Enter** to continue, or type **N** if you want to modify the component selection. ## Notice Next, you will be informed that the installation detects a previous version of **Editran Connect** installed on the system. In addition, you will be told that the installation will update the current version to the new version. Make sure you do not have any instance of **Editran Connect** open during the update process. ![Update notice](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-245140167699a6751a967e4e28118b11b4e59cb1%2Fupgrade_aviso_text.png?alt=media) Press **Enter** to continue. If the component **PostgreSQL** or **Nginx** is selected, continue in **Step 4**, and otherwise continue in **Step 5**. ## Linux distribution Next, you can select the Linux distribution you are using: ![Linux distribution](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-3a3b3ce0eef5f8764bfe8154ffae1cc638a32355%2Fdistribucion_linux_text.png?alt=media) 1. Indicate the Linux distribution you are using. If you are not sure, you can leave the default option. * **Debian**: For Debian-based distributions (Ubuntu, Mint). * **Red Hat**: For Red Hat-based distributions (Fedora, CentOS). * **Other distributions**: For other distributions not officially supported. 2. It is important to select the correct distribution, as this will affect the installation of the packages needed for the application to work. 3. Type the distribution number and press **Enter** to continue. ## Configuration. Certificate This information will be available if component **Nginx** is selected in **Step 2**. Otherwise, this step will be skipped. You can select the files for your own self-signed certificate: * **Certificate**: Certificate file (.pem). * **Certificate key**: Private key file (.key). ![Configuration. Certificate](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-a172a3c9eee67ba5fefabc91e43de4cfab9aa804%2Fconfiguracion_certificado_text.png?alt=media) 1. The application's signing certificate will be updated. 2. This information is optional. If you do not specify a certificate, the installer will use a temporary self-signed certificate. Although it is functional, it is not valid and must be replaced with an SSL certificate issued by a certificate authority. 3. If you want to use your own certificate, type **Y** in **Specify an SSL certificate**. 4. Press **Enter** to continue. 5. Then enter the name and path of the certificate files. ## License Next, you can select the license file (.dat) if you have one. This step is optional. ![License file](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-b6b0f9b4e5672fb7fc7ed50431cb3b7e475c8982%2Ffichero_licencia_text.png?alt=media) 1. Enter the name and full path of the license file, if you want to specify it. 2. Press **Enter** to continue. ## Summary Next, you will be shown a summary of the installation that will be performed: ![Installation summary](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-c22bfe90f97a436d3e3bcf6417d0c6ec5269b427%2Fupgrade_resumen_instalacion_text.png?alt=media) Among other things, the following information will be shown: * Version to install * Installation type (Update) * Directories * ... Press **Enter** to continue. *** ## Confirmation Next, you will be told that everything is ready to perform the installation: ![Ready to install](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-93ff9aa22d966f4209e36ab797c83b26ee9e1a74%2Fconfirmacion_instalacion_text.png?alt=media) 1. Type **N** if you do not want to start the installation process. 2. Press **Enter** to continue. ## Installation in progress Before carrying out the installation itself, a backup will be made of the files and folders from the previous installation. The backup will be stored in a directory with the same name as the application directory, adding the .backup extension at the end. **Default path**: `/opt/EditranConnect.backup`. Afterwards, the installation will begin and progress will be shown along with the running processes: ![Installation in progress](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-b2e40503d069aa9fd90462d552df319cd43e1d03%2Finstalacion_en_proceso_text.png?alt=media) 1. If the component **PostgreSQL** is selected in **Step 2**, and the installed PostgreSQL version is earlier than the version included in the installer, you will be asked whether you want to update PostgreSQL to the latest version. ![PostgreSQL version selection](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-a91f54e8f3b2492a1ce02454eb6681a4c3a09537%2Fupgrade_postgresql_text.png?alt=media) * Make sure the installed PostgreSQL version is compatible with your machine's operating system. If it is not compatible or you are not sure, type **N**. * If you type **Y**, PostgreSQL will be updated. 2. If the services do not start correctly, a warning message will appear. See the section *Troubleshooting* to identify the cause. Wait for the process to finish. ## Installation completed Once the installation is complete, a message will be shown that the process has finished ![Installation completed](https://1386330368-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jqgE5yyM3S58JKHROiz%2Fuploads%2Fgit-blob-3cc8959c4d41e830c0193131dd755a4b7f467eb8%2Finstalacion_finalizada_text.png?alt=media) **Done!** You now have the application **Editran Connect** updated. ## Post-Update This section only affects us if we are coming from version 2.x or earlier of **Editran Connect** In version 3.x, changes occur in the Editran protocol (5.3), along with a set of improvements to the product architecture. This forces us, after upgrading from Editran Connect 2.x to Editran Connect 3.x, to regenerate the data for P. The following process requires Connect to be updated to 3.x and the editran cfg folder to be empty (or, failing that, that there are no previous sessions) as well as the connect base services together with editran-license running. ### Steps to follow 1. Run migraContacto -u; if the message "Local configuration updated" appears, continue to the next step; otherwise, review the backend log (editranConnect/logs/connect-back). 2. Run migraCanales -c; if the message "Channel update to DES/RSA completed successfully" appears, continue to the next step; otherwise, review the backend log 3. Run migraCanales -u; if the message "Channels registered in editranP" appears, continue to the next step; otherwise, review the backend log 4. Review the txt files in the core/log/migrar folder indicated above to see the changes that have arisen (if no file was generated, it is probably because there were no changes to make) If there are channels that have switched to RSA cryptography, they must be edited to add exchange keys; until then they will not work, as they will give an incorrect RSA key error (a placeholder "?" is left). If a contact had protocol version 4.1, all its channels will already have been registered with 5.0 in editranP. Review integration scripts to stop using the old session alias and start using the local-remote-app code. **Once everything has been migrated, the editran base service can be started.** ## Troubleshooting ### 1. Errors during installation If you encounter any errors during the installation process, check the following points: * **Disk space**: Make sure there is enough space available for the installation. * **System compatibility**: Verify that your operating system and processor are compatible. * **Administrator permissions**: Run the installer with superuser (root) permissions to avoid permission problems. * **Antivirus or firewall**: Check that your antivirus or firewall is not blocking the installation. If necessary, disable them temporarily during the process. For more information about the error, consult the installation log file. ### 2. Services do not start If the installation was successful, but the services do not start, check the following: * **Dependencies**: Make sure all necessary services are running. For example, the service *Editran Connect Data* must be started before starting the service *Editran Connect Base*. * **Port in use**: Confirm that port 443 *(Editran Connect Server)* or 5432 *(Editran Connect Data)* is not occupied by another service. You can use tools such as `netstat` to check which ports are in use. * **Firewall**: Check that there is no firewall blocking the ports used by the services. * **Database configuration**: Verify that the database is correctly configured and accessible. Make sure the access credentials are correct and that the database server is running. * **Software conflicts**: Make sure there are no other programs or services in conflict with the **Editran Connect**. Check that the application **Editran Core Connect** is uninstalled. * **Linux distribution**: Verify that the Linux distribution selected during installation is the correct one. * **License**: Verify that the license file (`licencia.dat`) is present and valid. This means that the services *Editran License Service* and *Editran Connect Base* will not start. * **Local environment**: The service *Editran Connect Base* will not start until a local environment is configured in the *Editran Core*. For more details about possible errors, review the log files. *** ## Log files Below is a table with the different log files, their description, name, and location. | **Description** | **File(s)** | **Location** | | ------------------------------- | ------------------------------ | ------------------------------- | | Installation log | `installbuilder_installer.log` | `/tmp` | | Service startup and status log | `*.out, *log` | `%INSTALL_DIR%/services/logs` | | Database error and event log | `logfile` | `%INSTALL_DIR%/data` | | Application error and event log | `*.log` | `%INSTALL_DIR%/logs` | | Core module error and event log | `*.out, *log` | `%INSTALL_DIR%/core/log` | | License error and event log | `*.log` | `%INSTALL_DIR%/core/bin/SL/log` | *** ## Services Below is a table with the different application services, their description, and the dependencies required to start them. | **Name** | **Description** | **Startup dependencies** | | ----------------------- | -------------------------------------- | ------------------------ | | Editran Connect Base | Editran Connect services | Editran Connect Data | | Editran Connect Data | Database service for Editran Connect | | | Editran Connect Server | Web server for Editran Connect | | | Editran Connect Sign | Signing services for Editran Connect | Editran Connect Data | | Editran Base Service | EDITRAN protocol for file transmission | Editran License Service | | Editran License Service | Handles requests to the License V2 API | | *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/connect-3.2-en/instalacion/linux_actualizacion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.