Knowledge base

This guide is intended for developers who wish to use the ORM Propel on a hosting environment where command-line access is restricted.

Preamble

• The ORM allows linking application objects to database tables. Data is manipulated via PHP objects rather than writing raw SQL.
• Propel is the abstraction layer that manages these interactions (relations, joins, pagination) to simplify code maintenance.

Particularities & limitations

• Propel is not pre-installed via Pear.
  • You must install it manually in your project.
  • It is imperative to download the "Conventional Package" version of Propel.
• CLI commands (such as propel-gen) are not executable on the server.
  • Consequently, Propel is only used in "Runtime" mode in production. Class generation (build) must be performed locally.
  • The workflow involves generating code in a development environment and then transferring the resulting files to the server.
• Dependencies:
  • The complete set of libraries required for Propel is available, except for Phing.
  • The absence of Phing does not impact production, as this tool is only required during the local generation phase.

This guide is intended for users who have chosen Infomaniak, a hosting provider committed to the planet: you will find below the details of the calculation method used to display CO2 on invoices, as well as some tips to reduce your own digital footprint.

Introduction

• For Web Hosting and Mail services, Infomaniak displays the amount of CO2 emitted annually, a figure based on a rigorous Life Cycle Assessment (LCA) method that combines two key factors:
  1. Material impact (Full life cycle)
     • Using emission factors from the ResilioDB database, the calculation includes emissions generated during the manufacturing (BLD), transport (DIS), and end-of-life/recycling (EOL) of each piece of equipment (servers, RAM, disks, etc.).
  2. Energy impact (Actual consumption)
     • The actual electricity consumption of the servers is measured via IPMI probes.
     • This energy is then converted into CO2 equivalent using Infomaniak's specific energy mix, which is very low in carbon (11.77g CO2eq/kWh).
• The total impact is then distributed according to the customer's unit of usage (per hosted website or per mailbox).

What can you do?

If the hosting provider optimizes its infrastructure, the end-user also plays a key role. Here's how to reduce the environmental impact of your services.

For websites

The goal is to minimize the energy consumption of servers and visitors' devices:

• Technical optimization: Compress images, minify scripts, and use modern formats (WebP).
• Clean design: Limit autoplay videos, advertisements, and heavy scripts that consume bandwidth.
• Best practices: For WordPress in particular, it is recommended to consult the GreenIT guides.

For email

Email communication can also be optimized:

• Simplicity: Prefer plain text emails over HTML emails and limit the use of large, graphical signatures.
• Attachments: Prefer sending download links (via kDrive or SwissTransfer) instead of large attachments, or use compressed PDF format.
• Cleanup: Unsubscribe from unnecessary newsletters and use tracking tools to avoid sending emails that are not opened.

It is recommended to regularly monitor statistics to improve environmental performance. While waiting for Infomaniak's future integrated tools, it is possible to audit the impact of web pages via GreenFrame.io.

This guide covers website optimization, and more specifically, the use of a caching engine on your website.

Introduction

• When Infomaniak detects that your website is consuming more resources than other websites on the same server, an analysis is performed.
  • Often, it is found that a simple modification of a query or parameter would optimize your site and reduce the server load.
  • You will then be contacted by email with the instructions to follow, which frequently include the installation or activation of a caching engine.
• Resource consumption is not necessarily related to the number of visitors.
  • A well-optimized, up-to-date site with a properly configured caching engine can handle several tens of thousands of daily visitors, while a poorly optimized site can consume far too many resources with only a few visits per day.
• A cache engine temporarily stores frequently used data to provide it more quickly during new requests.
  • This significantly improves website speed and reduces the load on databases or web services.
  • To install an advanced caching system (Redis, Memcached) on Cloud Server Infomaniak, please refer to this guide.

Enable a cache engine…

… on WordPress

WordPress has many caching plugins. Here are the most popular and effective ones:

• WP Rocket (paid, the most efficient and user-friendly "all-in-one" solution).
• WP Super Cache (free, developed by Automattic, very reliable).
• LiteSpeed Cache (free, extremely comprehensive).

Standard activation procedure:

1. Log in to your WordPress administration panel.
2. Go to Extensions > Add.
3. Search for one of the plugins mentioned, install it, and then activate it.
4. Configure the cache options: page caching, CSS/JS minification, and especially Lazy Load for images.

You should also consult this other guide on the subject.

… on Joomla (v4 & v5)

