EN Ikoula wiki - User contributions [en]

How do I install my SSL certificate on my shared hosting?

2023-09-26T16:09:46Z

Ikbot: Created page with "<span data-link_translate_fr_title="Comment installer mon certificat SSL sur mon hébergement mutualisé" data-link_translate_fr_url="Comment installer mon certificat SSL sur..."

[[:fr:Comment installer mon certificat SSL sur mon hébergement mutualisé]][[fr:Comment installer mon certificat SSL sur mon hébergement mutualisé]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Array|here]]. 

{{#seo:
|title=How do I install my SSL certificate on my shared hosting?
|title_mode=append
|keywords=these,are,your,keywords
|description=This article explains how to install your SSL certificate on your shared hosting.
|image=Uploaded_file.png
|image_alt=Wiki Logo
}}

==Introduction==

You have a '''''[https://www.ikoula.com/fr/certificats-ssl SSL certificate]''''' for your website and you want to install it on your shared hosting.
You can do this via your Plesk interface.

We also invite you to consult this article with other procedures for a ...
Free "let's encrypt" certificate https://fr-wiki.ikoula.com/fr/Comment_installer_un_certificat_Let%27s_encrypt_depuis_mon_acc%C3%A8s_Plesk_%3F

==Course==

Log in to your Plesk management interface: [https://fr-wiki.ikoula.com/fr/Acc%C3%A8s_%C3%A0_l%27interface_de_gestion_(Plesk)_de_mon_h%C3%A9bergement Here is the procedure]

In the top left-hand menu, click on '''Websites & Domains''' then click on '''SSL/TLS Certificates'''

[[Image:SSL1.PNG]]

Then click on the "Advanced settings" tab. You will find yourself on a page where a certificate has already been added. This is normal, as when you order your certificate, we issue the CSR and the key from here.

'''DO NOT DELETE!'''

You have two choices:

*Click on '''Choose a file''' and add your .crt file

[[Image:SSL2.PNG]]

*Click on the certificate already displayed and add the certificate in the zone you want (Send certificate files or Send certificate in text mode).

[[Image:SSL3.PNG]]

Once you have added your certificate to your hosting, you need to configure it so that it secures your site.

To do this, go back to '''Websites & Domains and click on '''Hosting settings'''

[[Image:SSL4.PNG]]

In the Security section, you can select your certificate.

[[Image:SSL5.PNG]]

Then click on '''Apply''' and '''OK'''. Your site is now secure.

[[Category:Shared hosting]]

Updating Wordpress and its components

2023-07-11T14:06:34Z

Ikbot: Created page with ":fr:Mettre a jo..."

[[:fr:Mettre a jour Wordpress et ses composants]][[fr:Mettre a jour Wordpress et ses composants]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Mettre a jour Wordpress et ses composants|here]]. 


==Introduction== 
The aim of this guide is to teach you how to update your version of Wordpress, your plugins and your themes.

==Prerequisites== 
The first step is to access your Plesk control panel. 
Here's the KB to show you how: https://fr-wiki.ikoula.com/fr/Acc%C3%A8s_%C3%A0_l%27interface_de_gestion_(Plesk)_de_mon_h%C3%A9bergement

==Course== 

Once you are connected to Plesk, you can first check whether an update is available for Wordpress or a component associated with it. 
If this is the case, click on your domain name to the right of the Wordpress logo.

[[File:Wpupdate-1.PNG|600px]] 

'''You will then have two options: manual or automatic installation'''.

===Manual installation===

You should then click on '''Install Wordpress/plugin/theme updates''', whichever you choose, all 3 will be offered to you.

[[File:Wpupdate-2.PNG|600px]] 

Once you have arrived at this interface, you need to select the updates of your choice by ticking them, then click on '''Update''' in the top left-hand corner.

[[File:Wpupdate-3.PNG|700px]] 

===Setting up automatic updates===

If you want your site to always have the latest versions available, you can activate automatic updates.

To activate it, go to the tab of your choice among the three, then activate the option '''Autoupdate''' for all your plugins and themes.

[[File:Wpupdate-4.PNG|900px]]

==Conclusion== 
Your version of Worpdress, your plugins and your themes are now fully up to date.



 
Did you find this article useful? <vote />




<comments />


[[Category:Mutualised_housing]][[Category:plesk]] [[Category:Web hosting]][[Category:WordPress]]

Configuring a Mac OS Mail client for shared hosting

2023-07-11T10:38:01Z

Ikbot: Created page with "<span data-link_translate_fr_title="Configuration d'un client Mail sous Mac OS pour un hébergement mutualisé" data-link_translate_fr_url="Configuration d'un client Mail sou..."

<span data-link_translate_fr_title="Configuration d'un client Mail sous Mac OS pour un hébergement mutualisé" data-link_translate_fr_url="Configuration d'un client Mail sous Mac OS pour un hébergement mutualisé">[[:fr:Configuration d'un client Mail sous Mac OS pour un hébergement mutualisé]][[fr:Configuration d'un client Mail sous Mac OS pour un hébergement mutualisé]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Array|here]]. 
{{#seo:
|title=Setting up Mail on Mac OS for shared hosting.
|title_mode=append
|keywords=MacOS,mail,Mac,Apple
|description=This article explains how to set up Mail on Mac OS for shared hosting.
|image=Uploaded_file.png
|image_alt=Wiki Logo
}}

== Introduction ==
You will find below the different screens as well as the different parameters to be entered in order to configure '''Mail'''the Mac OS mail client.

== Add an account ==
In your Mac's settings menu, you'll find the "Internet Account" menu. Go to this menu.

[[File:macpj1.png|center|border 2px]]

For shared hosting, select "Mail Account".

[[File:macpj2.png|center|border]]

== Configure your account ==

The next step is to set up your account.

Here is the list of settings you need to enter:

[[File:macpj3.png|center|border]]

 '''E-mail address''' E-mail address you have created in the Plesk interface of your Shared Hosting.
 '''User name''' Also the e-mail address you created in the Plesk interface.
 '''Password '''The password for your e-mail address.
 '''Account type '''Account type: IMAP or POP.
 ''IMAP '': The IMAP protocol lets you store messages on the server and access them on all your devices whenever you want.
 ''POP'': The POP protocol allows you to delete messages and attachments from the server once you have received them on your device.
 '''Receiving server''' mail.yourdomain.tld: this is your domain, preceded by "mail.
 '''Sending server''' Mail server: mail.yourdomain.tld, this is your domain, preceded by "mail.

 On new versions of Plesk, it is possible to set up autodiscover, so that you don't have to fill in the ports. To do this, go to the interface '''Plesk > Mail > Mail Settings > Tick enable mail autodiscover'''.
 
 ''Note: In the same menu, tick DKIM too. This will already be done.''

 If autodiscover is not used, you will need to fill in the following ports:

 '''Incoming IMAP''' 993 / SSL/TLS
 '''Incoming POP''' POP : 995 / SSL/TLS
 '''Outgoing''' : 465 / SSL/TLS

 Finally, this window will be displayed once the settings have been made and validated.

[[File:macpj4.png|center|border]]

 You can add a name and description here to identify the account you have just created.

== Conclusion ==

 We have seen throughout this article how to set up the Mail client (MAC OS) for shared hosting.

[[Category:Mail]]
[[Category:Mutualised_housing]]
[[Category:Mac OS]] [[Category:Web hosting]]
 
<comments />

Create a contact account

2023-07-04T06:18:09Z

Ikbot: Created page with ":fr:Créer un compte contactfr:Créer un comp..."

[[:fr:Créer un compte contact]][[fr:Créer un compte contact]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Créer un compte contact|here]]. 


==Introduction== 
A contact account is a secondary user that you can add to your customer area.
This system allows you to limit access to your contact according to your needs.

==Course== 

First you need to log in to your Ikoula customer area: https://commande.ikoula.com/
Then click on '''My account''' then '''Contacts'''.
Once on this page you must click on '''Add a new contact'''.

[[File:GestionUtilisateurs01.PNG|1200px]]

Now you need to fill in the information about your new contact. You must fill in all the fields with an "*" otherwise it won't work.
Please note! You cannot use an email address or telephone number that is already in use for another customer account.
Once you have filled in the necessary information and selected the rights you want, click on '''Envoyer'''

[[File:GestionUtilisateurs02.PNG|1200px]]

You now have a contact account.
You can modify or delete it at any time by clicking on the cogwheel. 

[[File:GestionUtilisateurs03.PNG|1200px]]

==Conclusion== 
You now have new contact accounts to manage your customer account.



 
Did you find this article useful? <vote />




<comments />


[[Category:Interface]]

Run an FSCK on your server

2023-06-25T03:34:19Z

Ikbot: Created page with ":fr:Effectuer un FSCK sur v..."

[[:fr:Effectuer un FSCK sur votre serveur]][[fr:Effectuer un FSCK sur votre serveur]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Array|here]]. 


{{#seo:
|title=Run an FSCK on your server
|title_mode=append
|keywords=these,are,your,keywords
|description=Read this article to find out how to run an FSCK on your server.
|image=Uploaded_file.png
|image_alt=Wiki Logo
}}
==Introduction: What is FSCK?== 
FSCK is the integrity check and repair tool for Linux file systems. This command is useful when you encounter problems with your OS: instability, crashes, etc.

==Prerequisites== 
First of all, it's important to have a backup (this step is not compulsory, but strongly recommended). To do this, we recommend our Acronis : https://www.ikoula.com/fr/acronis-cloud-backup

Secondly, you will need to launch a netboot on your server. The way you do this depends on whether your server is virtualised or not.

* For a physical server, you need to go to the extranet interface (extranet.ikoula.com) and request a netboot using the button provided.
* If it's a virtualised server, you have two other options:
** On Hyper-V2 (Windows Server 2008), simply change the system boot image by choosing a Sysrescue CD, then reboot.
** On Hyper-V3 (Window Server 2012), as it is no longer possible to change the image on which to boot, you will need to contact technical support by ticket so that they can mount this image on your server.
** For more information on virtual server netbooting, please consult this article : [[Netboot sur serveur flex]]

Finally, if you would like more information on netbooting in general, we recommend this article [[Qu’est ce que le netboot et comment le lancer]]

==Course== 
Once the prerequisites have been met, it will be useful to detect the partitions. '''Be careful not to mount partitions'''.

It will then be possible to run FSCK on the desired partition. For example, here is what the syntax would look like on the partition /dev/sda1

<code> fsck -y /dev/sda1 </code> The -y argument is used to directly validate the corrections made by FSCK. If this argument is not present, you will have to manually validate the changes made by FSCK.

The system will then return a report like this:
 
 
<code> Passe 1 : vérification des i-noeuds, des blocs et des tailles
 I-noeud 2392126, i_size est 77055, devrait être 110592. Corriger<o>? oui
 I-noeud 2392126, i_blocs est 192, devrait être 224. Corriger<o>? oui
 Passe 2 : vérification de la structure des répertoires
 Passe 3 : vérification de la connectivité des répertoires
 Passe 3A : optimisation des répertoires
 Passe 4 : vérification des compteurs de référence
 Passe 5 : vérification de l'information du sommaire de groupe
 /dev/sda1: ***** LE SYSTÈME DE FICHIERS A ÉTÉ MODIFIÉ *****
 /dev/sda1: 68816/6750208 files (0.9% non contigus), 12039728/13492584 blocs </code>
 
 

FSCK will correct any anomalies it encounters at that time.

==Conclusion== 
So you can now launch an FSCK via a netboot to correct system errors and problems.



 
Did you find this article useful? <vote />




<comments />

 [[Category:FLEX]] [[Category:Dedicated server]]

Performance test via a netboot

2023-03-13T20:34:50Z

Ikbot: Created page with ":fr:Test de performance via u..."

[[:fr:Test de performance via un netboot]][[fr:Test de performance via un netboot]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Array|here]]. 
{{#seo:
|title=Performance test via a netboot
|title_mode=append
|keywords=these,are,your,keywords
|description=Discover in this article how to perform a performance test via a netboot
|image=Uploaded_file.png
|image_alt=Wiki Logo
}}

<center>[[File:Ico_Ded.png| 100px]] [[File:ROUAGEikl-12-2021.png| 100px]] </center>

When using your [https://www.ikoula.com/fr/serveur-dedie dedicated server]you may need to boot your server on a backup system called ''' Netboot '''.
Netboot, commonly known as SystemRescue, is an open source operating system, designed to be used without installation to allow administration, restoration or repair of an already installed system on a desktop, laptop or computer server.
Among other things, it allows operations to be performed on a system that no longer boots in normal mode. It completely isolates the equipment from the existing configuration.

In this article, you will find useful commands to test your hardware.

=== Launching the Netboot ===

To start your dedicated server in this mode, vous devez vous connecter à votre [https://extranet.ikoula.com/ Extranet] 
Go to "Serveur physique" and choose the server you are interested in.

Then in the list of features go to Netboot.

[[File:Lancement_netboot.png]]

 ''' /!\ Pour rappel, les informations de connexion au serveur en Netboot sont les identifiants reçus lors de la livraison de votre serveur /!\ ''' 

=== Check the temperature ===

The command '''sensors''' command allows you to display the processor's temperatures.

During the various performance tests, it may be useful to run the

 '''watch sensors''' 

This command will continuously monitor the machine's processor temperatures.

=== Check the integrity of the processor ===

The command '''stress''' command will stress the processor. Thus, the command

 '''stress --cpu 8 --io 4 --vm 2 --vm-bytes 128M --timeout 60m''' 

command will work the processor and memory and test your I/O for 60 minutes.

This is the '''--timeout''' option that will set the stress time.

If the test stops unexpectedly in full operation, the processor is no longer able to bear the load and/or is getting too hot.

----

=== Check the health of the hard disk ===

Before performing this test, the structure of the disks must be known.

The command '''fdisk -l''' command allows you to consult the partitions present, their types, their locations and their sizes.

[[Fichier : Disk_lvm.PNG | 500px ]]

----

=== Check the health of SATA drives ===

The command '''smartctl''' command allows you to perform a complete test of your hard disk. The following command:
 '''smartctl -d ata -a -f old /dev/<disque>''' 

allows you to have all the useful information about your disk and its current state.

To test your hard disk, run the command:
 '''smartctl -t short /dev/<disque>''' 
Replace ''short'' with ''long'' for a longer and more complete test.

''''' /!\ Replace /dev/<disque> with the name of your disk (/dev/sda, /dev/sdb, etc...) /!\ '''''

----

=== Check the health of the NVME disk ===

Always with the command '''smartctl'''command, the following command:

 ''' smartctl -a /dev/nvme0n1''' 

will also give you all the information you need about your NVME and its current status.

At the end of the test, you will receive a detailed report of the test.

== Check RAM memory ==

This is the '''memtester''' command, which will test the integrity of your memory. It is preferable to test the entire memory capacity of your machine.

To do this, type the command:
 '''memtester 16g 2 '''
where you replace 16g with the amount of memory you have (g for giga) and the 2 indicates the number of times the test should be performed.

----

If you have encountered any difficulties in following this article, or if you would like to provide any information about it, our technical support team is at your disposal:

* 24h/24 et 7j/7 par ticket depuis votre Espace client
* Du lundi au vendredi de 9h à 19h au 01 84 01 02 50


[[Category:netboot]]
[[Category:Dedicated server]]

Installing a Let's Encrypt certificate

2023-03-03T16:08:38Z

Ikbot: Created page with ":fr:Installat..."

[[:fr:Installation d'un certificat Let's Encrypt]][[fr:Installation d'un certificat Let's Encrypt]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Installation d'un certificat Let's Encrypt|here]]. 
== The free SSL certificate from Let's Encrypt ==

<center>[[File:LetsEncrypt.png | 500px]]</center>

The Let's Encrypt extension of Plesk allows you to secure your server with free SSL/TLS certificates from Let's Encrypt, a free and open source Certificate Authority. 
You can secure the mail server, as well as any hosted domain, subdomain and domain alias. 
Securing your server with Let's Encrypt certificates is quick and easy. It only takes a few clicks from the Plesk interface. 
The Let's Encrypt extension automatically keeps all issued certificates up to date.

== Requirements for the installation of the certificate == 

To install a Let's encrypt SSL certificate, there are certain prerequisites:

* The domain name must point to the IP address of the hosting
* The site must be reachable
The domain name must point to the IP address of the hosting * The site must be reachable * Know the service that manages the DNS zone for your domain name

Votre zone DNS peut être gérée par un service dans votre espace client Ikoula ou encore par service Plesk de l'hébergement.

To find out which service manages the zone, the site [https://dnschecker.org/ DNS Checker] references the names of the servers.
You must enter the domain name in the field provided for this purpose and select the NS field.

[[File:Dns_checker.png | 500px]]

''The DNS zones managed on Plesk have as name servers : ''

ns1.ikoula.nl
ns2.host2vps.com
linhebXX.ikoula.com (for a Linux server)
winhebXX.ikoula.com (for a Windows server)

'' The DNS zones managed by the client space have name servers : ''

ns4.ikoula.com
ns5.ikoula.com

== Setting up the certificate on a domain managed by Plesk == 

You need to be connected to the Plesk interface to perform these operations. [[ Accéder à mon interface Plesk ]]

In the Web Site and Domains tab, go to ''SSL/TLS Certificates'''

[[File:Plesk_SSL.png | 1000px ]]

Then select ''Install a free basic certificate provided by Let's Encrypt'''

[[File:Plesk_LetsEncrypt.png]]

A new page will open and you will have to enter a valid e-mail address if you have not done so.

[[File:Plesk_Secure.png]]

Activate the desired options.

* Secure the domain name
This option can be disabled if the site is managed externally and you want to use the SSL certificate only for the email service.

* Protect the Wildcard domain (including www and webmail)
If you use subdomains and want to protect them with the same certificate as well.

This option allows the automatic creation of a TXT record in the DNS zone.

It is only available if the domain's DNS zone is administered in Plesk.

* Enable the option "protect the www subdomain for the domain and all selected aliases".

* If necessary, enable the "Protect webmail on this domain" option.
This way, the webmail will also be secured.

* Assign the certificate to the mail domain

''Once these steps have been completed, it takes 10 to 30 minutes for DNS replication.''

Une fois ce délais écoulé, il faut cliquer sur "Recharger" et le certificat sera généré.''

== Setting up the certificate on a domain managed by the Customer Centre == 

The installation of the Let's Encrypt certificate will not be very different from the previous steps.

Unlike the DNS zone managed on the Plesk server, the DNS entries are not automatic and must be entered manually from your [https://commande.ikoula.com/ Customer area ]

[[File:Plesk_Wildcard.png]]

In the Dns Management Migrated service, choose your domain name to access the DNS zone management.

You then need to create a TXT field for the domain '_acme-challenge.yourdomainname.tld' with the content requested by Plesk.

Here you need to add the record ''tiDYhh0klLPltq_lPAeKb9jmuxsUyZ-1WWnUXQnJX-s''

[[File:DNS_Plesk_SSL.png]]

Before reloading the emission request, it is necessary to check the good propagation of the record '_acme-challenge.votrerenomdedomaine.tld'.

''Once these operations have been carried out, it takes 10 to 30 minutes for the DNS replication.''

The website [https://dnschecker.org/ DNS Checker] site also references the TXT records.

You must enter _acme-challenge.yourdomainname.tld and choose the TXT option

Une fois ce délais écoulé, il faut cliquer sur "Recharger" et le certificat sera généré.''

== Renewal of the certificate ==

Certificate renewal is automatic if the DNS zone is managed by PLESK, otherwise the certificate must be renewed every 3 months.

If you wish to opt for an automatic renewal and your zones are managed by your customer area, you can contact the technical support to request a migration to a more recent server.

If you have encountered any difficulties in following this article, or if you wish to provide any information concerning it, our technical support is at your disposal:

* 24 hours a day, 7 days a week by ticket from your Customer Area


[[Category:Web hosting]]

How to reset your customer account password

2023-01-20T15:43:41Z

Ikbot: Created page with "<span data-link_translate_fr_title="Comment réinitialiser son mot de passe de compte client" data-link_translate_fr_url="Comment réinitialiser son mot de passe de compte cl..."

[[:fr:Comment réinitialiser son mot de passe de compte client]][[fr:Comment réinitialiser son mot de passe de compte client]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Comment réinitialiser son mot de passe de compte client|here]]. 
== Can't connect to your ikoula interface? ==

=== Here is the procedure for resetting your password. ===

You will have to go to the ikoula interface:

https://commande.ikoula.com/

*1) You must click on Connection

[[Fichier:KBMDP1.PNG|1400px]]
 
 
 
 

*2) Click on Forgot your password?

[[Fichier:KBMDP2.PNG|1400px]]
 
 
 
 

*3) You must enter your email address in the box (1) and then click on Send me my password (2)

[[Fichier:KBMDP3.PNG|1400px]]
 
 
 
 

*4) You will receive a verification link in your mailbox, you will have to click on it.
 
This will take you to a standard login page.
 
[[Fichier:KBMDP4.PNG]]
 
 
 
 
'''However''', you will receive a 2nd email with the login details to be changed thereafter '''for more security'''.

[[Fichier:KBMDP5.PNG]]
 
 
 
 

=== And finally ===

You must change this by following the procedure below:

https://fr-wiki.ikoula.com/fr/Comment_changer_son_mot_de_passe_de_compte_client
 
 
 
 

[[Category:Customer area]]
[[Category:Interface]]

Reinstalling GRUB from a Netboot

2022-11-25T08:07:23Z

Ikbot: Created page with ":fr:Reinstallatio..."

[[:fr:Reinstallation de GRUB depuis un Netboot]][[fr:Reinstallation de GRUB depuis un Netboot]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Reinstallation de GRUB depuis un Netboot|here]]. 


This documentation explains the procedure for reinstalling GRUB from a Netboot

< style="background-color: #e78581;">
 /!\ Le montage des partitions peut entraîner une perte de données. Faites attention à la dangerosité de vos manipulations. /!\ 
</div>

==Launching the netboot == 
The netboot is a network boot mode on a Linux light image that allows, among other things, to perform operations on a system that no longer boots in normal mode.

From your extranet interface, you have the possibility to launch it on your machine.

You can also use this documentation: [[Qu’est ce que le netboot et comment le lancer]]

== Orders to be carried out == 
Once your netboot is effective on your server, you will have to follow the following commands:

fdisk -l # to help you find the partition where your ubuntu is
mount /dev/sdaX /mnt # mount it by replacing the X with the correct partition number
mount --bind /dev /mnt/dev # symbolic link from the current /dev folder to the mounted disk
mount --bind /dev/pts /mnt/dev /pts # symbolic link from the current /dev/pts folder to the mounted disk
mount --bind /sys /mnt/sys # symbolic link from the current /sys folder to the mounted disk
mount -t proc /proc /mnt/proc # For Grub2 to find /proc/mounts
chroot /mnt /bin/bash # root the mounted disk
mount -a # mount partitions in chroot
apt-get install grub-pc # install Grub2 software (on the now-rooted disk)
update-grub # create a new configuration file: grub.cfg
grub-install --force /dev/sda # install grub on MBR

Now you just have to unmount the partitions mounted in the chroot:

umount -a

From here, you can exit the mounted disk by pressing ctrl+D. Then, unmount this disk:

sudo umount /mnt/{dev/pts,dev,sys,proc}
sudo umount /mnt

All you have to do is reboot your machine.

''Source : [https://doc.ubuntu-fr.org/tutoriel/comment_restaurer_grub#comment_reinstaller_grub How do I reinstall GRUB?]''


[[Category:Dedicated server]]

Change the OS of your dedicated server

2022-08-01T10:42:24Z

Ikbot: Created page with ":fr:Changer l'OS de vot..."

[[:fr:Changer l'OS de votre serveur dédier]][[fr:Changer l'OS de votre serveur dédier]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Changer l'OS de votre serveur dédier|here]]. 


=Introduction=

This article will show you how to change the OS of your dedicated server.

=Requirements=

==From your customer area==
Log in to your customer account: https://commande.ikoula.com/clientarea/

=Proceedings=

Once in your customer area go to my account =>

[[File:clientespace.PNG]]

Then click on the management tab of your server.

[[File:Gestion.png]]

Then on operating system click on update/upgrade.

[[File:Système.PNG ]]

Then choose your desired OS.

Note that once the OS is changed a reset will be launched on your server.

Remember to make a backup of your data.

If you have encountered any difficulties in following this article, or if you wish to provide any information about it, our technical support is at your disposal:

24 hours a day, 7 days a week by ticket from your Customer Area
Monday to Friday from 9am to 7pm on 0892 350 503

[[Category:Client Interface]] [[Category:Dedicated server]]

How do I allow file extensions on my Windows Plesk?

2022-07-15T04:31:20Z

Ikbot: Created page with "<span data-link_translate_fr_title="Comment autoriser des extensions de fichiers sur mon Plesk Windows ?" data-link_translate_fr_url="Comment autoriser des extensions de fich..."

[[:fr:Comment autoriser des extensions de fichiers sur mon Plesk Windows ?]][[fr:Comment autoriser des extensions de fichiers sur mon Plesk Windows ?]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Comment autoriser des extensions de fichiers sur mon Plesk Windows ?|here]]. 


==Introduction== 
This article explains how to allow a new file extension to run on your Plesk hosting on Windows.

==Prerequisites== 
You will first need to access your Plesk control panel. 
Here is the KB that will show you how to do this: https://fr-wiki.ikoula.com/fr/Acc%C3%A8s_%C3%A0_l%27interface_de_gestion_(Plesk)_de_mon_h%C3%A9bergement

==Course== 
* From your Plesk control panel, click on '''Virtual Directory'''.

[[File:TypeMIME1.PNG|1000px]] 

* Then you can click on the '''MIME Types tab'''.

[[File:TypeMIME2.PNG|800px]] 

* Once on this page click on '''Add MIME Type''' then you can fill in the fields and add the extension of your choice.

[[File:TypeMIME3.PNG|200px]] 

* If you make a mistake you can remove it by selecting it and clicking on '''Remove'''

[[File:TypeMIME4.PNG]] 

==Conclusion== 

You now know how to add file extensions to your Windows Plesk.



 
Cet article vous a semblé utile ? <vote />




<comments />


[[Category:Mutualised_housing]][[Category:plesk]] [[Category:Web hosting]]

Access my Direct Admin interface

2022-06-27T08:22:38Z

Ikbot:

[[:nl:Toegang tot mijn Direct Admin interface]][[nl:Toegang tot mijn Direct Admin interface]]
[[:fr:Accéder à mon interface Direct Admin]][[fr:Accéder à mon interface Direct Admin]]
[[:en:Access my Direct Admin interface]][[en:Access my Direct Admin interface]]

{{#seo:
|title=Accéder à mon interface Direct Admin
|title_mode=append
|keywords=Direct Admin,interface,shared hosting,HEB,hosting
|description=In this article, you will see the procedure to access your interface Direct Admin.
|image=Uploaded_file.png
|image_alt=Wiki Logo
}}

===Introduction===
In this article, you will see the procedure to access your interface '''Direct Admin'''.

===Customer Area===
To begin, you will have to connect to your '''customer area''', you can do it by this link : https://commande.ikoula.com/clientarea/

If you can not connect, do not hesitate to click on '''Forgot your password''' in case of password error.

Otherwise you can also retry to connect by '''private navigation''', or by changing '''browser'''.

If it is functional by this method, you will have to '''empty the cache and delete the cookies''' of your main browser.

<div> Otherwise you will have to contact directly the technical support : '''support@ikoula.com'''</div>

===Access Direct Admin===

Once on your customer interface, you must go to '''Directadmin Hosting''' and select your service by clicking on '''Management'''.

[[File:DirectAdmin-EspaceClient.png|1100px]]

Once on the '''administrative management''' part of your hosting, you can access the Direct Admin control panel by clicking on '''Access Control Panel'''

[[File:DirectAdmin-ControlPanel.png|1100px]]

===Direct Admin===

You will get the '''connection interface''' of your hosting, you must connect with the associated identifiers.

[[File:DirectAdmin-Connexion.png]]

Otherwise, it is also possible to connect via a '''direct link''' depending on the host server where your hosting is located: https://ikdirectadminXX.ikoula.com:2222/


 

Did you find this article useful? <vote />


<comments />

[[Category:Directadmin]] [[Category:Shared hosting]] [[Category:Customer area]]

How to change the operating system of my dedicated server

2022-06-23T05:23:27Z

Ikbot:

[[:es:Cómo cambiar el sistema operativo de mi servidor dedicado]][[es:Cómo cambiar el sistema operativo de mi servidor dedicado]]
[[:fr:Comment changer le systeme d exploitation de mon serveur dedie]][[fr:Comment changer le systeme d exploitation de mon serveur dedie]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Array|here]]. 


{{#seo:
|title=How to change the operating system of my dedicated server
|title_mode=append
|keywords=these,are,your,keywords
|description=How to change the operating system of my dedicated server
|image=Uploaded_file.png
|image_alt=Wiki Logo
}}

==Introduction== 
I want to change the OS of my dedicated server

==Course== 
To change the OS of your dedicated server you need to : 
- Connect to your customer area: https://commande.ikoula.com/clientarea 
- Go to the "Dedicated Servers" tab and choose the server on which you want to change the OS 
- In the Service Details, click on Update/Upgrade next to Operating System 

[[File:ChangeOS.PNG]] 
[[File:Capture2.PNG]] 

==Conclusion== 
The process will then start automatically. You can follow the progress of your reset from the Extranet: https://extranet.ikoula.com



 
Cet article vous a semblé utile ? <vote />




<comments />



[[Category:Dedicated server]]

How to change the operating system of my dedicated server

2022-06-23T05:22:06Z

Ikbot: Created page with "<span data-link_translate_fr_title="Comment changer le systeme d exploitation de mon serveur dedie" data-link_translate_fr_url="Comment changer le systeme d exploitation de m..."

[[:fr:Comment changer le systeme d exploitation de mon serveur dedie]][[fr:Comment changer le systeme d exploitation de mon serveur dedie]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Array|here]]. 


{{#seo:
|title=How to change the operating system of my dedicated server
|title_mode=append
|keywords=these,are,your,keywords
|description=How to change the operating system of my dedicated server
|image=Uploaded_file.png
|image_alt=Wiki Logo
}}

==Introduction== 
I want to change the OS of my dedicated server

==Course== 
To change the OS of your dedicated server you need to : 
- Connect to your customer area: https://commande.ikoula.com/clientarea 
- Go to the "Dedicated Servers" tab and choose the server on which you want to change the OS 
- In the Service Details, click on Update/Upgrade next to Operating System 

[[File:ChangeOS.PNG]] 
[[File:Capture2.PNG]] 

==Conclusion== 
The process will then start automatically. You can follow the progress of your reset from the Extranet: https://extranet.ikoula.com



 
Cet article vous a semblé utile ? <vote />




<comments />



[[Category:Dedicated server]]

Disable Ubuntu sleep mode

2021-07-30T09:45:14Z

Ikbot:

[[:nl:Ubuntu slaapstand uitschakelen]][[nl:Ubuntu slaapstand uitschakelen]]
[[:it:Disattivare la modalità sonno di Ubuntu]][[it:Disattivare la modalità sonno di Ubuntu]]
[[:pt:Desactivar o modo de sono Ubuntu]][[pt:Desactivar o modo de sono Ubuntu]]
[[:es:Desactivar el modo de suspensión de Ubuntu]][[es:Desactivar el modo de suspensión de Ubuntu]]
[[:fr:Désactiver la mise en veille Ubuntu]][[fr:Désactiver la mise en veille Ubuntu]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Désactiver la mise en veille Ubuntu|here]]. 
==How to disable Ubuntu sleep mode? ===

To disable standby on your Ubuntu server, you already need to see the status of the standby service.

<pre>systemctl status sleep.target</pre>

[[File:Sleep.PNG]]

Once you have checked this, you should also check the status of other monitoring services.

<pre>systemctl status suspend.target</pre>

<pre>systemctl status hibernate.target</pre>

<pre>systemctl status hybrid-sleep.target</pre>

[[File:Sleep2.PNG]]

To suspend the standby service, you can perform the following command:

<pre>systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target</pre>

[[File:Sleep3.PNG]]

Then the service will appear as "masked" which will prevent your server from going to sleep.

<pre>systemctl status sleep.target</pre>

[[File:Sleep4.PNG]]

[[Category:Linux]] [[Category:VPS server]] [[Category:Dedicated server]]

Disable Ubuntu sleep mode

2021-07-30T09:44:28Z

Ikbot:

[[:it:Disattivare la modalità sonno di Ubuntu]][[it:Disattivare la modalità sonno di Ubuntu]]
[[:pt:Desactivar o modo de sono Ubuntu]][[pt:Desactivar o modo de sono Ubuntu]]
[[:es:Desactivar el modo de suspensión de Ubuntu]][[es:Desactivar el modo de suspensión de Ubuntu]]
[[:fr:Désactiver la mise en veille Ubuntu]][[fr:Désactiver la mise en veille Ubuntu]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Désactiver la mise en veille Ubuntu|here]]. 
==How to disable Ubuntu sleep mode? ===

To disable standby on your Ubuntu server, you already need to see the status of the standby service.

<pre>systemctl status sleep.target</pre>

[[File:Sleep.PNG]]

Once you have checked this, you should also check the status of other monitoring services.

<pre>systemctl status suspend.target</pre>

<pre>systemctl status hibernate.target</pre>

<pre>systemctl status hybrid-sleep.target</pre>

[[File:Sleep2.PNG]]

To suspend the standby service, you can perform the following command:

<pre>systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target</pre>

[[File:Sleep3.PNG]]

Then the service will appear as "masked" which will prevent your server from going to sleep.

<pre>systemctl status sleep.target</pre>

[[File:Sleep4.PNG]]

[[Category:Linux]] [[Category:VPS server]] [[Category:Dedicated server]]

Disable Ubuntu sleep mode

2021-07-30T09:43:48Z

Ikbot:

[[:pt:Desactivar o modo de sono Ubuntu]][[pt:Desactivar o modo de sono Ubuntu]]
[[:es:Desactivar el modo de suspensión de Ubuntu]][[es:Desactivar el modo de suspensión de Ubuntu]]
[[:fr:Désactiver la mise en veille Ubuntu]][[fr:Désactiver la mise en veille Ubuntu]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Désactiver la mise en veille Ubuntu|here]]. 
==How to disable Ubuntu sleep mode? ===

To disable standby on your Ubuntu server, you already need to see the status of the standby service.

<pre>systemctl status sleep.target</pre>

[[File:Sleep.PNG]]

Once you have checked this, you should also check the status of other monitoring services.

<pre>systemctl status suspend.target</pre>

<pre>systemctl status hibernate.target</pre>

<pre>systemctl status hybrid-sleep.target</pre>

[[File:Sleep2.PNG]]

To suspend the standby service, you can perform the following command:

<pre>systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target</pre>

[[File:Sleep3.PNG]]

Then the service will appear as "masked" which will prevent your server from going to sleep.

<pre>systemctl status sleep.target</pre>

[[File:Sleep4.PNG]]

[[Category:Linux]] [[Category:VPS server]] [[Category:Dedicated server]]

Disable Ubuntu sleep mode

2021-07-30T09:43:17Z

Ikbot:

[[:es:Desactivar el modo de suspensión de Ubuntu]][[es:Desactivar el modo de suspensión de Ubuntu]]
[[:fr:Désactiver la mise en veille Ubuntu]][[fr:Désactiver la mise en veille Ubuntu]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Désactiver la mise en veille Ubuntu|here]]. 
==How to disable Ubuntu sleep mode? ===

To disable standby on your Ubuntu server, you already need to see the status of the standby service.

<pre>systemctl status sleep.target</pre>

[[File:Sleep.PNG]]

Once you have checked this, you should also check the status of other monitoring services.

<pre>systemctl status suspend.target</pre>

<pre>systemctl status hibernate.target</pre>

<pre>systemctl status hybrid-sleep.target</pre>

[[File:Sleep2.PNG]]

To suspend the standby service, you can perform the following command:

<pre>systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target</pre>

[[File:Sleep3.PNG]]

Then the service will appear as "masked" which will prevent your server from going to sleep.

<pre>systemctl status sleep.target</pre>

[[File:Sleep4.PNG]]

[[Category:Linux]] [[Category:VPS server]] [[Category:Dedicated server]]

Disable Ubuntu sleep mode

2021-07-30T09:42:48Z

Ikbot: Created page with ":fr:Désactiver la mise e..."

[[:fr:Désactiver la mise en veille Ubuntu]][[fr:Désactiver la mise en veille Ubuntu]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Désactiver la mise en veille Ubuntu|here]]. 
==How to disable Ubuntu sleep mode? ===

To disable standby on your Ubuntu server, you already need to see the status of the standby service.

<pre>systemctl status sleep.target</pre>

[[File:Sleep.PNG]]

Once you have checked this, you should also check the status of other monitoring services.

<pre>systemctl status suspend.target</pre>

<pre>systemctl status hibernate.target</pre>

<pre>systemctl status hybrid-sleep.target</pre>

[[File:Sleep2.PNG]]

To suspend the standby service, you can perform the following command:

<pre>systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target</pre>

[[File:Sleep3.PNG]]

Then the service will appear as "masked" which will prevent your server from going to sleep.

<pre>systemctl status sleep.target</pre>

[[File:Sleep4.PNG]]

[[Category:Linux]] [[Category:VPS server]] [[Category:Dedicated server]]

Deploy a Gitea stack

2021-07-30T09:40:03Z

Ikbot:

[[:de:Einsatz eines Gitea-Stacks]][[de:Einsatz eines Gitea-Stacks]]
[[:nl:Een Gitea-stack implementeren]][[nl:Een Gitea-stack implementeren]]
[[:it:Distribuire uno stack Gitea]][[it:Distribuire uno stack Gitea]]
[[:pt:Implantação de uma pilha de Gitea]][[pt:Implantação de uma pilha de Gitea]]
[[:es:Despliegue de una pila Gitea]][[es:Despliegue de una pila Gitea]]
[[:en:Deploy a Gitea stack]][[en:Deploy a Gitea stack]]
[[:fr:Déployer une stack Gitea]][[fr:Déployer une stack Gitea]]

{{#seo:
|title=Deploy a Gitea stac
|titlemode=replace
|keywords=Gitea
|description=In order to deploy a Gitea stack you can follow the official documentation of the project
|og:type=article
|og:image=https://en-wiki.ikoula.com/resources/assets/logo_ikwiki.png

}}

== Prerequisites ==

In order to be able to deploy a "stack Gitea" you can follow the official documentation of the project :

[https://docs.gitea.io/en-us/install-with-docker/ Documentation Gitea]

To do this you must have :

* a functional GNU / Linux system to which you will have access in SSH
* a docker and docker facility
 
 
You can perform this installation from a Physical Machine, a Virtual Machine or a Cloud Ikoula One Instance.

== Deployment of Gitea ==

Deploying your "Stack" '''Gitea'''will be made using a file that you will have beforehand create or deposit in a folder to which the user will have access.

In our example we will deploy with the support of Postgres as SGBD (you can replace by the couple of login passwords of your choice):

<syntaxhighlight lang=bash>
version: "2"

networks:
gitea:
external: false

services:
server:
image: gitea/gitea:latest
environment:
- USER_UID=1000
- USER_GID=1000
restart: always
networks:
- gitea
volumes:
- /var/lib/persistent/gitea:/data
ports:
- "80:3000"
- "222:22"
depends_on:
- db

db:
image: postgres:9.6
restart: always
environment:
- POSTGRES_USER=gitea
- POSTGRES_PASSWORD=gitea
- POSTGRES_DB=gitea
networks:
- gitea
volumes:
- /var/lib/persistent/postgres:/var/lib/postgresql/data
</syntaxhighlight>

Be sure to open TCP ports 3000 and 222 on the host.

To run your composer.yml file in the background from the folder where the file is stored :

<syntaxhighlight lang=bash># docker-compose up -d</syntaxhighlight>

All you need to do is complete the form to finalize the installation and access your Gitea stack.

<syntaxhighlight lang=bash>http://VOTRE_IP</syntaxhighlight>

You should now be able to connect to your Stack Gitea on the Web and SSH from the authorized IPs on your firewall.
It is quite possible to make your ''Gitea'' stack coexist with other services behind a reverse Proxy in such a case free to you to modify at your convenience the listening port of the WEB service.

[[File:Gitea-deploy3.png|center|Gitea]]

[[Category:docker]]
[[Catégorie :Cloudstack]]
[[Catégorie :Cloud public]]
[[Catégorie:Serveur dédié]]
[[Catégorie:Linux]]
[[Catégorie:FLEX]]

Deploy a Gitea stack

2021-07-30T09:38:34Z

Ikbot:

[[:nl:Een Gitea-stack implementeren]][[nl:Een Gitea-stack implementeren]]
[[:it:Distribuire uno stack Gitea]][[it:Distribuire uno stack Gitea]]
[[:pt:Implantação de uma pilha de Gitea]][[pt:Implantação de uma pilha de Gitea]]
[[:es:Despliegue de una pila Gitea]][[es:Despliegue de una pila Gitea]]
[[:en:Deploy a Gitea stack]][[en:Deploy a Gitea stack]]
[[:fr:Déployer une stack Gitea]][[fr:Déployer une stack Gitea]]

{{#seo:
|title=Deploy a Gitea stac
|titlemode=replace
|keywords=Gitea
|description=In order to deploy a Gitea stack you can follow the official documentation of the project
|og:type=article
|og:image=https://en-wiki.ikoula.com/resources/assets/logo_ikwiki.png

}}

== Prerequisites ==

In order to be able to deploy a "stack Gitea" you can follow the official documentation of the project :

[https://docs.gitea.io/en-us/install-with-docker/ Documentation Gitea]

To do this you must have :

* a functional GNU / Linux system to which you will have access in SSH
* a docker and docker facility
 
 
You can perform this installation from a Physical Machine, a Virtual Machine or a Cloud Ikoula One Instance.

== Deployment of Gitea ==

Deploying your "Stack" '''Gitea'''will be made using a file that you will have beforehand create or deposit in a folder to which the user will have access.

In our example we will deploy with the support of Postgres as SGBD (you can replace by the couple of login passwords of your choice):

<syntaxhighlight lang=bash>
version: "2"

networks:
gitea:
external: false

services:
server:
image: gitea/gitea:latest
environment:
- USER_UID=1000
- USER_GID=1000
restart: always
networks:
- gitea
volumes:
- /var/lib/persistent/gitea:/data
ports:
- "80:3000"
- "222:22"
depends_on:
- db

db:
image: postgres:9.6
restart: always
environment:
- POSTGRES_USER=gitea
- POSTGRES_PASSWORD=gitea
- POSTGRES_DB=gitea
networks:
- gitea
volumes:
- /var/lib/persistent/postgres:/var/lib/postgresql/data
</syntaxhighlight>

Be sure to open TCP ports 3000 and 222 on the host.

To run your composer.yml file in the background from the folder where the file is stored :

<syntaxhighlight lang=bash># docker-compose up -d</syntaxhighlight>

All you need to do is complete the form to finalize the installation and access your Gitea stack.

<syntaxhighlight lang=bash>http://VOTRE_IP</syntaxhighlight>

You should now be able to connect to your Stack Gitea on the Web and SSH from the authorized IPs on your firewall.
It is quite possible to make your ''Gitea'' stack coexist with other services behind a reverse Proxy in such a case free to you to modify at your convenience the listening port of the WEB service.

[[File:Gitea-deploy3.png|center|Gitea]]

[[Category:docker]]
[[Catégorie :Cloudstack]]
[[Catégorie :Cloud public]]
[[Catégorie:Serveur dédié]]
[[Catégorie:Linux]]
[[Catégorie:FLEX]]

Deploy a Gitea stack

2021-07-30T09:37:34Z

Ikbot:

[[:it:Distribuire uno stack Gitea]][[it:Distribuire uno stack Gitea]]
[[:pt:Implantação de uma pilha de Gitea]][[pt:Implantação de uma pilha de Gitea]]
[[:es:Despliegue de una pila Gitea]][[es:Despliegue de una pila Gitea]]
[[:en:Deploy a Gitea stack]][[en:Deploy a Gitea stack]]
[[:fr:Déployer une stack Gitea]][[fr:Déployer une stack Gitea]]

{{#seo:
|title=Deploy a Gitea stac
|titlemode=replace
|keywords=Gitea
|description=In order to deploy a Gitea stack you can follow the official documentation of the project
|og:type=article
|og:image=https://en-wiki.ikoula.com/resources/assets/logo_ikwiki.png

}}

== Prerequisites ==

In order to be able to deploy a "stack Gitea" you can follow the official documentation of the project :

[https://docs.gitea.io/en-us/install-with-docker/ Documentation Gitea]

To do this you must have :

* a functional GNU / Linux system to which you will have access in SSH
* a docker and docker facility
 
 
You can perform this installation from a Physical Machine, a Virtual Machine or a Cloud Ikoula One Instance.

== Deployment of Gitea ==

Deploying your "Stack" '''Gitea'''will be made using a file that you will have beforehand create or deposit in a folder to which the user will have access.

In our example we will deploy with the support of Postgres as SGBD (you can replace by the couple of login passwords of your choice):

<syntaxhighlight lang=bash>
version: "2"

networks:
gitea:
external: false

services:
server:
image: gitea/gitea:latest
environment:
- USER_UID=1000
- USER_GID=1000
restart: always
networks:
- gitea
volumes:
- /var/lib/persistent/gitea:/data
ports:
- "80:3000"
- "222:22"
depends_on:
- db

db:
image: postgres:9.6
restart: always
environment:
- POSTGRES_USER=gitea
- POSTGRES_PASSWORD=gitea
- POSTGRES_DB=gitea
networks:
- gitea
volumes:
- /var/lib/persistent/postgres:/var/lib/postgresql/data
</syntaxhighlight>

Be sure to open TCP ports 3000 and 222 on the host.

To run your composer.yml file in the background from the folder where the file is stored :

<syntaxhighlight lang=bash># docker-compose up -d</syntaxhighlight>

All you need to do is complete the form to finalize the installation and access your Gitea stack.

<syntaxhighlight lang=bash>http://VOTRE_IP</syntaxhighlight>

You should now be able to connect to your Stack Gitea on the Web and SSH from the authorized IPs on your firewall.
It is quite possible to make your ''Gitea'' stack coexist with other services behind a reverse Proxy in such a case free to you to modify at your convenience the listening port of the WEB service.

[[File:Gitea-deploy3.png|center|Gitea]]

[[Category:docker]]
[[Catégorie :Cloudstack]]
[[Catégorie :Cloud public]]
[[Catégorie:Serveur dédié]]
[[Catégorie:Linux]]
[[Catégorie:FLEX]]

Deploy a Gitea stack

2021-07-30T09:35:53Z

Ikbot:

[[:pt:Implantação de uma pilha de Gitea]][[pt:Implantação de uma pilha de Gitea]]
[[:es:Despliegue de una pila Gitea]][[es:Despliegue de una pila Gitea]]
[[:en:Deploy a Gitea stack]][[en:Deploy a Gitea stack]]
[[:fr:Déployer une stack Gitea]][[fr:Déployer une stack Gitea]]

{{#seo:
|title=Deploy a Gitea stac
|titlemode=replace
|keywords=Gitea
|description=In order to deploy a Gitea stack you can follow the official documentation of the project
|og:type=article
|og:image=https://en-wiki.ikoula.com/resources/assets/logo_ikwiki.png

}}

== Prerequisites ==

In order to be able to deploy a "stack Gitea" you can follow the official documentation of the project :

[https://docs.gitea.io/en-us/install-with-docker/ Documentation Gitea]

To do this you must have :

* a functional GNU / Linux system to which you will have access in SSH
* a docker and docker facility
 
 
You can perform this installation from a Physical Machine, a Virtual Machine or a Cloud Ikoula One Instance.

== Deployment of Gitea ==

Deploying your "Stack" '''Gitea'''will be made using a file that you will have beforehand create or deposit in a folder to which the user will have access.

In our example we will deploy with the support of Postgres as SGBD (you can replace by the couple of login passwords of your choice):

<syntaxhighlight lang=bash>
version: "2"

networks:
gitea:
external: false

services:
server:
image: gitea/gitea:latest
environment:
- USER_UID=1000
- USER_GID=1000
restart: always
networks:
- gitea
volumes:
- /var/lib/persistent/gitea:/data
ports:
- "80:3000"
- "222:22"
depends_on:
- db

db:
image: postgres:9.6
restart: always
environment:
- POSTGRES_USER=gitea
- POSTGRES_PASSWORD=gitea
- POSTGRES_DB=gitea
networks:
- gitea
volumes:
- /var/lib/persistent/postgres:/var/lib/postgresql/data
</syntaxhighlight>

Be sure to open TCP ports 3000 and 222 on the host.

To run your composer.yml file in the background from the folder where the file is stored :

<syntaxhighlight lang=bash># docker-compose up -d</syntaxhighlight>

All you need to do is complete the form to finalize the installation and access your Gitea stack.

<syntaxhighlight lang=bash>http://VOTRE_IP</syntaxhighlight>

You should now be able to connect to your Stack Gitea on the Web and SSH from the authorized IPs on your firewall.
It is quite possible to make your ''Gitea'' stack coexist with other services behind a reverse Proxy in such a case free to you to modify at your convenience the listening port of the WEB service.

[[File:Gitea-deploy3.png|center|Gitea]]

[[Category:docker]]
[[Catégorie :Cloudstack]]
[[Catégorie :Cloud public]]
[[Catégorie:Serveur dédié]]
[[Catégorie:Linux]]
[[Catégorie:FLEX]]

Deploy a Gitea stack

2021-07-30T09:34:43Z

Ikbot:

[[:es:Despliegue de una pila Gitea]][[es:Despliegue de una pila Gitea]]
[[:en:Deploy a Gitea stack]][[en:Deploy a Gitea stack]]
[[:fr:Déployer une stack Gitea]][[fr:Déployer une stack Gitea]]

{{#seo:
|title=Deploy a Gitea stac
|titlemode=replace
|keywords=Gitea
|description=In order to deploy a Gitea stack you can follow the official documentation of the project
|og:type=article
|og:image=https://en-wiki.ikoula.com/resources/assets/logo_ikwiki.png

}}

== Prerequisites ==

In order to be able to deploy a "stack Gitea" you can follow the official documentation of the project :

[https://docs.gitea.io/en-us/install-with-docker/ Documentation Gitea]

To do this you must have :

* a functional GNU / Linux system to which you will have access in SSH
* a docker and docker facility
 
 
You can perform this installation from a Physical Machine, a Virtual Machine or a Cloud Ikoula One Instance.

== Deployment of Gitea ==

Deploying your "Stack" '''Gitea'''will be made using a file that you will have beforehand create or deposit in a folder to which the user will have access.

In our example we will deploy with the support of Postgres as SGBD (you can replace by the couple of login passwords of your choice):

<syntaxhighlight lang=bash>
version: "2"

networks:
gitea:
external: false

services:
server:
image: gitea/gitea:latest
environment:
- USER_UID=1000
- USER_GID=1000
restart: always
networks:
- gitea
volumes:
- /var/lib/persistent/gitea:/data
ports:
- "80:3000"
- "222:22"
depends_on:
- db

db:
image: postgres:9.6
restart: always
environment:
- POSTGRES_USER=gitea
- POSTGRES_PASSWORD=gitea
- POSTGRES_DB=gitea
networks:
- gitea
volumes:
- /var/lib/persistent/postgres:/var/lib/postgresql/data
</syntaxhighlight>

Be sure to open TCP ports 3000 and 222 on the host.

To run your composer.yml file in the background from the folder where the file is stored :

<syntaxhighlight lang=bash># docker-compose up -d</syntaxhighlight>

All you need to do is complete the form to finalize the installation and access your Gitea stack.

<syntaxhighlight lang=bash>http://VOTRE_IP</syntaxhighlight>

You should now be able to connect to your Stack Gitea on the Web and SSH from the authorized IPs on your firewall.
It is quite possible to make your ''Gitea'' stack coexist with other services behind a reverse Proxy in such a case free to you to modify at your convenience the listening port of the WEB service.

[[File:Gitea-deploy3.png|center|Gitea]]

[[Category:docker]]
[[Catégorie :Cloudstack]]
[[Catégorie :Cloud public]]
[[Catégorie:Serveur dédié]]
[[Catégorie:Linux]]
[[Catégorie:FLEX]]

Discover the WebUI Cockpit project

2021-07-30T08:07:58Z

Ikbot:

[[:nl:Ontdek het WebUI Cockpit project]][[nl:Ontdek het WebUI Cockpit project]]
[[:it:Scoprire il progetto WebUI Cockpit]][[it:Scoprire il progetto WebUI Cockpit]]
[[:pt:Descubra o projecto WebUI Cockpit]][[pt:Descubra o projecto WebUI Cockpit]]
[[:es:Descubre el proyecto WebUI Cockpit]][[es:Descubre el proyecto WebUI Cockpit]]
[[:fr:Découvrir la WebUI Cockpit project]][[fr:Découvrir la WebUI Cockpit project]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Array|here]]. 


{{#seo:
|title=Cockpit project
|titlemode=replace
|keywords=Cockpit project
|description= Administration and monitoring interface for Linux servers
|og:type=article
|og:image=https://it-wiki.ikoula.com/resources/assets/logo_ikwiki.png
}}

== Presentation ==
[[File:Cockpit-logo.png|right|225px|Cockpit logo]]
''' Cockpit project''' is an administration interface for operating systems based on the Linux kernel.

The list of supported systems is available at [https://cockpit-project.org/running.html the official website of the project].

This tool allows you to fully administer your server via a web interface.

Quote from the Cockpit documentation :
<blockquote>
Cockpit is a server manager that makes it easy to administer your Linux servers via a web browser. Jumping between the terminal and the web tool is not a problem. A service started via Cockpit can be stopped via the terminal. Also, if an error occurs in the terminal, it is displayed in the Cockpit log interface.

Cockpit is perfect for new system administrators, allowing them to easily perform simple tasks such as storage administration, log inspection, and starting and stopping services. You can monitor and administer multiple servers at the same time. Just add them with one click and your machines will take care of their peers.
</blockquote>

== Features ==
The following features are available in Cockpit, even with a minimal installation:

Overview
Overview: Global view of operating system and hardware information.
Overview: Usage graphs (CPU, Network, RAM and disk usage), hardware details and configurations are available.

Logs
Logs : Display of system logs.
Logs: It is possible to filter logs by date, severity and services.

Network
Network: Display network information (Send/Receive, zones and firewall rules, interfaces, network logs).
Network: Allows you to manage network interfaces and the firewall.

Accounts
User accounts : User account creation
To strengthen the security of the server, it is recommended to create a user account with the rights to log in to this user via the server. <code>sudo</code>The user can log in to this user via cockpit and lock the account. <code>root</code>.

Service Provisions
Lists the services installed on the system and their status (active/inactive).

Applications
Adds extensions to the cockpit.

Diagnostic Reports
Collection of system configuration and diagnostic information.

Kernel Dump
A memory dump mechanism that allows system memory to be saved after a kernel incident for later analysis.

Software Updates
Software Updates: Checks for and displays available updates.
Software Updates: Allows the installation of updates but also to schedule automatic updates.

SELinux
SELinux error logs : Management and detail of SELinux error logs.
SELinux : Propose solutions for each error detected by the SELinux service installed on the server.

Terminal
Access to the terminal from the web browser.

<gallery heights="200px" widths="200px" mode="packed-overlay" caption="Vue d'ensemble des fonctionnalités principales de Cockpit">
File:Cockpit Overview.png|Overview
File:Cockpit Logs.png|Logs
File:Cockpit Network.png|Network
File:Cockpit Accounts.png|Accounts
File:Cockpit Services.png|Service provision
</gallery>


== Cockpit installation ==
En fonction de l'installation du serveur, Cockpit peut ne pas être installé et/ou activé par défaut.

=== Installation ===
Ci-dessous, on va procéder à une installation minimale de Cockpit sans les applications associées.

Il est décessaire d'être connecté en ssh à un utilisateur ayant les droits d'administration ou des droits sudo.

;Fedora / Red Hat / CentOS
<pre>
# dnf check-update
# dnf install cockpit-ws
</pre>

;Debian / Ubuntu
<pre>
# apt update
# apt install cockpit
</pre>

=== Activation ===
Pour activer Cockpit sur votre serveur, nous allons utiliser les commandes fournies par systemd, le gestionnaire de démarrage de la plupart des distributions Linux.
<pre># systemctl enable --now cockpit</pre>

Une fois activé, nous pouvons vérifier le bon fonctionnement du service :

<pre>
# systemctl status cockpit
</pre>

== Use ==
Pour utiliser Cockpit, accédez avec votre navigateur internet à <code>https://[IP_du_serveur]:9090</code>.

Les identifiants et mots de passe correspondent aux utilisateurs du système d'exploitation.

 
Cet article vous a été utile ?
 
<vote />


<comments />

[[Category:Dedicated server]]
[[Category:Linux]]
[[Category:VPS server]]

Discover the WebUI Cockpit project

2021-07-30T08:06:48Z

Ikbot:

[[:it:Scoprire il progetto WebUI Cockpit]][[it:Scoprire il progetto WebUI Cockpit]]
[[:pt:Descubra o projecto WebUI Cockpit]][[pt:Descubra o projecto WebUI Cockpit]]
[[:es:Descubre el proyecto WebUI Cockpit]][[es:Descubre el proyecto WebUI Cockpit]]
[[:fr:Découvrir la WebUI Cockpit project]][[fr:Découvrir la WebUI Cockpit project]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Array|here]]. 


{{#seo:
|title=Cockpit project
|titlemode=replace
|keywords=Cockpit project
|description= Administration and monitoring interface for Linux servers
|og:type=article
|og:image=https://it-wiki.ikoula.com/resources/assets/logo_ikwiki.png
}}

== Presentation ==
[[File:Cockpit-logo.png|right|225px|Cockpit logo]]
''' Cockpit project''' is an administration interface for operating systems based on the Linux kernel.

The list of supported systems is available at [https://cockpit-project.org/running.html the official website of the project].

This tool allows you to fully administer your server via a web interface.

Quote from the Cockpit documentation :
<blockquote>
Cockpit is a server manager that makes it easy to administer your Linux servers via a web browser. Jumping between the terminal and the web tool is not a problem. A service started via Cockpit can be stopped via the terminal. Also, if an error occurs in the terminal, it is displayed in the Cockpit log interface.

Cockpit is perfect for new system administrators, allowing them to easily perform simple tasks such as storage administration, log inspection, and starting and stopping services. You can monitor and administer multiple servers at the same time. Just add them with one click and your machines will take care of their peers.
</blockquote>

== Features ==
The following features are available in Cockpit, even with a minimal installation:

Overview
Overview: Global view of operating system and hardware information.
Overview: Usage graphs (CPU, Network, RAM and disk usage), hardware details and configurations are available.

Logs
Logs : Display of system logs.
Logs: It is possible to filter logs by date, severity and services.

Network
Network: Display network information (Send/Receive, zones and firewall rules, interfaces, network logs).
Network: Allows you to manage network interfaces and the firewall.

Accounts
User accounts : User account creation
To strengthen the security of the server, it is recommended to create a user account with the rights to log in to this user via the server. <code>sudo</code>The user can log in to this user via cockpit and lock the account. <code>root</code>.

Service Provisions
Lists the services installed on the system and their status (active/inactive).

Applications
Adds extensions to the cockpit.

Diagnostic Reports
Collection of system configuration and diagnostic information.

Kernel Dump
A memory dump mechanism that allows system memory to be saved after a kernel incident for later analysis.

Software Updates
Software Updates: Checks for and displays available updates.
Software Updates: Allows the installation of updates but also to schedule automatic updates.

SELinux
SELinux error logs : Management and detail of SELinux error logs.
SELinux : Propose solutions for each error detected by the SELinux service installed on the server.

Terminal
Access to the terminal from the web browser.

<gallery heights="200px" widths="200px" mode="packed-overlay" caption="Vue d'ensemble des fonctionnalités principales de Cockpit">
File:Cockpit Overview.png|Overview
File:Cockpit Logs.png|Logs
File:Cockpit Network.png|Network
File:Cockpit Accounts.png|Accounts
File:Cockpit Services.png|Service provision
</gallery>


== Cockpit installation ==
En fonction de l'installation du serveur, Cockpit peut ne pas être installé et/ou activé par défaut.

=== Installation ===
Ci-dessous, on va procéder à une installation minimale de Cockpit sans les applications associées.

Il est décessaire d'être connecté en ssh à un utilisateur ayant les droits d'administration ou des droits sudo.

;Fedora / Red Hat / CentOS
<pre>
# dnf check-update
# dnf install cockpit-ws
</pre>

;Debian / Ubuntu
<pre>
# apt update
# apt install cockpit
</pre>

=== Activation ===
Pour activer Cockpit sur votre serveur, nous allons utiliser les commandes fournies par systemd, le gestionnaire de démarrage de la plupart des distributions Linux.
<pre># systemctl enable --now cockpit</pre>

Une fois activé, nous pouvons vérifier le bon fonctionnement du service :

<pre>
# systemctl status cockpit
</pre>

== Use ==
Pour utiliser Cockpit, accédez avec votre navigateur internet à <code>https://[IP_du_serveur]:9090</code>.

Les identifiants et mots de passe correspondent aux utilisateurs du système d'exploitation.

 
Cet article vous a été utile ?
 
<vote />


<comments />

[[Category:Dedicated server]]
[[Category:Linux]]
[[Category:VPS server]]

Discover the WebUI Cockpit project

2021-07-30T08:05:48Z

Ikbot:

[[:pt:Descubra o projecto WebUI Cockpit]][[pt:Descubra o projecto WebUI Cockpit]]
[[:es:Descubre el proyecto WebUI Cockpit]][[es:Descubre el proyecto WebUI Cockpit]]
[[:fr:Découvrir la WebUI Cockpit project]][[fr:Découvrir la WebUI Cockpit project]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Array|here]]. 


{{#seo:
|title=Cockpit project
|titlemode=replace
|keywords=Cockpit project
|description= Administration and monitoring interface for Linux servers
|og:type=article
|og:image=https://it-wiki.ikoula.com/resources/assets/logo_ikwiki.png
}}

== Presentation ==
[[File:Cockpit-logo.png|right|225px|Cockpit logo]]
''' Cockpit project''' is an administration interface for operating systems based on the Linux kernel.

The list of supported systems is available at [https://cockpit-project.org/running.html the official website of the project].

This tool allows you to fully administer your server via a web interface.

Quote from the Cockpit documentation :
<blockquote>
Cockpit is a server manager that makes it easy to administer your Linux servers via a web browser. Jumping between the terminal and the web tool is not a problem. A service started via Cockpit can be stopped via the terminal. Also, if an error occurs in the terminal, it is displayed in the Cockpit log interface.

Cockpit is perfect for new system administrators, allowing them to easily perform simple tasks such as storage administration, log inspection, and starting and stopping services. You can monitor and administer multiple servers at the same time. Just add them with one click and your machines will take care of their peers.
</blockquote>

== Features ==
The following features are available in Cockpit, even with a minimal installation:

Overview
Overview: Global view of operating system and hardware information.
Overview: Usage graphs (CPU, Network, RAM and disk usage), hardware details and configurations are available.

Logs
Logs : Display of system logs.
Logs: It is possible to filter logs by date, severity and services.

Network
Network: Display network information (Send/Receive, zones and firewall rules, interfaces, network logs).
Network: Allows you to manage network interfaces and the firewall.

Accounts
User accounts : User account creation
To strengthen the security of the server, it is recommended to create a user account with the rights to log in to this user via the server. <code>sudo</code>The user can log in to this user via cockpit and lock the account. <code>root</code>.

Service Provisions
Lists the services installed on the system and their status (active/inactive).

Applications
Adds extensions to the cockpit.

Diagnostic Reports
Collection of system configuration and diagnostic information.

Kernel Dump
A memory dump mechanism that allows system memory to be saved after a kernel incident for later analysis.

Software Updates
Software Updates: Checks for and displays available updates.
Software Updates: Allows the installation of updates but also to schedule automatic updates.

SELinux
SELinux error logs : Management and detail of SELinux error logs.
SELinux : Propose solutions for each error detected by the SELinux service installed on the server.

Terminal
Access to the terminal from the web browser.

<gallery heights="200px" widths="200px" mode="packed-overlay" caption="Vue d'ensemble des fonctionnalités principales de Cockpit">
File:Cockpit Overview.png|Overview
File:Cockpit Logs.png|Logs
File:Cockpit Network.png|Network
File:Cockpit Accounts.png|Accounts
File:Cockpit Services.png|Service provision
</gallery>


== Cockpit installation ==
En fonction de l'installation du serveur, Cockpit peut ne pas être installé et/ou activé par défaut.

=== Installation ===
Ci-dessous, on va procéder à une installation minimale de Cockpit sans les applications associées.

Il est décessaire d'être connecté en ssh à un utilisateur ayant les droits d'administration ou des droits sudo.

;Fedora / Red Hat / CentOS
<pre>
# dnf check-update
# dnf install cockpit-ws
</pre>

;Debian / Ubuntu
<pre>
# apt update
# apt install cockpit
</pre>

=== Activation ===
Pour activer Cockpit sur votre serveur, nous allons utiliser les commandes fournies par systemd, le gestionnaire de démarrage de la plupart des distributions Linux.
<pre># systemctl enable --now cockpit</pre>

Une fois activé, nous pouvons vérifier le bon fonctionnement du service :

<pre>
# systemctl status cockpit
</pre>

== Use ==
Pour utiliser Cockpit, accédez avec votre navigateur internet à <code>https://[IP_du_serveur]:9090</code>.

Les identifiants et mots de passe correspondent aux utilisateurs du système d'exploitation.

 
Cet article vous a été utile ?
 
<vote />


<comments />

[[Category:Dedicated server]]
[[Category:Linux]]
[[Category:VPS server]]

Discover the WebUI Cockpit project

2021-07-30T08:05:01Z

Ikbot:

[[:es:Descubre el proyecto WebUI Cockpit]][[es:Descubre el proyecto WebUI Cockpit]]
[[:fr:Découvrir la WebUI Cockpit project]][[fr:Découvrir la WebUI Cockpit project]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Array|here]]. 


{{#seo:
|title=Cockpit project
|titlemode=replace
|keywords=Cockpit project
|description= Administration and monitoring interface for Linux servers
|og:type=article
|og:image=https://it-wiki.ikoula.com/resources/assets/logo_ikwiki.png
}}

== Presentation ==
[[File:Cockpit-logo.png|right|225px|Cockpit logo]]
''' Cockpit project''' is an administration interface for operating systems based on the Linux kernel.

The list of supported systems is available at [https://cockpit-project.org/running.html the official website of the project].

This tool allows you to fully administer your server via a web interface.

Quote from the Cockpit documentation :
<blockquote>
Cockpit is a server manager that makes it easy to administer your Linux servers via a web browser. Jumping between the terminal and the web tool is not a problem. A service started via Cockpit can be stopped via the terminal. Also, if an error occurs in the terminal, it is displayed in the Cockpit log interface.

Cockpit is perfect for new system administrators, allowing them to easily perform simple tasks such as storage administration, log inspection, and starting and stopping services. You can monitor and administer multiple servers at the same time. Just add them with one click and your machines will take care of their peers.
</blockquote>

== Features ==
The following features are available in Cockpit, even with a minimal installation:

Overview
Overview: Global view of operating system and hardware information.
Overview: Usage graphs (CPU, Network, RAM and disk usage), hardware details and configurations are available.

Logs
Logs : Display of system logs.
Logs: It is possible to filter logs by date, severity and services.

Network
Network: Display network information (Send/Receive, zones and firewall rules, interfaces, network logs).
Network: Allows you to manage network interfaces and the firewall.

Accounts
User accounts : User account creation
To strengthen the security of the server, it is recommended to create a user account with the rights to log in to this user via the server. <code>sudo</code>The user can log in to this user via cockpit and lock the account. <code>root</code>.

Service Provisions
Lists the services installed on the system and their status (active/inactive).

Applications
Adds extensions to the cockpit.

Diagnostic Reports
Collection of system configuration and diagnostic information.

Kernel Dump
A memory dump mechanism that allows system memory to be saved after a kernel incident for later analysis.

Software Updates
Software Updates: Checks for and displays available updates.
Software Updates: Allows the installation of updates but also to schedule automatic updates.

SELinux
SELinux error logs : Management and detail of SELinux error logs.
SELinux : Propose solutions for each error detected by the SELinux service installed on the server.

Terminal
Access to the terminal from the web browser.

<gallery heights="200px" widths="200px" mode="packed-overlay" caption="Vue d'ensemble des fonctionnalités principales de Cockpit">
File:Cockpit Overview.png|Overview
File:Cockpit Logs.png|Logs
File:Cockpit Network.png|Network
File:Cockpit Accounts.png|Accounts
File:Cockpit Services.png|Service provision
</gallery>


== Cockpit installation ==
En fonction de l'installation du serveur, Cockpit peut ne pas être installé et/ou activé par défaut.

=== Installation ===
Ci-dessous, on va procéder à une installation minimale de Cockpit sans les applications associées.

Il est décessaire d'être connecté en ssh à un utilisateur ayant les droits d'administration ou des droits sudo.

;Fedora / Red Hat / CentOS
<pre>
# dnf check-update
# dnf install cockpit-ws
</pre>

;Debian / Ubuntu
<pre>
# apt update
# apt install cockpit
</pre>

=== Activation ===
Pour activer Cockpit sur votre serveur, nous allons utiliser les commandes fournies par systemd, le gestionnaire de démarrage de la plupart des distributions Linux.
<pre># systemctl enable --now cockpit</pre>

Une fois activé, nous pouvons vérifier le bon fonctionnement du service :

<pre>
# systemctl status cockpit
</pre>

== Use ==
Pour utiliser Cockpit, accédez avec votre navigateur internet à <code>https://[IP_du_serveur]:9090</code>.

Les identifiants et mots de passe correspondent aux utilisateurs du système d'exploitation.

 
Cet article vous a été utile ?
 
<vote />


<comments />

[[Category:Dedicated server]]
[[Category:Linux]]
[[Category:VPS server]]

Discover the WebUI Cockpit project

2021-07-30T08:00:19Z

Ikbot: Created page with ":fr:Découvrir la WebUI Coc..."

[[:fr:Découvrir la WebUI Cockpit project]][[fr:Découvrir la WebUI Cockpit project]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Array|here]]. 


{{#seo:
|title=Cockpit project
|titlemode=replace
|keywords=Cockpit project
|description= Administration and monitoring interface for Linux servers
|og:type=article
|og:image=https://it-wiki.ikoula.com/resources/assets/logo_ikwiki.png
}}

== Presentation ==
[[File:Cockpit-logo.png|right|225px|Cockpit logo]]
''' Cockpit project''' is an administration interface for operating systems based on the Linux kernel.

The list of supported systems is available at [https://cockpit-project.org/running.html the official website of the project].

This tool allows you to fully administer your server via a web interface.

Quote from the Cockpit documentation :
<blockquote>
Cockpit is a server manager that makes it easy to administer your Linux servers via a web browser. Jumping between the terminal and the web tool is not a problem. A service started via Cockpit can be stopped via the terminal. Also, if an error occurs in the terminal, it is displayed in the Cockpit log interface.

Cockpit is perfect for new system administrators, allowing them to easily perform simple tasks such as storage administration, log inspection, and starting and stopping services. You can monitor and administer multiple servers at the same time. Just add them with one click and your machines will take care of their peers.
</blockquote>

== Features ==
The following features are available in Cockpit, even with a minimal installation:

Overview
Overview: Global view of operating system and hardware information.
Overview: Usage graphs (CPU, Network, RAM and disk usage), hardware details and configurations are available.

Logs
Logs : Display of system logs.
Logs: It is possible to filter logs by date, severity and services.

Network
Network: Display network information (Send/Receive, zones and firewall rules, interfaces, network logs).
Network: Allows you to manage network interfaces and the firewall.

Accounts
User accounts : User account creation
To strengthen the security of the server, it is recommended to create a user account with the rights to log in to this user via the server. <code>sudo</code>The user can log in to this user via cockpit and lock the account. <code>root</code>.

Service Provisions
Lists the services installed on the system and their status (active/inactive).

Applications
Adds extensions to the cockpit.

Diagnostic Reports
Collection of system configuration and diagnostic information.

Kernel Dump
A memory dump mechanism that allows system memory to be saved after a kernel incident for later analysis.

Software Updates
Software Updates: Checks for and displays available updates.
Software Updates: Allows the installation of updates but also to schedule automatic updates.

SELinux
SELinux error logs : Management and detail of SELinux error logs.
SELinux : Propose solutions for each error detected by the SELinux service installed on the server.

Terminal
Access to the terminal from the web browser.

<gallery heights="200px" widths="200px" mode="packed-overlay" caption="Vue d'ensemble des fonctionnalités principales de Cockpit">
File:Cockpit Overview.png|Overview
File:Cockpit Logs.png|Logs
File:Cockpit Network.png|Network
File:Cockpit Accounts.png|Accounts
File:Cockpit Services.png|Service provision
</gallery>


== Cockpit installation ==
En fonction de l'installation du serveur, Cockpit peut ne pas être installé et/ou activé par défaut.

=== Installation ===
Ci-dessous, on va procéder à une installation minimale de Cockpit sans les applications associées.

Il est décessaire d'être connecté en ssh à un utilisateur ayant les droits d'administration ou des droits sudo.

;Fedora / Red Hat / CentOS
<pre>
# dnf check-update
# dnf install cockpit-ws
</pre>

;Debian / Ubuntu
<pre>
# apt update
# apt install cockpit
</pre>

=== Activation ===
Pour activer Cockpit sur votre serveur, nous allons utiliser les commandes fournies par systemd, le gestionnaire de démarrage de la plupart des distributions Linux.
<pre># systemctl enable --now cockpit</pre>

Une fois activé, nous pouvons vérifier le bon fonctionnement du service :

<pre>
# systemctl status cockpit
</pre>

== Use ==
Pour utiliser Cockpit, accédez avec votre navigateur internet à <code>https://[IP_du_serveur]:9090</code>.

Les identifiants et mots de passe correspondent aux utilisateurs du système d'exploitation.

 
Cet article vous a été utile ?
 
<vote />


<comments />

[[Category:Dedicated server]]
[[Category:Linux]]
[[Category:VPS server]]

Duplicate an instance in another zone

2021-07-29T15:36:33Z

Ikbot:

[[:ro:Duplicarea unei instanțe în altă zonă]][[ro:Duplicarea unei instanțe în altă zonă]]
[[:ru:Дублирование экземпляра в другой зоне]][[ru:Дублирование экземпляра в другой зоне]]
[[:pl:Duplikuj instancję w innej strefie]][[pl:Duplikuj instancję w innej strefie]]
[[:ja:インスタンスを別のゾーンに複製する]][[ja:インスタンスを別のゾーンに複製する]]
[[:zh:在另一区复制一个实例]][[zh:在另一区复制一个实例]]
[[:de:Duplizieren einer Instanz in einer anderen Zone]][[de:Duplizieren einer Instanz in einer anderen Zone]]
[[:nl:Een instantie in een andere zone dupliceren]][[nl:Een instantie in een andere zone dupliceren]]
[[:it:Duplicare un'istanza in un'altra zona]][[it:Duplicare un'istanza in un'altra zona]]
[[:pt:Duplicar uma instância noutra zona]][[pt:Duplicar uma instância noutra zona]]
[[:es:Duplicar una instancia en otra zona]][[es:Duplicar una instancia en otra zona]]
[[:fr:Dupliquer une instance dans une autre zone]][[fr:Dupliquer une instance dans une autre zone]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Dupliquer une instance dans une autre zone|here]]. 
==Use cases==
I have created an instance in a BASIC zone, I would like to move my instance to an ADVANCE zone to benefit from the features of this zone.
I would like to deploy my infrastructure identically in another zone to have a test infrastructure.

==Prerequisites==
I would like to deploy my infrastructure in another zone to have a test infrastructure.

==Unwinding==
Create a model of my cf instance: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]
# Copy my template to another zone cf: [[Copier_mon_modele_dans_une_autre_zone]]
# Deploy my template cf: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]

[[Category:Cloud_public]]
[[Catégorie :Cloud]]

Duplicate an instance in another zone

2021-07-29T15:35:37Z

Ikbot:

[[:ru:Дублирование экземпляра в другой зоне]][[ru:Дублирование экземпляра в другой зоне]]
[[:pl:Duplikuj instancję w innej strefie]][[pl:Duplikuj instancję w innej strefie]]
[[:ja:インスタンスを別のゾーンに複製する]][[ja:インスタンスを別のゾーンに複製する]]
[[:zh:在另一区复制一个实例]][[zh:在另一区复制一个实例]]
[[:de:Duplizieren einer Instanz in einer anderen Zone]][[de:Duplizieren einer Instanz in einer anderen Zone]]
[[:nl:Een instantie in een andere zone dupliceren]][[nl:Een instantie in een andere zone dupliceren]]
[[:it:Duplicare un'istanza in un'altra zona]][[it:Duplicare un'istanza in un'altra zona]]
[[:pt:Duplicar uma instância noutra zona]][[pt:Duplicar uma instância noutra zona]]
[[:es:Duplicar una instancia en otra zona]][[es:Duplicar una instancia en otra zona]]
[[:fr:Dupliquer une instance dans une autre zone]][[fr:Dupliquer une instance dans une autre zone]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Dupliquer une instance dans une autre zone|here]]. 
==Use cases==
I have created an instance in a BASIC zone, I would like to move my instance to an ADVANCE zone to benefit from the features of this zone.
I would like to deploy my infrastructure identically in another zone to have a test infrastructure.

==Prerequisites==
I would like to deploy my infrastructure in another zone to have a test infrastructure.

==Unwinding==
Create a model of my cf instance: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]
# Copy my template to another zone cf: [[Copier_mon_modele_dans_une_autre_zone]]
# Deploy my template cf: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]

[[Category:Cloud_public]]
[[Catégorie :Cloud]]

Duplicate an instance in another zone

2021-07-29T15:34:53Z

Ikbot:

[[:pl:Duplikuj instancję w innej strefie]][[pl:Duplikuj instancję w innej strefie]]
[[:ja:インスタンスを別のゾーンに複製する]][[ja:インスタンスを別のゾーンに複製する]]
[[:zh:在另一区复制一个实例]][[zh:在另一区复制一个实例]]
[[:de:Duplizieren einer Instanz in einer anderen Zone]][[de:Duplizieren einer Instanz in einer anderen Zone]]
[[:nl:Een instantie in een andere zone dupliceren]][[nl:Een instantie in een andere zone dupliceren]]
[[:it:Duplicare un'istanza in un'altra zona]][[it:Duplicare un'istanza in un'altra zona]]
[[:pt:Duplicar uma instância noutra zona]][[pt:Duplicar uma instância noutra zona]]
[[:es:Duplicar una instancia en otra zona]][[es:Duplicar una instancia en otra zona]]
[[:fr:Dupliquer une instance dans une autre zone]][[fr:Dupliquer une instance dans une autre zone]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Dupliquer une instance dans une autre zone|here]]. 
==Use cases==
I have created an instance in a BASIC zone, I would like to move my instance to an ADVANCE zone to benefit from the features of this zone.
I would like to deploy my infrastructure identically in another zone to have a test infrastructure.

==Prerequisites==
I would like to deploy my infrastructure in another zone to have a test infrastructure.

==Unwinding==
Create a model of my cf instance: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]
# Copy my template to another zone cf: [[Copier_mon_modele_dans_une_autre_zone]]
# Deploy my template cf: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]

[[Category:Cloud_public]]
[[Catégorie :Cloud]]

Duplicate an instance in another zone

2021-07-29T15:34:10Z

Ikbot:

[[:ja:インスタンスを別のゾーンに複製する]][[ja:インスタンスを別のゾーンに複製する]]
[[:zh:在另一区复制一个实例]][[zh:在另一区复制一个实例]]
[[:de:Duplizieren einer Instanz in einer anderen Zone]][[de:Duplizieren einer Instanz in einer anderen Zone]]
[[:nl:Een instantie in een andere zone dupliceren]][[nl:Een instantie in een andere zone dupliceren]]
[[:it:Duplicare un'istanza in un'altra zona]][[it:Duplicare un'istanza in un'altra zona]]
[[:pt:Duplicar uma instância noutra zona]][[pt:Duplicar uma instância noutra zona]]
[[:es:Duplicar una instancia en otra zona]][[es:Duplicar una instancia en otra zona]]
[[:fr:Dupliquer une instance dans une autre zone]][[fr:Dupliquer une instance dans une autre zone]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Dupliquer une instance dans une autre zone|here]]. 
==Use cases==
I have created an instance in a BASIC zone, I would like to move my instance to an ADVANCE zone to benefit from the features of this zone.
I would like to deploy my infrastructure identically in another zone to have a test infrastructure.

