Officelucky

• Linode Tokyo No Open Slots For This Plan Youtube

At Linode, we’re incredibly passionate about helping our customers. That means more than just answering tickets or phone calls—we’re here to solve real problems for people trying to get stuff done. This is why we’re deeply involved in the greater customer support community, and for us, there’s no better community than Elevate. Aug 02, 2019  New Priority Pass Lounge At Palm Beach Airport To Open In January. Delta Plans Big Changes For Tokyo And Singapore. American Airlines is also making changes to its Bolivia route. That has become less of a problem now that a dozen new slots have been opened up for airlines from the United States. Delta has been granted five of the slots.

What is Yubikey?

YubiKeys are small USB dongles that you can plug into your computer. They can simulate keyboard input, allowing you to enter One Time Passwords (OTPs) with the press of a button to authenticate with services like Google, Dropbox and GitHub.

YubiKeys can also be used when logging into a remote server. This guide will show you how to configure your Linode so that a YubiKey must be plugged in and tapped in order to log in to your server using ssh. Depending on your needs, you can also configure a password in addition to the YubiKey for an extra level of security.

If you want to work through this guide but don't have a YubiKey, you can find one at this link. As of this writing, any key that supports 'Yubico OTP' will support two-factor SSH authentication.

Before You Begin

1. Make sure you have a complete and working Linode as per the instructions in the Getting Started guide.

2. This guide will use sudo wherever possible. Complete the sections of our Securing Your Server to create a standard user account, harden SSH access and remove unnecessary network services.

3. Update your local system. Then update your server using the following:

4. Test your YubiKey at demo.yubico.com to make sure it's working correctly.

{{< note >}}Replace each instance of user@example.com in this guide with your site's domain name and the appropriate user.{{< /note >}}

Configure Your YubiKey

If your YubiKey still has its default configuration, you can skip this step. If you've made some changes, this section will tell you how to put the appropriate configuration for this guide onto slot 1 of your YubiKey. If you want to use a different slot, make sure you select it instead of slot 1 in the following instructions.

1. Install the YubiKey Personalization Tool for your system and open it.

2. Click on the 'Yubico OTP' menu in the top-left corner, and select 'Quick'. Your screen should look like the one below.

3. Click 'Write Configuration'. Click 'Cancel' on the pop-up window that asks where to save the log file.

4. Now select 'Upload to Yubico'. In the web form that opens, fill in your email address. Select the field asking for an 'OTP from the YubiKey' and touch the button on your YubiKey (or touch and hold if you programmed slot 2). This should fill the field with a string of letters. Complete the captcha and press 'Upload AES key'.

   {{< note >}}The page will respond with a table containing your key information. You should keep this data in a safe place. Should you ever lose your YubiKey, you will need this data to reconfigure a new one with the same settings.{{< /note >}}

5. Test that your key works by following the instructions for single-factor authentication on demo.yubico.com. If it doesn't, you may need to wait up to 15 minutes for your key to process on their servers.

Install the Authentication Software

1. Register for an API key here, by entering your email address and (with the 'YubiKey one time password' field selected) touching the button on your YubiKey. Keep the Client ID and Secret Key returned by the website.

   {{< note >}}On Ubuntu, you may need to install software-properties-common and python-software-properties to add the repository.{{< /note >}}

2. On your Linode, install the pam_yubico package.

   On Ubuntu:

   On Debian (Wheezy):

   On Fedora/EPEL/Arch Linux:

   Yubico's documentation also has instructions on how to build pam_yubico from source.

   {{< note >}}You may need to move pam_yubico.so to wherever PAM modules are stored on your system (usually lib/security). The Ubuntu package will automatically install the module in the appropriate location, but you can check to see whether it's in the right location with ls /lib/security. It may also be stored in /usr/local/lib/security, in which case you will need to move it manually.{{< /note >}}

3. Create the file /etc/ssh/authorized_yubikeys:

4. Populate this file with the usernames for which you want to enable two-factor authentication and their YubiKey IDs. You can obtain the ID by opening a text editor and touching the button on the YubiKey, and selecting only the first 12 characters. The first line below would be a typical configuration. The subsequent lines show a configuration where users user2, user3, and user4 use multiple YubiKeys and plan to access the server with all of them.

   {{< file '/etc/ssh/authorized_yubikeys' >}}user1:vvklhtiubdcuuser2:ccurrufnjder:ccturefjtehv:cctbhunjimkouser3:ccdvnvlcbdre:vvvglinuddekuser4:vvddhfjjasui:vvfjidkflssd