1. Go to System > General Settings.
2. Select the System tab.
3. In the Cache Settings section, enable the cache (the Conservative mode is the safest to start with).
4. Select the cache manager (Default file).
5. Next, go to System > Plugins and make sure the System - Cache plugin is enabled to cache entire pages.

… on PrestaShop (v1.7 & v8+)

1. Go to Advanced Settings > Performance.
2. Smarty: check "Never recompile template files" (in production) and enable "Cache".
3. CCC (Combine, Compress and Cache): enable all options (Smart CSS cache, Smart JS cache, Apache optimization).
4. Cache: at the bottom of the page, enable "Use cache". On shared hosting, prioritize the file system; on Cloud Server, use Memcached.

… on Drupal (v9, v10 & v11)

Caching is natively integrated and very powerful in Drupal:

1. Go to Settings > Development > Performance.
2. Check "Cache pages for anonymous users".
3. Define a duration for "Maximum cache expiration in the browser and proxy" (e.g., 10 minutes).
4. Enable CSS and JavaScript file aggregation.

… on Contao (v4 & v5)

1. The cache is now managed primarily via the config/config.yaml configuration file or via the administration interface under Layout > Themes > Edit the page layout.
2. Define a "Cache expiration delay" for the page in question.
3. Use the Contao Manager to clear the production cache (Symfony Cache) after structural changes.

Check the effectiveness

After activation, test your website with these free tools:

• Google PageSpeed Insights
• GTmetrix

This guide explains how to report a phishing attemptwhich you would be a victim of.

Preamble

• Phishing is a fraud and scam attempt aimed at fraudulently obtaining sensitive information.
• Generally, the victim receives a message in their inbox that appears to be from Infomaniak, their bank, or a trusted organization, indicating that a problem has occurred with their account or in their daily life:
  
• The purpose of this identity theft is usually to get the user to voluntarily visit a page and provide private information that will then be used for various purposes, mainly financial ones.
• If it is not a “pretending to be something it is not”, but if it is simply an unsolicited advertising message, it is best to report it as Spam.

Report a Phishing Email

Prerequisites

• Check that the spam filter is active.
• For added security, enable the external email warning.

If you find an email of this type directly in your inbox, you can take action to reduce the number of these messages and eventually eliminate them from email systems:

1. Click here to access the Infomaniak Mail web app (online service ksuite.infomaniak.com/mail).
2. Open the phishing message.
3. Click on the action menu ⋮ on the right.
4. Click on Report message.
5. From the menu that appears, select Report as phishing:
   
6. Confirm sending for processing.
7. Delete the email.

Once you have clicked on Report as phishing, an email is automatically sent to Infomaniak with all the information needed to process the scam report.

In the event of a more serious problem (when the message is directly addressed to you by someone you know or a contact, and it is not a mass mailing), it is recommended to contact an organization such as report.ncsc.admin.ch.

This guide explains how to view the activity logs for files on your Infomaniak hosting server.

FTP space activity logs

To view the activity logs for your FTP space, contact Infomaniak support and request FTP logs. You will need to authenticate using the credentials for managing your web hosting.

Help with reading logs: http://www.castaglia.org/proftpd/doc/xferlog.html

The possible information_schema indication does not concern you directly.

This is an internal MySQL database that provides a summary of the information from your own databases.

This guide concerns RTMP (Real-Time Messaging Protocol), a service that allows you to stream multimedia content in real time over the Internet:

• It is a proprietary protocol developed by Adobe, and its use requires the configuration of a dedicated RTMP server or the use of RTMP hosting services.
• Viewers can access the live stream using a RTMP-compatible media player, such as VLC.

By default, RTMP is blocked by Infomaniak's security rules..

• Refer to this other guide to open the corresponding port.

This guide is for you if you receive the The web host does not exist error when visiting a website address on an Infomaniak Web Hosting service.

Introduction

• This type of error most often occurs because your domain name is not correctly linked to your website (your domain name probably points to the wrong IP address or is incorrectly configured).
  • Example: a domain abc.xyz that is incorrectly configured and points to an IPv4 address for a Starter hosting plan, and to an IPv6 address for a shared hosting plan…

Troubleshooting Domain - Website Linking Issues

To get your website back online:

• Check the DNS zone of your domain name, especially its A records.
• Correct them if necessary by indicating the IP address of your hosting.
  • Any DNS addition/modification may take up to 48 hours to propagate.

