Difference between revisions of "Frequently asked questions"

Revision as of 14:40, 20 March 2015

Cannot connect with SSH to newly booted VM

The provisioning and booting process may take as long as five minutes in some cases, depending on the specific operating system you are selecting. You can monitor progress over VNC by hitting the VNC Connection button. Once booted, you will be able to authenticate via SSH using the username and password displayed on the virtual machine page (or SSH key if you specified one).

Note that if you selected an image marked "ISO" when provisioning the VM, you will have to install the operating system via VNC. If you simply want a ready-made VM up and running, you should select an image marked "template" instead.

I cannot ping my IP address 172.20.8.187

The IP address starting with 172 is the private IP address for your VM. Go to your VM details page and look for the "external IP address".

How to purchase the Special XYZ plan?

First, check https://dynamic.lunanode.com/info.php to make sure it is still in stock. If so, you can register an account and then go to the Create VM sidebar option to create the VM of your desired special plan. Note that special plans are only available for a limited time.

Do you support IPv6?

Currently we do not support IPv6. Our hardware is fully IPv6 ready and we have IPv6 allocation ready, we are waiting for next OpenStack release Kilo (estimated May 2015) to fully support IPv6 with prefix allocation.

My account request was denied

We do not accept new account registrations from proxies, hosting services, or other non-residential/business IP addresses. Please contact support@lunanode.com if you do not know why your account request was denied.

How to resize my VM?

To upgrade your VM, follow these steps:

1. Snapshot your VM
2. Provision a new VM from the snapshot with your desired plan
3. Ensure new VM is functioning
4. Detach the floating IP from both old and new VM
5. Attach the old floating IP to the new VM

To downgrade, you will need to resize your disk. Contact support if you need assistance doing this.

Unable to attach volume to my Windows VM

Volumes are best used with Linux virtual machines using the virtio driver. If you are using another operating system or ide driver, then you likely will need to shut down the VM before attaching or detaching volumes. You may also need to specify the attachment target as /dev/hdc or /dev/hdd or etc.

I cannot login as root!

As stated in the "VM provisioned successfully" email, template-based virtual machines are configured to accept connections with the administrative user. The username and password are displayed on the virtual machine details page. For security reasons, the VM does not accept root login by default.

Once authenticated as the administrative user, you can execute sudo su to login as root.

If you wish, you can of course set a root password. First, login as root by authenticating with the administrative user and running sudo su. Then, run passwd to set a root user password. Finally, edit the SSH configuration:

sed -i 's/PermitRootLogin.*/PermitRootLogin yes/' /etc/ssh/sshd_config
service ssh restart; service sshd restart

Then logout and you should be able to authenicate via SSH directly as the root user with your newly set password.

Alternatively, you can use a startup script so that the root password is set when the VM boots.

Note: use an SSH client like Putty to authenticate.

Please note that our services are unmanaged and you are responsible or the security of your VM; if your VM is taken over and used in denial of service attacks, spam, or other activities that violate our terms of service, your account may be suspended depending on the circumstances.

Is additional bandwidth usage billed hourly? What about CPU usage for flexible plans?

Both bandwidth and CPU are billed as consumable resources, i.e., you are charged for the amount that you use. For example, if you use 5 GB bandwidth, then you will be billed $0.003 for each GB, and it does not matter how long it takes you to use that 5 GB. Similarly, for CPU usage, if you use 10 CPU-core-hours (e.g. 5% of a CPU core for 200 hours, or 100% of a CPU core for 10 hours) then you will be billed $0.22, and again it doesn't matter what timespan you use it over.

So, the question of whether we bill "hourly" versus "monthly" doesn't make sense for flexible resources (including additional bandwidth on all plans, as well as bandwidth / CPU for flexible plans). For fixed resources (memory, disk size, etc.), though, we do bill hourly.

If you are still confused, this is probably because you are used to monthly providers that may charge for additional CPU core or additional 1 TB bandwidth for the next month. The reason that monthly providers do this is because they don't expect you to use the full allocation, and if you only use 500 GB additional bandwidth then they save 500 GB on their end. However, in our case, we charge for resources as they are being consumed instead of in advance, so hourly versus monthly no longer matters, and you only need to pay for what you use.

My disk space is smaller than the plan disk

Almost all of the templates will automatically resize the partition and filesystem the first time that the virtual machine boots. If you install from ISO, you can also choose the partitioning scheme.

So, if you are having this problem where filesystem doesn't actually get resized, it likely means you are using the CentOS 6 template, which does not support automatic filesystem resizing. You can instead run the following commands to manually resize the partition/filesystem:

fdisk /dev/vda
> u
> p
> d 1
(this will print "Selected partition 1" and delete the first partition)
> n
(select "p" for primary partition)
(partition number should be 1, but make sure it matches the number displayed in print command)
(first sector should be 2048, but make sure it matches the "Start" column displayed in print command)
(and set last sector to the default value)
> a
(type "1" to make new first partition bootable)
> w
(this will write the new partitions and exit fdisk)
shutdown -r 0
(connect to VM after it reboots, if it has resized partition but not filesystem then run resize2fs)