==Prerequisites==
I would like to deploy my infrastructure in another zone to have a test infrastructure.

==Unwinding==
Create a model of my cf instance: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]
# Copy my template to another zone cf: [[Copier_mon_modele_dans_une_autre_zone]]
# Deploy my template cf: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]

[[Category:Cloud_public]]
[[Catégorie :Cloud]]

Duplicate an instance in another zone

2021-07-29T15:33:26Z

Ikbot:

[[:zh:在另一区复制一个实例]][[zh:在另一区复制一个实例]]
[[:de:Duplizieren einer Instanz in einer anderen Zone]][[de:Duplizieren einer Instanz in einer anderen Zone]]
[[:nl:Een instantie in een andere zone dupliceren]][[nl:Een instantie in een andere zone dupliceren]]
[[:it:Duplicare un'istanza in un'altra zona]][[it:Duplicare un'istanza in un'altra zona]]
[[:pt:Duplicar uma instância noutra zona]][[pt:Duplicar uma instância noutra zona]]
[[:es:Duplicar una instancia en otra zona]][[es:Duplicar una instancia en otra zona]]
[[:fr:Dupliquer une instance dans une autre zone]][[fr:Dupliquer une instance dans une autre zone]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Dupliquer une instance dans une autre zone|here]]. 
==Use cases==
I have created an instance in a BASIC zone, I would like to move my instance to an ADVANCE zone to benefit from the features of this zone.
I would like to deploy my infrastructure identically in another zone to have a test infrastructure.

==Prerequisites==
I would like to deploy my infrastructure in another zone to have a test infrastructure.

==Unwinding==
Create a model of my cf instance: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]
# Copy my template to another zone cf: [[Copier_mon_modele_dans_une_autre_zone]]
# Deploy my template cf: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]

[[Category:Cloud_public]]
[[Catégorie :Cloud]]

Duplicate an instance in another zone

2021-07-29T15:32:50Z

Ikbot:

[[:de:Duplizieren einer Instanz in einer anderen Zone]][[de:Duplizieren einer Instanz in einer anderen Zone]]
[[:nl:Een instantie in een andere zone dupliceren]][[nl:Een instantie in een andere zone dupliceren]]
[[:it:Duplicare un'istanza in un'altra zona]][[it:Duplicare un'istanza in un'altra zona]]
[[:pt:Duplicar uma instância noutra zona]][[pt:Duplicar uma instância noutra zona]]
[[:es:Duplicar una instancia en otra zona]][[es:Duplicar una instancia en otra zona]]
[[:fr:Dupliquer une instance dans une autre zone]][[fr:Dupliquer une instance dans une autre zone]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Dupliquer une instance dans une autre zone|here]]. 
==Use cases==
I have created an instance in a BASIC zone, I would like to move my instance to an ADVANCE zone to benefit from the features of this zone.
I would like to deploy my infrastructure identically in another zone to have a test infrastructure.

==Prerequisites==
I would like to deploy my infrastructure in another zone to have a test infrastructure.

==Unwinding==
Create a model of my cf instance: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]
# Copy my template to another zone cf: [[Copier_mon_modele_dans_une_autre_zone]]
# Deploy my template cf: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]

[[Category:Cloud_public]]
[[Catégorie :Cloud]]

Duplicate an instance in another zone

2021-07-29T15:32:08Z

Ikbot:

[[:nl:Een instantie in een andere zone dupliceren]][[nl:Een instantie in een andere zone dupliceren]]
[[:it:Duplicare un'istanza in un'altra zona]][[it:Duplicare un'istanza in un'altra zona]]
[[:pt:Duplicar uma instância noutra zona]][[pt:Duplicar uma instância noutra zona]]
[[:es:Duplicar una instancia en otra zona]][[es:Duplicar una instancia en otra zona]]
[[:fr:Dupliquer une instance dans une autre zone]][[fr:Dupliquer une instance dans une autre zone]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Dupliquer une instance dans une autre zone|here]]. 
==Use cases==
I have created an instance in a BASIC zone, I would like to move my instance to an ADVANCE zone to benefit from the features of this zone.
I would like to deploy my infrastructure identically in another zone to have a test infrastructure.

==Prerequisites==
I would like to deploy my infrastructure in another zone to have a test infrastructure.

==Unwinding==
Create a model of my cf instance: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]
# Copy my template to another zone cf: [[Copier_mon_modele_dans_une_autre_zone]]
# Deploy my template cf: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]

[[Category:Cloud_public]]
[[Catégorie :Cloud]]

Duplicate an instance in another zone

2021-07-29T15:31:30Z

Ikbot:

[[:it:Duplicare un'istanza in un'altra zona]][[it:Duplicare un'istanza in un'altra zona]]
[[:pt:Duplicar uma instância noutra zona]][[pt:Duplicar uma instância noutra zona]]
[[:es:Duplicar una instancia en otra zona]][[es:Duplicar una instancia en otra zona]]
[[:fr:Dupliquer une instance dans une autre zone]][[fr:Dupliquer une instance dans une autre zone]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Dupliquer une instance dans une autre zone|here]]. 
==Use cases==
I have created an instance in a BASIC zone, I would like to move my instance to an ADVANCE zone to benefit from the features of this zone.
I would like to deploy my infrastructure identically in another zone to have a test infrastructure.

==Prerequisites==
I would like to deploy my infrastructure in another zone to have a test infrastructure.

==Unwinding==
Create a model of my cf instance: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]
# Copy my template to another zone cf: [[Copier_mon_modele_dans_une_autre_zone]]
# Deploy my template cf: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]

[[Category:Cloud_public]]
[[Catégorie :Cloud]]

Duplicate an instance in another zone

2021-07-29T15:30:58Z

Ikbot:

[[:pt:Duplicar uma instância noutra zona]][[pt:Duplicar uma instância noutra zona]]
[[:es:Duplicar una instancia en otra zona]][[es:Duplicar una instancia en otra zona]]
[[:fr:Dupliquer une instance dans une autre zone]][[fr:Dupliquer une instance dans une autre zone]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Dupliquer une instance dans une autre zone|here]]. 
==Use cases==
I have created an instance in a BASIC zone, I would like to move my instance to an ADVANCE zone to benefit from the features of this zone.
I would like to deploy my infrastructure identically in another zone to have a test infrastructure.

==Prerequisites==
I would like to deploy my infrastructure in another zone to have a test infrastructure.

==Unwinding==
Create a model of my cf instance: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]
# Copy my template to another zone cf: [[Copier_mon_modele_dans_une_autre_zone]]
# Deploy my template cf: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]

[[Category:Cloud_public]]
[[Catégorie :Cloud]]

Duplicate an instance in another zone

2021-07-29T15:30:27Z

Ikbot:

[[:es:Duplicar una instancia en otra zona]][[es:Duplicar una instancia en otra zona]]
[[:fr:Dupliquer une instance dans une autre zone]][[fr:Dupliquer une instance dans une autre zone]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Dupliquer une instance dans une autre zone|here]]. 
==Use cases==
I have created an instance in a BASIC zone, I would like to move my instance to an ADVANCE zone to benefit from the features of this zone.
I would like to deploy my infrastructure identically in another zone to have a test infrastructure.

==Prerequisites==
I would like to deploy my infrastructure in another zone to have a test infrastructure.

==Unwinding==
Create a model of my cf instance: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]
# Copy my template to another zone cf: [[Copier_mon_modele_dans_une_autre_zone]]
# Deploy my template cf: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]

[[Category:Cloud_public]]
[[Catégorie :Cloud]]

Duplicate an instance in another zone

2021-07-29T15:29:55Z

Ikbot: Created page with ":fr:Dupliquer..."

[[:fr:Dupliquer une instance dans une autre zone]][[fr:Dupliquer une instance dans une autre zone]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Dupliquer une instance dans une autre zone|here]]. 
==Use cases==
I have created an instance in a BASIC zone, I would like to move my instance to an ADVANCE zone to benefit from the features of this zone.
I would like to deploy my infrastructure identically in another zone to have a test infrastructure.

==Prerequisites==
I would like to deploy my infrastructure in another zone to have a test infrastructure.

==Unwinding==
Create a model of my cf instance: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]
# Copy my template to another zone cf: [[Copier_mon_modele_dans_une_autre_zone]]
# Deploy my template cf: [[Cr%C3%A9er_un_mod%C3%A8le_%C3%A0_partir_de_ma_VM]]

[[Category:Cloud_public]]
[[Catégorie :Cloud]]

Docker debugging a container that stops immediately

2021-07-29T15:27:59Z

Ikbot:

[[:ro:Docker depanarea unui container care se oprește imediat]][[ro:Docker depanarea unui container care se oprește imediat]]
[[:ru:Docker отлаживает контейнер, который немедленно останавливается]][[ru:Docker отлаживает контейнер, который немедленно останавливается]]
[[:pl:Docker debuguje kontener, który natychmiast się zatrzymuje]][[pl:Docker debuguje kontener, który natychmiast się zatrzymuje]]
[[:ja:すぐに停止するコンテナをDockerでデバッグする]][[ja:すぐに停止するコンテナをDockerでデバッグする]]
[[:zh:Docker调试一个立即停止的容器]][[zh:Docker调试一个立即停止的容器]]
[[:de:Docker-Debugging eines Containers, der sofort anhält]][[de:Docker-Debugging eines Containers, der sofort anhält]]
[[:nl:Docker debuggen van een container die onmiddellijk stopt]][[nl:Docker debuggen van een container die onmiddellijk stopt]]
[[:it:Docker esegue il debug di un contenitore che si ferma immediatamente]][[it:Docker esegue il debug di un contenitore che si ferma immediatamente]]
[[:pt:Depuração de um contentor que pára imediatamente]][[pt:Depuração de um contentor que pára imediatamente]]
[[:es:Docker depurando un contenedor que se detiene inmediatamente]][[es:Docker depurando un contenedor que se detiene inmediatamente]]
[[:fr:Docker déboguer un conteneur qui se stop immédiatement]][[fr:Docker déboguer un conteneur qui se stop immédiatement]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Docker déboguer un conteneur qui se stop immédiatement|here]]. 


==Introduction== 
When you start your '''docker run''' the container stops immediately, it is possible that your ''PID 1'' did not start, however you do not see anything in the logs and cannot check in your container. 
We will see how to debug a ''Docker'' container that stops immediately, by forcing a command on it at ''PID 1''.

==Course== 
Restart your '''docker run''' with the command below:
<pre>
$ docker run -d --name NOM_DE_VOTRE_CONTENEUR NOM_DE_VOTRE_IMAGE /bin/sh -c "while true; do sleep 2; df -h; done"
</pre>

This will make your '''PID 1''' will still be running, so you can check in your container if your services are running and debug them.



 
Cet article vous a semblé utile ? <vote />




<comments />


[[Category:Linux]]
[[Category:Docker]]

Docker debugging a container that stops immediately

2021-07-29T15:25:57Z

Ikbot:

[[:ru:Docker отлаживает контейнер, который немедленно останавливается]][[ru:Docker отлаживает контейнер, который немедленно останавливается]]
[[:pl:Docker debuguje kontener, który natychmiast się zatrzymuje]][[pl:Docker debuguje kontener, który natychmiast się zatrzymuje]]
[[:ja:すぐに停止するコンテナをDockerでデバッグする]][[ja:すぐに停止するコンテナをDockerでデバッグする]]
[[:zh:Docker调试一个立即停止的容器]][[zh:Docker调试一个立即停止的容器]]
[[:de:Docker-Debugging eines Containers, der sofort anhält]][[de:Docker-Debugging eines Containers, der sofort anhält]]
[[:nl:Docker debuggen van een container die onmiddellijk stopt]][[nl:Docker debuggen van een container die onmiddellijk stopt]]
[[:it:Docker esegue il debug di un contenitore che si ferma immediatamente]][[it:Docker esegue il debug di un contenitore che si ferma immediatamente]]
[[:pt:Depuração de um contentor que pára imediatamente]][[pt:Depuração de um contentor que pára imediatamente]]
[[:es:Docker depurando un contenedor que se detiene inmediatamente]][[es:Docker depurando un contenedor que se detiene inmediatamente]]
[[:fr:Docker déboguer un conteneur qui se stop immédiatement]][[fr:Docker déboguer un conteneur qui se stop immédiatement]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Docker déboguer un conteneur qui se stop immédiatement|here]]. 


==Introduction== 
When you start your '''docker run''' the container stops immediately, it is possible that your ''PID 1'' did not start, however you do not see anything in the logs and cannot check in your container. 
We will see how to debug a ''Docker'' container that stops immediately, by forcing a command on it at ''PID 1''.

==Course== 
Restart your '''docker run''' with the command below:
<pre>
$ docker run -d --name NOM_DE_VOTRE_CONTENEUR NOM_DE_VOTRE_IMAGE /bin/sh -c "while true; do sleep 2; df -h; done"
</pre>