To do this, the easiest way is to use the Infomaniak DNS Diagnostic tool to automatically correct the settings, by grouping the products into the same Organisation if necessary.

This guide explains how to prevent cyber attacks and how to avoid a website hack for the website you manage.

The role of the host

Infomaniak's job is to provide quality hosting, so it is crucial to respond extremely quickly to the various attacks that any Internet actor may be subject to. Infomaniak therefore does everything possible to take the maximum of precautions against hacking, notably by keeping the different versions of the technologies used up to date.

In the event of a proven hack, if it is possible to trace back to the author and the machine has been compromised due to a security flaw on Infomaniak's part, if the integrity of the servers is at stake, Infomaniak takes matters into its own hands.

The role of the site owner and the webmaster

If the hacking of your site is your responsibility (an outdated script, a security patch that has not been applied, etc.), Infomaniak contacts you to warn you of a problem that will need to be resolved quickly. Some organizations like Saferinternet can also suspend the domain name upstream, which will deactivate the site but also the email.

Infomaniak cannot counter exploits related to a bug in your PHP code or other. If the hacking is not detected, you will generally notice the intrusion quite quickly through suspicious elements in your pages or by receiving numerous error emails.

It is therefore your responsibility to take care of the evolution of your website over time and not to let it "die" in a corner, even if it means calling on a webmaster whose job it is.

Infomaniak recommendations

1. Regularly update all your web applications (WordPress, Joomla, Drupal, ownCloud, etc.).
2. Keep the PHP version of your site on Infomaniak servers up to date.
3. Keep your site up to date by migrating to new offers when they are proposed to you.
4. ‍Add a protection system on your contact forms (captcha, etc.) and on any "recommend to a friend" tools (tell-a-friend...).
5. Regularly run an antivirus analysis of the hosting.
6. Monitor the vulnerability detection tool.
7. Remove anything you have not developed yourself and for which the author has not provided an update/correction for several months.
8. Make a regular backup of your site (refer to this other guide if you use WordPress) when everything is fine and keep it safe (as automatic backups are only kept for a few days and this is sometimes not far enough back to go back after you notice an intrusion).
9. Consult ibarry.ch.

If a problem has occurred...

1. Change the passwords of your Web applications, your FTP accounts and your databases by previously checking that no virus is on your computer.
2. Restore a backup but update immediately what can be updated as soon as the restoration is complete.
3. If you encounter a problem with third-party software, contact its publisher or a Partner and refer to the support policy as well as section 11.9 of the Infomaniak Terms of Service.

The CGID module for Apache has been disabled on shared web hosting plansfrom Infomaniak.

If necessary, you should consider upgrading to a Cloud Server if you are currently using shared web hosting. This can be done seamlessly: refer to this other guide for more information.

This guide concerns YAZ, a software library used to implement the Z39.50 protocol, an information retrieval protocol that enables communication between different library management systems (LMS) such as PMB, widely used in France.

Infomaniak for efficient library management

On Infomaniak's Web Hosting, PMB is supported and YAZ is activated by default.

However, if you encounter errors such as Call to undefined function yaz_connect(), you will need to open ports via the Manager. Port 210 is the standard port used for Z39.50 communications, but do not hesitate to consult the documentation of your applications.

For older Infomaniak hosting plans, consider changing your offer.

This guide explains how to increase the max_children value on Managed Cloud Server to increase the number of simultaneous PHP processes that can be used by your site. This will be very useful for resolving infinite page loading issues on your site.

Preamble

• By default on all hosting, the max_children limit is set to 20.
  • Although it is possible to increase this value from the Infomaniak Manager, the max_children limit is automatically adjusted based on the configuration of your Managed Cloud Server.
  • To increase this limit on shared hosting, migrate to Managed Cloud Server.
• To understand how to calculate the max_children needed as accurately as possible, refer to this article on the subject.

Increase the max_children value

Prerequisites

• Ensure that you have the necessary resources on the Managed Cloud Server.
• Ensure that all resources of the Managed Cloud Server are not being used; if it turns out that they are fully used, increasing the max_children value will have no effect (Modify Managed Cloud Server resources).
• Monitor the resources of your server, in case the resources of your server are reached, it will be necessary to check the optimization of processes and your site before considering increasing the max_children value.
• Consult the PHP error reports from the /ik-logs folder (master process php logs - file name: php-fpm.log) to check if the "max_children" limit has been exceeded... example of error: [05-Jul-2024 09:08:58] WARNING: [pool www.infomaniak.ch] server reached max_children setting (20), consider raising it