{{< /file >}}

5. Add auth required pam_yubico.so id=<client id> key=<secret key> authfile=/etc/ssh/authorized_yubikeys to the start of /etc/pam.d/sshd. Replace <client id> with the ID you retrieved when applying for an API key, and <secret key> with the secret key. If you only want single-factor authentication (either a YubiKey or a password), change required to sufficient to tell the system that a valid YubiKey will be enough to log in.

   {{< file '/etc/pam.d/sshd' >}}

auth required pam_yubico.so id=client id key=secret key authfile=/etc/ssh/authorized_yubikeys

@include common-auth

{{< /file >}}

On some systems, like Arch Linux, you will need to edit /etc/pam.d/system-remote-login instead of /etc/pam.d/sshd.{{< /note >}}

6. In /etc/ssh/sshd_config, add or edit the following settings:

   {{< file '/etc/ssh/sshd_config' >}}ChallengeResponseAuthentication yesUsePAM yes

{{< /file >}}

7. Restart the sshd daemon to allow the changes to take effect:

Test the YubiKey

Now that this process is done, you can test your login by logging out and back in:

Depending on your setup, you may be prompted for your YubiKey. All you need to do is touch the button; it will enter the key for you. Then, type in your password if you are using multi-factor authentication. It will look something like the image below.

You can now log into your server.

Troubleshoot YubiKey

If you encounter any problems, make sure you've followed all of the steps in this guide and restarted your server. If these steps don't solve your issues, you can enable logging, by following these steps:

1. Add the word debug to the end of the line you added in /etc/pam.d/sshd:

   {{< file '/etc/pam.d/sshd' >}}auth required pam_yubico.so id= key= authfile=/etc/ssh/authorized_yubikeys debug

{{< /file >}}

2. Create a debug log file:

3. Log data to this file:

4. Log in again and analyze this file for clues as to what is causing the problem.

5. Once you're done, disable debugging by removing the debug flag from /etc/pam.d/sshd. Then, delete the log file.

Linode’s Block Storage service allows you to attach additional storage Volumes to your Linode. A single Volume can range from 10 GiB to 10,000 GiB in size and costs $0.10/GiB per month. They can be partitioned however you like and can accommodate any filesystem type you choose. Up to eight Volumes can be attached to a single Linode, be it new or already existing, so you do not need to recreate your server to add a Block Storage Volume.

Linode Tokyo No Open Slots For This Plan Youtube

The Block Storage service is currently available in the Dallas, Fremont, Frankfurt, London, Newark, Tokyo, Toronto, Mumbai, and Singapore data centers.

{{< caution >}}

• Linode's backup services do not cover Block Storage Volumes. You must execute your own backups for this data.

• Your Linode must be running in Paravirtualization mode. Block storage currently does not support Full-virtualization.{{< /caution >}}

How to Add a Block Storage Volume to a Linode

This guide assumes a Linode with the root disk mounted as /dev/sda and swap space mounted as /dev/sdb. In this scenario, the Block Storage Volume will be available to the operating system as /dev/disk/by-id/scsi-0Linode_Volume_EXAMPLE, where EXAMPLE is a label you assign the Volume in the Linode Cloud Manager. Storage Volumes can be added when your Linode is already running, and will show immediately in /dev/disk/by-id/.

Add a Volume from the Linode Detail Page

1. Click on the Linodes link in the sidebar.

2. Select the Linode to which you want to attach a Block Storage Volume. The detail page for the Linode will appear.

3. Click on the Volumes tab, then click Add a Volume:

4. Assign the Block Storage Volume a label and size. The label can be up to 32 characters long and consist only of ASCII characters a-z; 0-9.-_. The maximum Volume size is 10,000 GiB. When finished, click Submit:

   {{< note >}}There is currently a soft limit of 100 TB of Block Storage Volume per account.{{< /note >}}

5. Once you add a Volume it will appear under Attached Volumes with the new Volume's label, size, and file system path.

6. You'll need to create a filesystem in your new Volume. If your Linode is not already running, boot then SSH into your Linode and execute the following command, where FILE_SYSTEM_PATH is your Volume's file system path:

7. Once the Volume has a filesystem, you can create a mountpoint for it:

8. You can then mount the new Volume:

9. If you want to mount the new Volume automatically every time your Linode boots, you'll want to add the following line to your /etc/fstab file:

   {{< note >}}If you plan on detaching the volume regularly or moving it between other Linodes, you may want to consider adding the flags noatime and nofail to the /etc/fstab entry.

• noatime - This will save space and time by preventing writes made to the filesystem for data being read on the volume.
• nofail - If the volume is not attached, this will allow your server to boot/reboot normally without hanging at dependency failures if the volume is not attached.

Example:

Attach a Volume from Your Account's Volume List

1. Click on the Volumes link in the sidebar to see your account's Volume list:

2. Click the more options ellipsis to open the menu for the Volume you want to attach to a Linode and select Attach:

3. Select the label of the Linode you want to attach the Volume to from the dropdown menu, then click Save:

   {{< note >}}The Linodes available in this dropdown menu all share the same region as your Volume.{{< /note >}}

4. You'll need to create a filesystem in your new Volume. If your Linode is not already running, boot then SSH into your Linode and execute the following command, where FILE_SYSTEM_PATH is your Volume's file system path:

5. Once the Volume has a filesystem, you can create a mountpoint for it:

6. You can then mount the new Volume, where FILE_SYSTEM_PATH is your Volume's file system path:

7. If you want to mount the new Volume automatically every time your Linode boots, you'll want to add the following line to your /etc/fstab file:

How to Detach a Block Storage Volume from a Linode

1. Go to the detail page page of the Linode which the Volume is attached to. Shut down the Linode.

2. When the Linode is powered off, click on the Volumes tab, click the more options ellipsis next to the Volume you would like to detach, then click Detach.

3. A confirmation screen appears and explains that the Volume will be detached from the Linode. Click Detach to confirm:

   The Linode's dashboard does not show the Volume present anymore:

   The Volume still exists on your account and you can see it if you view the Volumes page:

{{< caution >}}If a volume is currently mounted, detaching it while the Linode is powered on could cause data loss or an unexpected reboot. You can unmount the volume for safe live-detaching using the umount command:

To avoid additional issues with your Linode, remove the detached volume's line from your /etc/fstab/ configuration:

FILE_SYSTEM_PATH /mnt/BlockStorage1 ext4 defaults 0 2

{{< /caution >}}

How to Delete a Block Storage Volume

{{< caution >}}The removal process is irreversible, and the data will be permanently deleted.{{< /caution >}}

1. Shut down the attached Linode.

2. Detach the Volume as described above.

3. On the Volumes page, click the more options ellipsis next to the Volume you would like to delete.

4. Click Delete.

How to Resize a Block Storage Volume

Storage Volumes cannot be sized down, only up. Keep this in mind when sizing your Volumes.

1. Shut down your Linode.

2. Click the more options ellipsis next to the Volume you would like to resize to bring up the Volume's menu.

3. Click Resize.

4. Enter the new Volume size. The minimum size is 10 GiB and maximum is 10,000 GiB. Then click Submit.

5. You'll be returned to the Volume list and the notification bell in the top right of the page will notify you when the resizing is complete.

6. Reboot your Linode.

7. Once your Linode has restarted, make sure the Volume is unmounted for safety:

8. Assuming you have an ext2, ext3, or ext4 partition,first run a file system check:

9. Then resize it to fill the new Volume size:

10. Mount your volume back onto the filesystem:

How to Transfer Block Storage Data Between Data Centers

Block Storage volumes cannot be directly migrated to a different Data Center. This section will show you how to transfer a volume's data to a different data center.

{{< note >}}Consult our Network Transfer Quota guide for information on charges related to outbound traffic when downloading Linode data outside of Linode's private network.{{</ note >}}

Use SCP to Transfer Block Storage Volume Data to Another Data Center

1. Attach and mount your Block Storage volume to a Linode, if you have not already.

2. Use the Secure Copy Protocol (SCP) to download your volume's data to the receiving computer or Linode.

   {{< note >}}You will need a device that has enough storage capacity to receive the entirety of your Block Storage volume's data.{{</ note >}}

3. Once your Block Storage volume's data has been copied, create a new Block Storage volume in the desired data center and attach it to a Linode.

4. Use SCP to upload the data from the receiving computer or Linode to the new Block Storage volume. The new Block Storage volume must be attached and mounted to a Linode.

Where to Go From Here?

Need ideas for what to do with space? We have several guides which walk you through installing software that would make a great pairing with large storage Volumes: