It is up to the you to report any potential security breaches with regards to your account as soon as practicable after you become aware of them. The Sooner we know, the sooner we can change your password and disable any compromised public keys. If you are aware of a breach and do not report it you may be held responsible for any and all actions done using your account whether or not you did them.
You are not permitted to share your account by any means with anyone else without prior permission from the server admins. For an account in the name of an organisation, it is your (the person named above’s) responsibility to ensure that only valid members of your organisation have access to the account.
You are not allowed to store or host any illegal material on your account. You are not allowed to host (but can store for personal use) any copyrighted media or content unless you are the copyright owner or have permission from the copyright owner. We may as to see proof of this permission.
We do not impose quotas on bandwidth, cpu usage or ram. Please remember though that they are shared resources and if we have reason to believe you are unfairly monopolising any of these resources in a way that we feel could affect our other customers or sector-alpha’s own sites we will ask you to stop by email to the email address registered on your account.
If your usage at any time causes problems to other clients or Sector Alpha Hosting’s own sites we will give you 24 hours to stop or we will intervene in whatever way necessary possibly including (but not limited to) disabling your website and user account. In cases where your usage is causing major problems to other clients or Sector Alpha Hosting’s own sites we may intervene immediately with no prior warning.
If your usage goes above what is considered fair usage but isn’t causing problems to other clients or Sector Alpha Hosting’s’s own sites we will give you 1 week to reply. If you do not reply we may choose to intervene in whatever way we consider necessary to bring your usage back to a reasonable level.
Our at risk period is currently 1:30pm-3:30pm London time, on Sundays. If updates will be happening we will email out 24 hours in advance to the email address registered on your account. If any updates take longer than the 2 hours or we have to perform emergency updates we will do our best to inform you. The at risk time may be changed at any point by us giving you 1 week notice by email to the email address registered on your account. If the at risk time is likely to be in a busy time for your site then please talk to us and we will do our best to accommodate you.
Access to files is via ftp or ftps (ftp over tls) only. For windows users we recommend filezilla (https://filezilla-project.org/). For linux users a terminal ftp client is usually provided by the operating system or a graphical client such as filezilla can be used. Note that you can use ftps but not sftp. Your username will be the one we provide.
We provide a hosting shell which can be accessed using ssh and is used to create your initial password, update your password later, add extra ssh keys for login to the hosting shell and add and remove email addresses to receive messages about down time and from the server.
Login is via ssh authenticated with an ssh key. For this reason we need you to provide an ssh public key. The server to connect to is alessa.sector-alpha.net, port 22 (the default for ss) and your username will be the one specified above.
For windows users we suggest using putty and puttygen similar to the description in https://www.howtoforge.com/ssh_key_based_logins_putty. Note that you will ot be able to login using a password and any attempt will fail to authenticate.
For linux ssh will be included on your system. Your ssh public key (which is needed in the form above) will be stored in the file ~/.ssh/id_rsa.pub. If this doesn’t exist then generate the key by running ‘ssh-keygen’ in a terminal and answering the questions (use default file to save the key in, the pass phrase it asks for is a new passphrase that is used to unlock the key when used later). Once you have a key copy the contents of ~/.ssh/id_rsa.pub into the “SSH Public Key” field above. To run ssh, from a terminal (e.g. ‘ssh email@example.com’) and as long as the default path is used when generating your ssh key it will automatically find the key, prompt for your passphrase (which you set when generating the key) and use it when logging in.
Once connected to the hosting shell help is provided via the help command (type help at the prompt).
© Copyright Sector Alpha Hosting 2018.
Designed by: Iryska