To access the management of PHP / Apache parameters of the site for which you need to increase the max_children value on Managed Cloud Server, refer to this other guide.

You will be able to...

• ... choose a new max_children value:
  

Limits depending on the server

Limit of max_children depending on the resources of the Managed Cloud Server:

This guide is for you if you want to perform vulnerability tests on your website/server hosted by Infomaniak.

Allowed and restricted

You are free to perform vulnerability tests (SQL injection, XSS, etc.), intrusion tests, or penetration tests (pentests) on your Infomaniak hosting only under the following conditions:

• between 9 AM and 5 PM CET
• from Monday to Friday
• with the minimum attack package, regardless of the software used (e.g. AppScan)
• without ever launching any DoS or DDoS attacks (Denial of Service)
• by respecting the Infomaniak Terms of Service, in particular the shared service framework

This guide explains how to optimize the caching of web resources using HTTP headers.

Introduction

• A good caching strategy can significantly improve your website's performance by avoiding the unnecessary retransmission of unchanged files.
• Web caching relies on two complementary mechanisms:
  1. The cache validity period (via the Expires header), which indicates how long a resource can be reused without contacting the server.
  2. Conditional validation (via the Last-Modified/If-Modified-Since headers), which allows you to check if a resource has changed before re-downloading it.

Configuring the cache duration with Expires

The Expires header allows you to specify a duration during which the browser can directly reuse resources from its local cache. Here's how to configure it in your .htaccess file:

1. Create or open the .htaccess file in the root directory of your website (usually in /web or /sites/domain.xyz).

2. Add the configuration for the expires module:

   <IfModule mod_expires.c>

3. Define the appropriate cache durations for each type of resource:

   ExpiresActive On
   ExpiresByType text/html "access plus 1 week"
   ExpiresByType image/jpeg "access plus 1 month"
   ExpiresByType text/css "access plus 1 month"
   ExpiresByType application/javascript "access plus 1 month"

   These directives mean that:

   • HTML pages will be cached for one week.
   • JPEG images, CSS files, and JavaScript files will be cached for one month.

   Adjust these durations according to the frequency with which your resources are updated.

4. Close the configuration section:

   </IfModule>

Conditional validation with Last-Modified

Even when a resource has expired in the cache, it is not always necessary to download it completely again. The conditional validation mechanism allows the browser to check if its cached version is still up to date. This process works as follows:

1. The server automatically sends a Last-Modified header with each resource, indicating its last modification date.
   • Apache handles this natively for static files - no additional configuration is required.

2. When the browser requests the resource again, it sends an If-Modified-Since header containing the date it has in its cache:

   GET /resource HTTP/1.1
   Host: www.example.com
   If-Modified-Since: Wed, 21 Oct 2015 07:28:00 GMT

3. The server compares this date with the actual file modification date:
   • If the file has not changed, it simply returns a 304 Not Modified code, thus saving bandwidth.
   • If the file has been modified, it returns the new version with a 200 OK code.

This guide explains why an FTP account (and most of the time Web Hosting as well) may suddenly become blocked.

Introduction

• Infomaniak uses an antivirus solution on all shared servers to combat the sending of viruses via FTP and scripts.
• The antivirus detects:
  • potential FTP account hacks
  • the intentional or unintentional sending of files (WordPress themes, fraudulent modules, etc.) containing malicious code lines or inclusions

Malicious File Detection

The antivirus scans all uploaded files smaller than 1 MB to prevent the upload of viruses, spam scripts, etc.

If a suspicious element is detected, the FTP account password is automatically changed, and the files in question on the server are locked (FTPban).

The FTP server then sends a message to the FTP client of the following type:

550 Virus Detected and Removed: botnet.infomaniak.5.UNOFFICIAL

or

550 Virus Detected and Removed: winnow.botnet.ff.trojans.15900.UNOFFICIAL

What to do if the account is blocked?

If your FTP account is suddenly blocked, you will receive an email; follow the procedure indicated in the email to resolve the issue. In particular:

• Clean up your site and analyze what you want to send to the server.
• Check if the web applications and CMS you use are up to date:
  • Most hacks are caused by security vulnerabilities in outdated web applications or weak passwords.

Resolve the problem permanently

To prevent your site from being hacked and blocked again, take the following steps:

