The services offered on LowEndSpirit are unmanaged i.e. self managed (By You). This allows the price to remain low.
This page will offer some general advice and help to get you started. You might also want to read unofficial guide for beginners at getLES.tk that covers steps from signing up till hosting simple static website.
Connecting to your new server
If you are lucky enough to have native IPv6 or are already running a tunnel then you can simply connect via your IPv6 address just as you would do usually via IPv4.
If you do not have native IPv6 or a tunnel then it is suggested you consider getting an IPv6 tunnel. This page will not cover this as many online guides and places to get a tunnel set up already exist such as: http://tunnelbroker.net/ or http://www.sixxs.net/
Options do exist for connecting over IPv4 such as DNAT port forwarding and console connectivity. In one of the first emails you get from us after signing up, you will find details on which ports have been configured to forward IPv4 connections to your VPS; one of which will be for SSH connectivity.
The final option for connecting will be via the virtual console connection. You can use this via the SolusVM control panel or direct connect via SSH using your console username and password - provided again via SolusVM.
So how can I host a website if I do not have a dedicated IPv4 address?
Well strictly speaking you do have an IPv4 address albeit a private unrouted one, e.g. 192.168.0.10 . Now obviously you cannot usually connect to this from the outside world, so we have set up a reverse proxy on each node to allow you to host a website or any service with TCP headers. We use haproxy which is capable of header based forwarding.
An example of how this works would be that you point a domain at the IPv4 address you have been given for this purpose. For the sake of this example we will use 126.96.36.199 as the IP and example.com as the domain.
We would then set up your reverse proxy connection for you. You then set up your website or service as you normally would.
When an internet user attempts to reach example.com a DNS lookup will be done and they will be told that example.com lives at 188.8.131.52. The request will then be made by the internet user's browser. This request will contain the header example.com. When the request reaches our reverse proxy it will forward that request on to your servers private IPv4 address e.g. 192.168.0.10 which will then serve the information or website requested.
Internet user => haproxy on VPS node => your VPS => your service => Internet user.
What limitations can I expect?
With private addresses we cannot set rDNS records for IPv4 and only in some cases will we be able to do this for IPv6 - so email services may not be a reliable option, and in some locations email may be blocked completely to avoid abuse.
If you install software that requires specific ports in order to run, this may not be viable over IPv4.
If you are running TCP based services that do not use TCP Headers then this may also not be an option.
For further information please consult the FAQ page.
What support is offered with this service?
In a nutshell, very little. It is not intended for novice users or those who are unwilling to learn new things.