====== Self service system ======

The self service system allows you to check service status and perform a number of things, such as rebooting your dedicated server, by sending an email. 

Keep in mind that because of this, it's important that the email address you use is secure. Anyone with access to your email account can abuse it to gain access to other services, so your email is always the most important thing to keep safe. Please make sure you don't use the same password for your email as you do for anything else, including Xirvik service.

**__Registering with the system__** \\
The self service system is easy to use once you get the hang of it. The first thing you need to do is register with it, by sending an email, from the same email we have on file, to selfservice@xirvik.com. The subject of the email is not important, in this example we just use "hey, xirvik" but anything would work. 

The body contains the line "#register" (all comands start with a #). The system replies with a password. Note that this password is only for the self service system. It's not your seedbox password. 

{{ :self_service_tutorial_1_registration.png?direct&400 |}}

__**Getting the list of services**__\\
Once we have the password, we can get a list of services that we can manage using the self service system. This always has the form of login@hostname. However getting a list of services is convenient to confirm that we are using the right email address. 

In this example we just have one service, but it's common for users to have more than one, such as one dedicated and one shared, or several dedicated.

{{ :self_service_tutorial_2_list_services.png?direct&400 |}}

__**Getting a list of torrents**__\\
After we have the password and the service list, we can easily operate on any of the services. For example, to get a list of torrents:

{{ :self_service_tutorial_3_list_torrents_1.png?direct&400 |}}

We get a second email, which is sent directly from the server:

{{ :self_service_tutorial_3_list_torrents_2.png?direct&400 |}}

**__Getting service status__** \\
Sometimes we cannot connect to the server, and it's useful to know if the problem is that the service is down or if there's a problem somewhere between the server and ourselves. You can ask the self service system to check for you. It will try to connect to the server and check the services inside it to generate a convenient report. 

{{ :self_service_tutorial_4_check_status.png?direct&400 |}}

**__Other commands__** \\
The list of commands grows with time, as users send us feedback. 
To get a complete list, send the command 

#help

The system will return a complete list of commands with a description of each. All of them are used the same way as the previous examples: First send the password, then the service, and finally the action you want to do (such as hard reboot).