• Update the web applications (WordPress, Joomla, etc.) and the extensions you are using.
• Remove any web applications that you are not using.
• Change the password for all your FTP accounts.
• Change the passwords to access web applications (WordPress, Joomla, etc.).
• Change the password for MySQL database users.
• Delete MySQL database users that you are not using.
• Use a different, complex password each time, with a minimum of 8 characters.
• Manually launch an antivirus scan on your hosting.
• Install and use an up-to-date antivirus program (regardless of the operating system).
• Refer to this other guide if you are looking for information on monitoring and resolving vulnerabilities in hosted scripts.

This guide details the use of Perl or Python scripts on Infomaniak hosting and the management of their modules.

Prerequisites

To run Python or Perl scripts via Apache on Cloud Server, the interpretation of files with the extensions .py and .pl is not active by default.

Using your FTP software/client or the Web FTP, add and adapt the following directive in the .htaccess file located in the folder containing your scripts:

AddHandler cgi-script .pl .cgi .py
Options +ExecCGI

Installation of additional modules

On a Cloud Server, you have the possibility to install third-party libraries that are not present by default.

Python

• The installation is done through PIP, which is a package manager used to install and manage packages written in Python.
• Infomaniak offers PIP and PIP3 via the Fast Installer tool.
• Once PIP is installed, you will be able to install Python modules by specifying --user during the command. For example:

• pip3 install mysql-connector-python --user

Perl

• The addition of Perl modules is also done via SSH (console). It is necessary to install them in the user directory and to define the full path within the scripts.

Important technical information

• Interpreter Path: /usr/bin/python
• Extensions: Scripts must have the extension .pl, .cgi or .py.
• Limitations: The mod_python module is not supported.

Error Resolution (CGIWrap)

If you encounter the following error when loading an image:

CGIWrap Error: Execution of this script not permitted
Request Data:Extra Path Info: /dossier/.../image.PL.12.34.gif

The server interprets the file as a script because it contains ".PL" (or .PY) in its name.
Solution: Simply rename the file to remove this mention (example: image-12-34.gif).

This guide explains how to resolve an issue when importing a .csv file into a MySQL table. The proposed alternative is to read the CSV file line by line using PHP and insert the data into the MySQL database.

"LOAD DATA LOCAL INFILE" function disabled

The LOAD DATA LOCAL INFILE function allows you to import a CSV file directly into a MySQL table. However, this feature is often exploited by attackers to gain unauthorized access to websites hosted on servers that allow it.

To prevent any security risks and protect customer data, Infomaniak has disabled the LOAD DATA LOCAL INFILE function. Users who import their CSV files via phpMyAdmin (without checking the “CSV via LOAD DATA” option) are not affected.

Here is an alternative method for importing data in CSV format into a MySQL table. The example below shows how to properly handle errors when opening the CSV file and inserting data into the database.

This script uses mysqli to connect to the database and prepared statements to insert the data. This ensures better security, optimal compatibility with recent versions of PHP, and simple integration into your project, whether in an existing script or a new file located in the /web directory:

$fileName = "data.csv";

// Connect to MySQL database using mysqli
$link = new mysqli("localhost", "username", "password", "database");

// Check database connection
if ($link->connect_error) {
   die("Connection failed: " . $link->connect_error);
}

// Open the CSV file for reading
if (($handle = fopen($fileName, "r")) !== FALSE) {

   // Read each line of the CSV file
   while (($data = fgetcsv($handle, 1000, ";")) !== FALSE) {

       // Prepare the SQL query dynamically
       $query = "INSERT INTO `test` VALUES (" . str_repeat('?,', count($data) - 1) . "?)";
       $stmt = $link->prepare($query);

       // Check if query preparation was successful
       if ($stmt === FALSE) {
           die("Query preparation failed: " . $link->error);
       }

       // Bind parameters (assuming all columns are strings)
       $types = str_repeat('s', count($data));
       $stmt->bind_param($types, ...$data);

       // Execute the query
       if (!$stmt->execute()) {
           die("Query execution failed: " . $stmt->error);
       }

       // Close the statement
       $stmt->close();
   }

   // Close the CSV file
   fclose($handle);

} else {
   echo "Error: unable to open the file.\n";
   exit(1);
}

// Close the database connection
$link->close();
?>

Get help

Unfortunately, it is impossible to specify exactly where in the script these lines of code should be inserted.

If this method causes problems (for example, when importing multiple CSV files simultaneously without any error messages), the structure of the tables or the indexing of the fields may be the cause. In this case, contact your webmaster for verification.

Also, consult the official PHP documentation regarding the fgetcsv() function.

This guide helps you protect the reputation of your domain name, to maintain the trust of internet users and service providers in your website or business, thereby facilitating the proper functioning of your email service.

Web reputation

There are different types of online reputation, including personal reputation, corporate reputation, and domain reputation.

Domain reputation is essentially a score that determines how email systems decide what to allow into users' inboxes. In essence, your domain reputation is a measure of the health and legitimacy of your domain. This reputation can be influenced by the security of your email and website.

For example, a domain's reputation may decrease if…

• … the website accessible at the domain's address is hacked, leading to the mass sending of fraudulent emails,
• … the domain's email service is being used to send unsolicited spam.

If your domain's reputation remains poor, your emails may be marked as spam and may not reach their intended recipients. This can harm email deliverability (see this other guide in English for more information).

Improve your domain reputation

By following these tips, you can improve your domain's reputation and, for example, boost all your email marketing efforts:

• Set up and verify SPF, DKIM, and DMARC records to help protect your domain against spoofing attacks.
• Check your domain's reputation using tools such as Google Postmaster Tools, Sender Score, Microsoft SNDS, McAfee, or Talos Intelligence, and identify any potential issues.
• Only send emails to users who have chosen to subscribe!
• Get trusted links or backlinks…

Refer to this other guide about RBLs.

This guide explains how to obtain the EPP code for your domain name with Hostpoint to transfer it to Infomaniak.

Preamble

• The terms "EPP", "AuthCode", "AuthInfo", "transfer code" and "authorization code" all refer to alphanumeric sequences specific to the domain whose main purpose is to verify the owner's authorization before a transfer between Registrars.
• Refer to the main guide regarding the rest of the transfer procedure.
• ⚠️ This is about transferring a domain name that you own with a different provider than Infomaniak, so that the future management of this domain is done with Infomaniak; this is therefore not an internal transfer from one holder to another and the code to be obtained is therefore not a code for an internal transfer with your current provider.

Transfer the domain name to Infomaniak

To obtain the authorization code with the current provider:

1. Refer to the complete procedure provided by Hostpoint to obtain the code and keep it safe.
2. Once the authorization code is obtained, refer to the main Infomaniak guide regarding the rest of the domain name transfer procedure.

This guide will help you if, for example, you want to deploy a package like pymysql and it requires a Python version higher than the default version offered on your hosting.

Introduction

• Anaconda is a free and open-source distribution of the Python and R programming languages; it aims to simplify package management and deployment.
• It is recommended to use Miniconda (a lightweight version of conda); it installs in your user space, avoiding any conflicts with the system Python and not requiring administrator privileges.
• Refer to the official documentation.

1. Download the installer

For example, the Linux 64-bit version for Python 3.11.

2. Verify integrity (SHA256 hash)

2. Contrôler l'intégrité (Hash SHA256)

user@server:~$ sha256sum Miniconda3-py311_23.10.0-1-Linux-x86_64.sh
6c714a33ea348303f909194246990422e698889417d74b9714856b3e9a7e6c3a  Miniconda3-py311_23.10.0-1-Linux-x86_64.sh
3. Start the installation

3. Lancer l'installation

The -b argument enables a silent installation. By default, Miniconda will be installed in ~/miniconda3.

user@server:~$ bash Miniconda3-py311_23.10.0-1-Linux-x86_64.sh -b
PREFIX=/home/clients/your_client_hash/miniconda3
Unpacking payload ...
Collecting package metadata (current_repodata.json): done
Solving environment: done
Executing transaction: done
installation finished.

4. Initialize and activate Conda

To use conda immediately and with each SSH connection:

user@server:~$ ~/miniconda3/bin/conda init bash
no change     /home/clients/your_client_hash/miniconda3/condabin/conda
...
modified      /home/clients/your_client_hash/.bashrc

user@server:~$ source ~/.bashrc

5. Install a package (example: pymysql)

Once activated, the prefix (base) appears before your command prompt. You can then install your tools without using sudo or --user.

(base) user@server:~$ python -V
Python 3.11.5

(base) user@server:~$ pip install pymysql
Collecting pymysql
  Downloading PyMySQL-1.1.0-py3-none-any.whl (44 kB)
Installing collected packages: pymysql
Successfully installed pymysql-1.1.0