This will make your '''PID 1''' will still be running, so you can check in your container if your services are running and debug them.



 
Cet article vous a semblé utile ? <vote />




<comments />


[[Category:Linux]]
[[Category:Docker]]

Docker debugging a container that stops immediately

2021-07-29T15:23:20Z

Ikbot:

[[:pl:Docker debuguje kontener, który natychmiast się zatrzymuje]][[pl:Docker debuguje kontener, który natychmiast się zatrzymuje]]
[[:ja:すぐに停止するコンテナをDockerでデバッグする]][[ja:すぐに停止するコンテナをDockerでデバッグする]]
[[:zh:Docker调试一个立即停止的容器]][[zh:Docker调试一个立即停止的容器]]
[[:de:Docker-Debugging eines Containers, der sofort anhält]][[de:Docker-Debugging eines Containers, der sofort anhält]]
[[:nl:Docker debuggen van een container die onmiddellijk stopt]][[nl:Docker debuggen van een container die onmiddellijk stopt]]
[[:it:Docker esegue il debug di un contenitore che si ferma immediatamente]][[it:Docker esegue il debug di un contenitore che si ferma immediatamente]]
[[:pt:Depuração de um contentor que pára imediatamente]][[pt:Depuração de um contentor que pára imediatamente]]
[[:es:Docker depurando un contenedor que se detiene inmediatamente]][[es:Docker depurando un contenedor que se detiene inmediatamente]]
[[:fr:Docker déboguer un conteneur qui se stop immédiatement]][[fr:Docker déboguer un conteneur qui se stop immédiatement]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Docker déboguer un conteneur qui se stop immédiatement|here]]. 


==Introduction== 
When you start your '''docker run''' the container stops immediately, it is possible that your ''PID 1'' did not start, however you do not see anything in the logs and cannot check in your container. 
We will see how to debug a ''Docker'' container that stops immediately, by forcing a command on it at ''PID 1''.

==Course== 
Restart your '''docker run''' with the command below:
<pre>
$ docker run -d --name NOM_DE_VOTRE_CONTENEUR NOM_DE_VOTRE_IMAGE /bin/sh -c "while true; do sleep 2; df -h; done"
</pre>

This will make your '''PID 1''' will still be running, so you can check in your container if your services are running and debug them.



 
Cet article vous a semblé utile ? <vote />




<comments />


[[Category:Linux]]
[[Category:Docker]]

Docker debugging a container that stops immediately

2021-07-29T15:22:25Z

Ikbot:

[[:ja:すぐに停止するコンテナをDockerでデバッグする]][[ja:すぐに停止するコンテナをDockerでデバッグする]]
[[:zh:Docker调试一个立即停止的容器]][[zh:Docker调试一个立即停止的容器]]
[[:de:Docker-Debugging eines Containers, der sofort anhält]][[de:Docker-Debugging eines Containers, der sofort anhält]]
[[:nl:Docker debuggen van een container die onmiddellijk stopt]][[nl:Docker debuggen van een container die onmiddellijk stopt]]
[[:it:Docker esegue il debug di un contenitore che si ferma immediatamente]][[it:Docker esegue il debug di un contenitore che si ferma immediatamente]]
[[:pt:Depuração de um contentor que pára imediatamente]][[pt:Depuração de um contentor que pára imediatamente]]
[[:es:Docker depurando un contenedor que se detiene inmediatamente]][[es:Docker depurando un contenedor que se detiene inmediatamente]]
[[:fr:Docker déboguer un conteneur qui se stop immédiatement]][[fr:Docker déboguer un conteneur qui se stop immédiatement]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Docker déboguer un conteneur qui se stop immédiatement|here]]. 


==Introduction== 
When you start your '''docker run''' the container stops immediately, it is possible that your ''PID 1'' did not start, however you do not see anything in the logs and cannot check in your container. 
We will see how to debug a ''Docker'' container that stops immediately, by forcing a command on it at ''PID 1''.

==Course== 
Restart your '''docker run''' with the command below:
<pre>
$ docker run -d --name NOM_DE_VOTRE_CONTENEUR NOM_DE_VOTRE_IMAGE /bin/sh -c "while true; do sleep 2; df -h; done"
</pre>

This will make your '''PID 1''' will still be running, so you can check in your container if your services are running and debug them.



 
Cet article vous a semblé utile ? <vote />




<comments />


[[Category:Linux]]
[[Category:Docker]]

Docker debugging a container that stops immediately

2021-07-29T15:21:37Z

Ikbot:

[[:zh:Docker调试一个立即停止的容器]][[zh:Docker调试一个立即停止的容器]]
[[:de:Docker-Debugging eines Containers, der sofort anhält]][[de:Docker-Debugging eines Containers, der sofort anhält]]
[[:nl:Docker debuggen van een container die onmiddellijk stopt]][[nl:Docker debuggen van een container die onmiddellijk stopt]]
[[:it:Docker esegue il debug di un contenitore che si ferma immediatamente]][[it:Docker esegue il debug di un contenitore che si ferma immediatamente]]
[[:pt:Depuração de um contentor que pára imediatamente]][[pt:Depuração de um contentor que pára imediatamente]]
[[:es:Docker depurando un contenedor que se detiene inmediatamente]][[es:Docker depurando un contenedor que se detiene inmediatamente]]
[[:fr:Docker déboguer un conteneur qui se stop immédiatement]][[fr:Docker déboguer un conteneur qui se stop immédiatement]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Docker déboguer un conteneur qui se stop immédiatement|here]]. 


==Introduction== 
When you start your '''docker run''' the container stops immediately, it is possible that your ''PID 1'' did not start, however you do not see anything in the logs and cannot check in your container. 
We will see how to debug a ''Docker'' container that stops immediately, by forcing a command on it at ''PID 1''.

==Course== 
Restart your '''docker run''' with the command below:
<pre>
$ docker run -d --name NOM_DE_VOTRE_CONTENEUR NOM_DE_VOTRE_IMAGE /bin/sh -c "while true; do sleep 2; df -h; done"
</pre>

This will make your '''PID 1''' will still be running, so you can check in your container if your services are running and debug them.



 
Cet article vous a semblé utile ? <vote />




<comments />


[[Category:Linux]]
[[Category:Docker]]

Docker debugging a container that stops immediately

2021-07-29T15:20:58Z

Ikbot:

[[:de:Docker-Debugging eines Containers, der sofort anhält]][[de:Docker-Debugging eines Containers, der sofort anhält]]
[[:nl:Docker debuggen van een container die onmiddellijk stopt]][[nl:Docker debuggen van een container die onmiddellijk stopt]]
[[:it:Docker esegue il debug di un contenitore che si ferma immediatamente]][[it:Docker esegue il debug di un contenitore che si ferma immediatamente]]
[[:pt:Depuração de um contentor que pára imediatamente]][[pt:Depuração de um contentor que pára imediatamente]]
[[:es:Docker depurando un contenedor que se detiene inmediatamente]][[es:Docker depurando un contenedor que se detiene inmediatamente]]
[[:fr:Docker déboguer un conteneur qui se stop immédiatement]][[fr:Docker déboguer un conteneur qui se stop immédiatement]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Docker déboguer un conteneur qui se stop immédiatement|here]]. 


==Introduction== 
When you start your '''docker run''' the container stops immediately, it is possible that your ''PID 1'' did not start, however you do not see anything in the logs and cannot check in your container. 
We will see how to debug a ''Docker'' container that stops immediately, by forcing a command on it at ''PID 1''.

==Course== 
Restart your '''docker run''' with the command below:
<pre>
$ docker run -d --name NOM_DE_VOTRE_CONTENEUR NOM_DE_VOTRE_IMAGE /bin/sh -c "while true; do sleep 2; df -h; done"
</pre>

This will make your '''PID 1''' will still be running, so you can check in your container if your services are running and debug them.



 
Cet article vous a semblé utile ? <vote />




<comments />


[[Category:Linux]]
[[Category:Docker]]

Docker debugging a container that stops immediately

2021-07-29T15:20:19Z

Ikbot:

[[:nl:Docker debuggen van een container die onmiddellijk stopt]][[nl:Docker debuggen van een container die onmiddellijk stopt]]
[[:it:Docker esegue il debug di un contenitore che si ferma immediatamente]][[it:Docker esegue il debug di un contenitore che si ferma immediatamente]]
[[:pt:Depuração de um contentor que pára imediatamente]][[pt:Depuração de um contentor que pára imediatamente]]
[[:es:Docker depurando un contenedor que se detiene inmediatamente]][[es:Docker depurando un contenedor que se detiene inmediatamente]]
[[:fr:Docker déboguer un conteneur qui se stop immédiatement]][[fr:Docker déboguer un conteneur qui se stop immédiatement]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Docker déboguer un conteneur qui se stop immédiatement|here]]. 


==Introduction== 
When you start your '''docker run''' the container stops immediately, it is possible that your ''PID 1'' did not start, however you do not see anything in the logs and cannot check in your container. 
We will see how to debug a ''Docker'' container that stops immediately, by forcing a command on it at ''PID 1''.

==Course== 
Restart your '''docker run''' with the command below:
<pre>
$ docker run -d --name NOM_DE_VOTRE_CONTENEUR NOM_DE_VOTRE_IMAGE /bin/sh -c "while true; do sleep 2; df -h; done"
</pre>

This will make your '''PID 1''' will still be running, so you can check in your container if your services are running and debug them.



 
Cet article vous a semblé utile ? <vote />




<comments />


[[Category:Linux]]
[[Category:Docker]]

Docker debugging a container that stops immediately

2021-07-29T15:19:35Z

Ikbot:

[[:it:Docker esegue il debug di un contenitore che si ferma immediatamente]][[it:Docker esegue il debug di un contenitore che si ferma immediatamente]]
[[:pt:Depuração de um contentor que pára imediatamente]][[pt:Depuração de um contentor que pára imediatamente]]
[[:es:Docker depurando un contenedor que se detiene inmediatamente]][[es:Docker depurando un contenedor que se detiene inmediatamente]]
[[:fr:Docker déboguer un conteneur qui se stop immédiatement]][[fr:Docker déboguer un conteneur qui se stop immédiatement]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Docker déboguer un conteneur qui se stop immédiatement|here]]. 


==Introduction== 
When you start your '''docker run''' the container stops immediately, it is possible that your ''PID 1'' did not start, however you do not see anything in the logs and cannot check in your container. 
We will see how to debug a ''Docker'' container that stops immediately, by forcing a command on it at ''PID 1''.

==Course== 
Restart your '''docker run''' with the command below:
<pre>
$ docker run -d --name NOM_DE_VOTRE_CONTENEUR NOM_DE_VOTRE_IMAGE /bin/sh -c "while true; do sleep 2; df -h; done"
</pre>

This will make your '''PID 1''' will still be running, so you can check in your container if your services are running and debug them.



 
Cet article vous a semblé utile ? <vote />




<comments />


[[Category:Linux]]
[[Category:Docker]]

Docker debugging a container that stops immediately

2021-07-29T15:18:48Z

Ikbot:

[[:pt:Depuração de um contentor que pára imediatamente]][[pt:Depuração de um contentor que pára imediatamente]]
[[:es:Docker depurando un contenedor que se detiene inmediatamente]][[es:Docker depurando un contenedor que se detiene inmediatamente]]
[[:fr:Docker déboguer un conteneur qui se stop immédiatement]][[fr:Docker déboguer un conteneur qui se stop immédiatement]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Docker déboguer un conteneur qui se stop immédiatement|here]]. 


==Introduction== 
When you start your '''docker run''' the container stops immediately, it is possible that your ''PID 1'' did not start, however you do not see anything in the logs and cannot check in your container. 
We will see how to debug a ''Docker'' container that stops immediately, by forcing a command on it at ''PID 1''.

==Course== 
Restart your '''docker run''' with the command below:
<pre>
$ docker run -d --name NOM_DE_VOTRE_CONTENEUR NOM_DE_VOTRE_IMAGE /bin/sh -c "while true; do sleep 2; df -h; done"
</pre>

This will make your '''PID 1''' will still be running, so you can check in your container if your services are running and debug them.



 
Cet article vous a semblé utile ? <vote />




<comments />


[[Category:Linux]]
[[Category:Docker]]

Docker debugging a container that stops immediately

2021-07-29T15:18:11Z

Ikbot:

[[:es:Docker depurando un contenedor que se detiene inmediatamente]][[es:Docker depurando un contenedor que se detiene inmediatamente]]
[[:fr:Docker déboguer un conteneur qui se stop immédiatement]][[fr:Docker déboguer un conteneur qui se stop immédiatement]]
 This article has been created by an automatic translation software. You can view the article source [[:fr:Docker déboguer un conteneur qui se stop immédiatement|here]]. 


==Introduction== 
When you start your '''docker run''' the container stops immediately, it is possible that your ''PID 1'' did not start, however you do not see anything in the logs and cannot check in your container. 
We will see how to debug a ''Docker'' container that stops immediately, by forcing a command on it at ''PID 1''.

==Course== 
Restart your '''docker run''' with the command below:
<pre>
$ docker run -d --name NOM_DE_VOTRE_CONTENEUR NOM_DE_VOTRE_IMAGE /bin/sh -c "while true; do sleep 2; df -h; done"
</pre>

This will make your '''PID 1''' will still be running, so you can check in your container if your services are running and debug them.



 
Cet article vous a semblé utile ? <vote />




<comments />


[[Category:Linux]]
[[Category:Docker]]