From 1ca91ab9f9a9ed0ea5c4ec2ad50e2c914a5b5a2a Mon Sep 17 00:00:00 2001 From: Matthew Wildman Date: Tue, 30 Jul 2024 11:59:01 -0400 Subject: [PATCH] Fix internal links (#7063) * Update internal links * Fix anchor links --- .../index.md | 2 +- .../index.md | 4 ++-- .../install-and-configure-owncloud-on-debian-10/index.md | 2 +- .../install-and-configure-owncloud-on-ubuntu-20-04/index.md | 2 +- .../deploy-linodes-using-linode-ansible-collection/index.md | 2 +- .../index.md | 2 +- .../using-metadata-cloud-init-on-any-distribution/index.md | 2 +- .../packer/deploy-packer-image-with-terraform/index.md | 2 +- .../pulumi/deploy-in-code-with-pulumi/index.md | 2 +- .../index.md | 2 +- .../index.md | 2 +- .../index.md | 2 +- .../containers/using-nomad-for-orchestration/index.md | 2 +- .../applications/project-management/install-farmos/index.md | 2 +- .../index.md | 2 +- docs/guides/development/nodejs/nodejs-twitter-bot/index.md | 4 ++-- .../use-paramiko-python-to-ssh-into-a-server/index.md | 2 +- .../install-apache-subversion-ubuntu/index.md | 2 +- .../deploy-7-days-to-die-linux-game-server/index.md | 4 ++-- docs/guides/kubernetes/deploy-nginx-ingress-on-lke/index.md | 2 +- .../index.md | 2 +- .../index.md | 2 +- .../dns/dns-primary-and-secondary-server-setup/index.md | 4 ++-- .../networking/dns/introduction-to-dns-on-linux/index.md | 2 +- .../networking/vpn/set-up-wireguard-vpn-on-debian/index.md | 2 +- .../networking/vpn/set-up-wireguard-vpn-on-ubuntu/index.md | 2 +- .../how-to-migrate-from-gcp-to-linode/index.md | 2 +- .../migrating-a-server-to-your-linode/index.md | 2 +- .../how-to-use-the-linode-api-with-twilio/index.md | 2 +- .../a-beginners-guide-to-selinux-on-centos-7/index.md | 2 +- .../a-beginners-guide-to-selinux-on-centos-8/index.md | 2 +- .../install-a-custom-distribution-on-a-xen-linode/index.md | 2 +- .../run-a-distributionsupplied-kernel-with-pvgrub/index.md | 2 +- docs/guides/uptime/analytics/plausible/index.md | 2 +- docs/guides/uptime/monitoring/_index.md | 2 +- .../how-to-use-monitorix-for-system-monitoring/index.md | 2 +- .../lamp/how-to-create-a-lamp-stack-application/index.md | 2 +- .../lemp/how-to-create-a-lemp-stack-application/index.md | 2 +- docs/guides/websites/cms/strapi/using-strapi-cms/index.md | 2 +- .../index.md | 2 +- .../erp/install-an-odoo-13-stack-on-debian-10/index.md | 2 +- .../hosting/secure-website-lets-encrypt-acme-sh/index.md | 2 +- .../hosting/set-up-web-server-host-website/index.md | 2 +- .../products/compute/compute-instances/get-started/index.md | 2 +- docs/products/compute/compute-instances/guides/_index.md | 2 +- .../compute-instances/guides/disks-and-storage/index.md | 2 +- .../compute/compute-instances/guides/distributions/index.md | 2 +- .../compute-instances/guides/failover-bgp-frr/index.md | 4 ++-- .../guides/manual-network-configuration/index.md | 2 +- .../compute/compute-instances/guides/metadata/index.md | 2 +- .../guides/migrate-to-different-dc/index.md | 2 +- .../compute-instances/guides/placement-groups/index.md | 2 +- .../compute-instances/guides/rescue-and-rebuild/index.md | 2 +- .../compute-instances/guides/set-up-and-secure/index.md | 2 +- .../guides/troubleshooting-connection-issues/index.md | 2 +- .../guides/troubleshooting-firewall-issues/index.md | 2 +- .../guides/troubleshooting-ssh-issues/index.md | 2 +- docs/products/compute/kubernetes/developers/index.md | 2 +- docs/products/compute/kubernetes/guides/_index.md | 4 ++-- .../deploy-and-manage-cluster-with-the-linode-api/index.md | 2 +- .../compute/kubernetes/guides/load-balancing/index.md | 2 +- .../kubernetes/guides/secure-a-cluster-with-rbac/index.md | 2 +- .../kubernetes/guides/upgrade-kubernetes-version/index.md | 2 +- .../cloud-firewall/guides/apply-to-service/index.md | 2 +- .../networking/dns-manager/guides/a-record/index.md | 2 +- .../guides/manage-nodebalancers-with-linode-api/index.md | 2 +- .../products/networking/vpc/guides/assign-services/index.md | 2 +- docs/products/networking/vpc/guides/create/index.md | 2 +- docs/products/platform/get-started/_index.md | 2 +- .../guides/manage-block-storage-with-linode-api/index.md | 2 +- docs/products/tools/api/get-started/index.md | 2 +- docs/products/tools/api/guides/_index.md | 2 +- docs/products/tools/cli/guides/cli-v3/index.md | 6 +++--- docs/products/tools/cli/guides/install/index.md | 4 ++-- docs/products/tools/images/guides/_index.md | 2 +- .../images/guides/deploy-image-to-existing-linode/index.md | 2 +- .../marketplace-custom-domain-fields-shortguide/index.md | 2 +- .../tools/marketplace/guides/apache-kafka-cluster/index.md | 2 +- docs/products/tools/marketplace/guides/chevereto/index.md | 2 +- docs/products/tools/marketplace/guides/cyberpanel/index.md | 2 +- docs/products/tools/marketplace/guides/discourse/index.md | 2 +- docs/products/tools/marketplace/guides/flask/index.md | 2 +- .../tools/marketplace/guides/galera-cluster/index.md | 2 +- docs/products/tools/marketplace/guides/gitea/index.md | 2 +- .../tools/marketplace/guides/glusterfs-cluster/index.md | 2 +- .../guides/hashicorp-nomad-clients-cluster/index.md | 2 +- .../marketplace/guides/hashicorp-nomad-cluster/index.md | 2 +- docs/products/tools/marketplace/guides/jenkins/index.md | 2 +- docs/products/tools/marketplace/guides/jupyterlab/index.md | 2 +- docs/products/tools/marketplace/guides/linuxgsm/index.md | 2 +- docs/products/tools/marketplace/guides/mastodon/index.md | 2 +- docs/products/tools/marketplace/guides/mistio/index.md | 2 +- .../tools/marketplace/guides/mongodb-cluster/index.md | 2 +- .../tools/marketplace/guides/nats-single-node/index.md | 2 +- docs/products/tools/marketplace/guides/openvpn/index.md | 2 +- .../guides/percona-monitoring-management/index.md | 2 +- docs/products/tools/marketplace/guides/plex/index.md | 4 ++-- .../tools/marketplace/guides/postgresql-cluster/index.md | 2 +- .../tools/marketplace/guides/redis-cluster/index.md | 2 +- docs/products/tools/marketplace/guides/splunk/index.md | 2 +- 100 files changed, 110 insertions(+), 110 deletions(-) diff --git a/docs/guides/applications/big-data/big-data-in-the-linode-cloud-streaming-data-processing-with-apache-storm/index.md b/docs/guides/applications/big-data/big-data-in-the-linode-cloud-streaming-data-processing-with-apache-storm/index.md index 53ca7569150..7bf413b4c92 100644 --- a/docs/guides/applications/big-data/big-data-in-the-linode-cloud-streaming-data-processing-with-apache-storm/index.md +++ b/docs/guides/applications/big-data/big-data-in-the-linode-cloud-streaming-data-processing-with-apache-storm/index.md @@ -78,7 +78,7 @@ These are the names we'll use, but you are welcome to choose your own when creat ### Get a Linode API Key -Follow the steps in [Generating an API Key](/docs/products/tools/api/guides/manage-api-tokens/) and save your key securely. It will be entered into configuration files in upcoming steps. +Follow the steps in [Generating an API Key](/docs/products/platform/accounts/guides/manage-api-tokens/) and save your key securely. It will be entered into configuration files in upcoming steps. If the key expires or is removed, remember to create a new one and update the `api_env_linode.conf` API environment configuration file on the cluster manager Linode. This will be explained further in the next section. diff --git a/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-centos-stream-8/index.md b/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-centos-stream-8/index.md index 7f676376dbc..5dd514d0a08 100644 --- a/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-centos-stream-8/index.md +++ b/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-centos-stream-8/index.md @@ -83,7 +83,7 @@ ownCloud requires a full LAMP (Linux, Apache, MySQL, PHP) stack. In this section sudo firewall-cmd --reload ``` -1. Ensure you can reach the Apache server. Open a web browser, and enter in your [Linode's IP address](/docs/guides/find-your-linodes-ip-address/). For example, enter in `http://192.0.2.0` and replace the IP address with your own. You should see the Apache welcome page. +1. Ensure you can reach the Apache server. Open a web browser, and enter in your [Linode's IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). For example, enter in `http://192.0.2.0` and replace the IP address with your own. You should see the Apache welcome page. #### Install MariaDB @@ -228,7 +228,7 @@ Apache requires a [virtual host configuration file](https://httpd.apache.org/doc sudo nano /etc/httpd/conf.d/owncloud.conf ``` -1. Paste the following text into the new file. Replace mentions of `example.com` with your own domain name or your [Linode's IP Address](/docs/guides/find-your-linodes-ip-address/): +1. Paste the following text into the new file. Replace mentions of `example.com` with your own domain name or your [Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/): ```file {title="etc/httpd/conf.d/owncloud.conf"} Alias /owncloud "/var/www/html/owncloud/" diff --git a/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-debian-10/index.md b/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-debian-10/index.md index 347b0976f0b..2afa24a5442 100644 --- a/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-debian-10/index.md +++ b/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-debian-10/index.md @@ -162,7 +162,7 @@ Apache requires a [virtual host configuration file](https://httpd.apache.org/doc sudo nano /etc/apache2/sites-available/owncloud.conf -1. Paste the following text into the new file. Replace mentions of `example.com` with your own domain name or your [Linode's IP Address](/docs/guides/find-your-linodes-ip-address/): +1. Paste the following text into the new file. Replace mentions of `example.com` with your own domain name or your [Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/): {{< file "/etc/apache2/sites-available/owncloud.conf">}} diff --git a/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-ubuntu-20-04/index.md b/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-ubuntu-20-04/index.md index f307c454f45..422f2e65eb6 100644 --- a/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-ubuntu-20-04/index.md +++ b/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-ubuntu-20-04/index.md @@ -156,7 +156,7 @@ Apache requires a [virtual host configuration file](https://httpd.apache.org/doc sudo nano /etc/apache2/sites-available/owncloud.conf -1. Paste the following text into the new file. Replace mentions of `example.com` with your own domain name or your [Linode's IP Address](/docs/guides/find-your-linodes-ip-address/): +1. Paste the following text into the new file. Replace mentions of `example.com` with your own domain name or your [Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/): {{< file "/etc/apache2/sites-available/owncloud.conf">}} diff --git a/docs/guides/applications/configuration-management/ansible/deploy-linodes-using-linode-ansible-collection/index.md b/docs/guides/applications/configuration-management/ansible/deploy-linodes-using-linode-ansible-collection/index.md index c7b94e4b8c1..dfda63725bb 100644 --- a/docs/guides/applications/configuration-management/ansible/deploy-linodes-using-linode-ansible-collection/index.md +++ b/docs/guides/applications/configuration-management/ansible/deploy-linodes-using-linode-ansible-collection/index.md @@ -88,7 +88,7 @@ The Linode Ansible collection is now installed and ready to deploy and manage Li ## Configure Ansible -When interfacing with the Linode Ansible collection, it is generally good practice to use variables to securely store sensitive strings like API tokens. This section shows how to securely store and access the [Linode API Access token](/docs/products/tools/api/guides/manage-api-tokens/) (generated in the [Before You Begin](#before-you-begin) section) along with a root password that is assigned to new Linode instances. Both of these are encrypted with [Ansible Vault](https://docs.ansible.com/ansible/latest/user_guide/vault.html). +When interfacing with the Linode Ansible collection, it is generally good practice to use variables to securely store sensitive strings like API tokens. This section shows how to securely store and access the [Linode API Access token](/docs/products/platform/accounts/guides/manage-api-tokens/) (generated in the [Before You Begin](#before-you-begin) section) along with a root password that is assigned to new Linode instances. Both of these are encrypted with [Ansible Vault](https://docs.ansible.com/ansible/latest/user_guide/vault.html). ### Create an Ansible Vault Password File diff --git a/docs/guides/applications/configuration-management/ansible/use-ansible-to-automate-web-server-infrastructure/index.md b/docs/guides/applications/configuration-management/ansible/use-ansible-to-automate-web-server-infrastructure/index.md index 27720af1d98..72a708ad254 100644 --- a/docs/guides/applications/configuration-management/ansible/use-ansible-to-automate-web-server-infrastructure/index.md +++ b/docs/guides/applications/configuration-management/ansible/use-ansible-to-automate-web-server-infrastructure/index.md @@ -383,7 +383,7 @@ Ansible playbooks are what makes Ansible powerful software. The syntax of the ta Using `scp`, the above files are sent to the Ansible control node. You can then log into the control node and execute the control node script, `ansibleCN_setup.sh`. {{< note >}} -Throughout all the steps in this section, replace `VM1_IPADDRESS` with the [IP address](/docs/guides/find-your-linodes-ip-address/) obtained from either the Linode CLI or Cloud Manager. +Throughout all the steps in this section, replace `VM1_IPADDRESS` with the [IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) obtained from either the Linode CLI or Cloud Manager. {{< /note >}} {{< note type="alert" >}} diff --git a/docs/guides/applications/configuration-management/cloud-init/using-metadata-cloud-init-on-any-distribution/index.md b/docs/guides/applications/configuration-management/cloud-init/using-metadata-cloud-init-on-any-distribution/index.md index a8b875ef878..aeada4450c5 100644 --- a/docs/guides/applications/configuration-management/cloud-init/using-metadata-cloud-init-on-any-distribution/index.md +++ b/docs/guides/applications/configuration-management/cloud-init/using-metadata-cloud-init-on-any-distribution/index.md @@ -127,7 +127,7 @@ A few configuration steps are necessary to prepare the cloud-init installation f ``` ## Create a Custom Image -Creating an image from the instance setup above allows you to deploy new instances leveraging the Metadata service and custom cloud-init deployment scripts. For more on creating an image of an Akamai Compute Instance, you can refer to our [Capture an Image](/docs/products/tools/images/guides/capture-an-image/#capturing-an-image-through-the-cloud-manager) guide. +Creating an image from the instance setup above allows you to deploy new instances leveraging the Metadata service and custom cloud-init deployment scripts. For more on creating an image of an Akamai Compute Instance, you can refer to our [Capture an Image](/docs/products/tools/images/guides/capture-an-image/#capturing-an-image-through-cloud-manager) guide. What follows is a summary of steps you can use to create a base image from the instance on which you installed cloud-init. diff --git a/docs/guides/applications/configuration-management/packer/deploy-packer-image-with-terraform/index.md b/docs/guides/applications/configuration-management/packer/deploy-packer-image-with-terraform/index.md index 8694aa55501..45676cb38a1 100644 --- a/docs/guides/applications/configuration-management/packer/deploy-packer-image-with-terraform/index.md +++ b/docs/guides/applications/configuration-management/packer/deploy-packer-image-with-terraform/index.md @@ -222,7 +222,7 @@ This tutorial handles variables using two files. image_id = "private/" ``` - The `` needs to be an API token associated with your Linode account. You can follow our [Get an API Access Token](/docs/products/tools/api/guides/manage-api-tokens/) guide to generate a personal access token. Be sure to give the token "Read/Write" permissions. + The `` needs to be an API token associated with your Linode account. You can follow our [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/) guide to generate a personal access token. Be sure to give the token "Read/Write" permissions. Above, you can see a value of `private/` for the `image_id`. This value should match the image ID for the Linode image you created with Packer. All custom Linode images are prefaced with `private/` and conclude with the image's ID. In these examples, `private/17691867` is assumed to be the ID for the Linode image built with Packer. diff --git a/docs/guides/applications/configuration-management/pulumi/deploy-in-code-with-pulumi/index.md b/docs/guides/applications/configuration-management/pulumi/deploy-in-code-with-pulumi/index.md index a63f2b7100a..765d7ff4648 100644 --- a/docs/guides/applications/configuration-management/pulumi/deploy-in-code-with-pulumi/index.md +++ b/docs/guides/applications/configuration-management/pulumi/deploy-in-code-with-pulumi/index.md @@ -33,7 +33,7 @@ In this guide you will learn how to: ## Before You Begin -1. If you haven't yet, [create a Linode API token](/docs/products/tools/api/guides/manage-api-tokens/#create-an-api-token). +1. If you haven't yet, [create a Linode API token](/docs/products/platform/accounts/guides/manage-api-tokens/#create-an-api-token). 1. [Create a free Pulumi Cloud account](https://app.pulumi.com/signup). diff --git a/docs/guides/applications/configuration-management/salt/configure-and-use-salt-cloud-and-cloud-maps-to-provision-systems/index.md b/docs/guides/applications/configuration-management/salt/configure-and-use-salt-cloud-and-cloud-maps-to-provision-systems/index.md index a5f58d5e13b..035a1a36060 100644 --- a/docs/guides/applications/configuration-management/salt/configure-and-use-salt-cloud-and-cloud-maps-to-provision-systems/index.md +++ b/docs/guides/applications/configuration-management/salt/configure-and-use-salt-cloud-and-cloud-maps-to-provision-systems/index.md @@ -33,7 +33,7 @@ This guide shows how to install Salt Cloud and configure it to work on a Linode. 2. This guide assumes that Salt Cloud will be installed together with Salt master server. -3. Generate an [API key](/docs/products/tools/api/guides/manage-api-tokens/) to access Linode API. This key will be used by Salt Cloud to manage your instances. Make sure to keep your API key safe. Set the environment variable `API_TOKEN` and test your API key is working through the REST interface: +3. Generate an [API key](/docs/products/platform/accounts/guides/manage-api-tokens/) to access Linode API. This key will be used by Salt Cloud to manage your instances. Make sure to keep your API key safe. Set the environment variable `API_TOKEN` and test your API key is working through the REST interface: curl -H "Authorization:Bearer $API_TOKEN" https://api.linode.com/v4/account | json_pp diff --git a/docs/guides/applications/configuration-management/terraform/create-a-multicloud-infrastructure-using-terraform/index.md b/docs/guides/applications/configuration-management/terraform/create-a-multicloud-infrastructure-using-terraform/index.md index db2af5d24f1..41cd4b2b808 100644 --- a/docs/guides/applications/configuration-management/terraform/create-a-multicloud-infrastructure-using-terraform/index.md +++ b/docs/guides/applications/configuration-management/terraform/create-a-multicloud-infrastructure-using-terraform/index.md @@ -73,7 +73,7 @@ In this section, you install Terraform on an Ubuntu 20.04 Linode. These steps ar To download Terraform on a Linode server, follow the steps below: -1. [Login to the Linode server via SSH](/docs/products/compute/compute-instances/guides/set-up-and-secure/#connect-to-the-instance). This is the Linode server where you want to install Terraform. Replace `192.0.2.0` with your [Linode's IP address](/docs/guides/find-your-linodes-ip-address/). +1. [Login to the Linode server via SSH](/docs/products/compute/compute-instances/guides/set-up-and-secure/#connect-to-the-instance). This is the Linode server where you want to install Terraform. Replace `192.0.2.0` with your [Linode's IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). ssh username@192.0.2.0 diff --git a/docs/guides/applications/configuration-management/terraform/how-to-deploy-secure-linodes-using-cloud-firewalls-and-terraform/index.md b/docs/guides/applications/configuration-management/terraform/how-to-deploy-secure-linodes-using-cloud-firewalls-and-terraform/index.md index 076d717320d..4e9df15ec84 100644 --- a/docs/guides/applications/configuration-management/terraform/how-to-deploy-secure-linodes-using-cloud-firewalls-and-terraform/index.md +++ b/docs/guides/applications/configuration-management/terraform/how-to-deploy-secure-linodes-using-cloud-firewalls-and-terraform/index.md @@ -25,7 +25,7 @@ In this guide, you will create a Linode Firewalls module which declares commonly 1. See [Create a Terraform Module](/docs/guides/create-terraform-module/) for a deeper dive into Terraform's standard module structure and other helpful details. -1. You need a Linode API personal access token to use with Terraform. This token will allow you to create, update, and destroy Linode resources. See the [Manage Personal Access Tokens](/docs/products/tools/api/guides/manage-api-tokens/) guide for steps to create a token. +1. You need a Linode API personal access token to use with Terraform. This token will allow you to create, update, and destroy Linode resources. See the [Manage Personal Access Tokens](/docs/products/platform/accounts/guides/manage-api-tokens/) guide for steps to create a token. {{< note respectIndent=false >}} When you create a personal access token ensure that you set **Read/Write** access permissions for Linode instances and Cloud Firewalls. diff --git a/docs/guides/applications/containers/using-nomad-for-orchestration/index.md b/docs/guides/applications/containers/using-nomad-for-orchestration/index.md index 766b1113e8b..35f96db833a 100644 --- a/docs/guides/applications/containers/using-nomad-for-orchestration/index.md +++ b/docs/guides/applications/containers/using-nomad-for-orchestration/index.md @@ -246,7 +246,7 @@ The configurations and commands used in this guide add multiple Linode instances 1. Open the `terraform.tfvars` file, and configure the variables there. Here is a breakdown of the variables and how to set them: - - `token` needs your Linode API token. Terraform uses this to provision Linode instances. Follow our [Get an API Access Token](/docs/products/tools/api/guides/manage-api-tokens/) guide to generate a personal access token. Be sure to give the token "Read/Write" permissions. + - `token` needs your Linode API token. Terraform uses this to provision Linode instances. Follow our [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/) guide to generate a personal access token. Be sure to give the token "Read/Write" permissions. - `ssh_keys` takes a list of SSH public keys. These keys are added to the known hosts on each node, allowing SSH access to the nodes. Enter the full public key for your local machine in one line. diff --git a/docs/guides/applications/project-management/install-farmos/index.md b/docs/guides/applications/project-management/install-farmos/index.md index 20485b983a2..54ad35171ef 100644 --- a/docs/guides/applications/project-management/install-farmos/index.md +++ b/docs/guides/applications/project-management/install-farmos/index.md @@ -105,7 +105,7 @@ Ensure that the version number matches the farmOS version you wish to download. ## Configure farmOS -1. Go to your Linode's domain or [IP address](/docs/guides/find-your-linodes-ip-address) in a web browser. This shows you the first step of the farmOS/Drupal web configuration. +1. Go to your Linode's domain or [IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) in a web browser. This shows you the first step of the farmOS/Drupal web configuration. 1. The first screen you encounter asks you to choose a profile and a language: diff --git a/docs/guides/applications/social-networking/create-an-aggregate-blog-using-planet-venus-on-ubuntu-12-04-precise-pangolin/index.md b/docs/guides/applications/social-networking/create-an-aggregate-blog-using-planet-venus-on-ubuntu-12-04-precise-pangolin/index.md index 4e90dfd263d..1f8db304860 100644 --- a/docs/guides/applications/social-networking/create-an-aggregate-blog-using-planet-venus-on-ubuntu-12-04-precise-pangolin/index.md +++ b/docs/guides/applications/social-networking/create-an-aggregate-blog-using-planet-venus-on-ubuntu-12-04-precise-pangolin/index.md @@ -36,7 +36,7 @@ Install the Planet and other required software by issuing the following command: apt-get install apache2 planet-venus -This will also install the Apache HTTP server if you have not already installed this software. Be sure to [configure a name-based virtual host](/docs/guides/how-to-install-a-lamp-stack-on-ubuntu-22-04/#apache) if you haven't already. You may now begin the configuration of Planet Venus. +This will also install the Apache HTTP server if you have not already installed this software. Be sure to [configure a name-based virtual host](/docs/guides/how-to-install-a-lamp-stack-on-ubuntu-22-04/#configuring-a-virtual-host-for-your-domain-on-apache) if you haven't already. You may now begin the configuration of Planet Venus. ## Configure Planet diff --git a/docs/guides/development/nodejs/nodejs-twitter-bot/index.md b/docs/guides/development/nodejs/nodejs-twitter-bot/index.md index d97004f7add..3feef7a0379 100644 --- a/docs/guides/development/nodejs/nodejs-twitter-bot/index.md +++ b/docs/guides/development/nodejs/nodejs-twitter-bot/index.md @@ -841,7 +841,7 @@ You could certainly let this code run for a long while from your local machine, ### Log In and Secure the Server -1. To log into the server, follow the [Connect to Your Linode via SSH](/docs/products/compute/compute-instances/guides/set-up-and-secure/#connect-to-the-instance) section of our [Getting Started](/docs/products/platform/get-started/) guide. If you do not have access to an SSH client, or if SSH connections are firewalled on your local network, you can also opt to use [the Lish console](/docs/products/compute/compute-instances/guides/lish/) from the Cloud Manager in your web browser. To do so, follow the [Use a Web Browser](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish) instructions in our Lish guide. +1. To log into the server, follow the [Connect to Your Linode via SSH](/docs/products/compute/compute-instances/guides/set-up-and-secure/#connect-to-the-instance) section of our [Getting Started](/docs/products/platform/get-started/) guide. If you do not have access to an SSH client, or if SSH connections are firewalled on your local network, you can also opt to use [the Lish console](/docs/products/compute/compute-instances/guides/lish/) from the Cloud Manager in your web browser. To do so, follow the [Use a Web Browser](/docs/products/compute/compute-instances/guides/lish/#through-cloud-manager-weblish) instructions in our Lish guide. {{< note respectIndent=false >}} Our [Connecting to a Remote Server Over SSH](/docs/guides/connect-to-server-over-ssh/) guide series has a few other options for SSH clients, like SSH extension for the Chrome web browser. @@ -899,7 +899,7 @@ The server is now ready to run the bot, but you still need to upload the bot's c | Field | Value | |-------|-------| - | Host | The IP Address for your Linode. Use the [Find your Linode's IP Address](/docs/guides/find-your-linodes-ip-address/) guide to locate your IP address in the Cloud Manager. | + | Host | The IP Address for your Linode. Use the [Find your Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) guide to locate your IP address in the Cloud Manager. | | Username | This should be the name for the limited non-root-user you created. | | Password | The password for the limited non-root-user you created. | | Port | This should be set to 22. | diff --git a/docs/guides/development/python/use-paramiko-python-to-ssh-into-a-server/index.md b/docs/guides/development/python/use-paramiko-python-to-ssh-into-a-server/index.md index a4ad7b9aa4b..b4d1ead17c9 100644 --- a/docs/guides/development/python/use-paramiko-python-to-ssh-into-a-server/index.md +++ b/docs/guides/development/python/use-paramiko-python-to-ssh-into-a-server/index.md @@ -37,7 +37,7 @@ If your system is [configured to use Anaconda](/docs/guides/how-to-install-anaco ## A Paramiko SSH Example: Connect to Your Server Using a Password -This section shows you how to authenticate to a remote server with a username and password. To begin, create a new file named `first_experiment.py` and add the contents of the example file. Ensure that you update the file with your own Linode's details. Replace the values for `YOUR_IP_ADDRESS`, `YOUR_LIMITED_USER_ACCOUNT`, and `YOUR_PASSWORD`. Use the [Find Your Linode's IP Address](/docs/guides/find-your-linodes-ip-address/) guide, if needed. +This section shows you how to authenticate to a remote server with a username and password. To begin, create a new file named `first_experiment.py` and add the contents of the example file. Ensure that you update the file with your own Linode's details. Replace the values for `YOUR_IP_ADDRESS`, `YOUR_LIMITED_USER_ACCOUNT`, and `YOUR_PASSWORD`. Use the [Find Your Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) guide, if needed. {{< file "password_login.py" >}} import paramiko diff --git a/docs/guides/development/version-control/install-apache-subversion-ubuntu/index.md b/docs/guides/development/version-control/install-apache-subversion-ubuntu/index.md index b7ce29ec538..de165a4f113 100644 --- a/docs/guides/development/version-control/install-apache-subversion-ubuntu/index.md +++ b/docs/guides/development/version-control/install-apache-subversion-ubuntu/index.md @@ -85,7 +85,7 @@ Root or sudo permissions must be available to install Apache Subversion. systemctl start apache2 -1. To verify that the installation was successful, open a browser window and enter the [Linode instance’s IP address](/docs/guides/find-your-linodes-ip-address/), `http://<>:80`. +1. To verify that the installation was successful, open a browser window and enter the [Linode instance’s IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/), `http://<>:80`. 1. If the instance is not accessible, the instance hosting Apache might require opening firewall ports. To enable `ufw` to let traffic flow between interfaces and the Apache daemon, you must instruct `ufw` to open ports for Apache. diff --git a/docs/guides/game-servers/deploy-7-days-to-die-linux-game-server/index.md b/docs/guides/game-servers/deploy-7-days-to-die-linux-game-server/index.md index e2f0587c0f2..1e1948050f8 100644 --- a/docs/guides/game-servers/deploy-7-days-to-die-linux-game-server/index.md +++ b/docs/guides/game-servers/deploy-7-days-to-die-linux-game-server/index.md @@ -42,7 +42,7 @@ The Linux Game Server manager ([LinuxGSM](https://linuxgsm.com/)) is a command-l sudo adduser sdtdserver sudo adduser sdtdserver sudo -1. Switch your terminal session to the new `sdtdserver` user. You can exit your current session by typing **exit**, then [SSH into your Linode](/docs/products/compute/compute-instances/guides/set-up-and-secure/#connect-to-the-instance) using as the `sdtdserver` user. Ensure you replace the example command with your [Linode's IP address](/docs/guides/find-your-linodes-ip-address/). +1. Switch your terminal session to the new `sdtdserver` user. You can exit your current session by typing **exit**, then [SSH into your Linode](/docs/products/compute/compute-instances/guides/set-up-and-secure/#connect-to-the-instance) using as the `sdtdserver` user. Ensure you replace the example command with your [Linode's IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). ssh sdtdserver@192.0.2.0 @@ -109,7 +109,7 @@ To start server type: Execute the `./sdtdserver` command to get a list of all available 7 Days to Die server commands. {{< /note >}} -1. On your computer, use Steam to fire up the game and connect to your [Linode server's IP address](/docs/guides/find-your-linodes-ip-address/). +1. On your computer, use Steam to fire up the game and connect to your [Linode server's IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). ![7dtd server status](Linux_game_server_7dtd_server.png) diff --git a/docs/guides/kubernetes/deploy-nginx-ingress-on-lke/index.md b/docs/guides/kubernetes/deploy-nginx-ingress-on-lke/index.md index 5d01504216f..00a09e36e97 100644 --- a/docs/guides/kubernetes/deploy-nginx-ingress-on-lke/index.md +++ b/docs/guides/kubernetes/deploy-nginx-ingress-on-lke/index.md @@ -50,7 +50,7 @@ This guide will show you how to: - [Cloud Manager LKE instructions](/docs/products/compute/kubernetes/) - [Linode API LKE instructions](/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/) - - [Terraform instructions](/docs/products/compute/kubernetes/guides/deploy-cluster-using-terraform/) + - [Terraform instructions](/docs/guides/deploy-lke-cluster-using-terraform/) You can also use an unmanaged Kubernetes cluster (that's not deployed through LKE). The instructions within this guide depend on the Linode Cloud Controller Manager (CCM), which is installed by default on LKE clusters but needs to be manually installed on unmanaged clusters. To learn how to install the Linode CCM on a cluster that was not deployed through LKE, see the [Installing the Linode CCM on an Unmanaged Kubernetes Cluster](/docs/guides/install-the-linode-ccm-on-unmanaged-kubernetes/) guide. diff --git a/docs/guides/kubernetes/deploy-volumes-with-the-linode-block-storage-csi-driver/index.md b/docs/guides/kubernetes/deploy-volumes-with-the-linode-block-storage-csi-driver/index.md index f5351039b09..f08a4b6aaec 100644 --- a/docs/guides/kubernetes/deploy-volumes-with-the-linode-block-storage-csi-driver/index.md +++ b/docs/guides/kubernetes/deploy-volumes-with-the-linode-block-storage-csi-driver/index.md @@ -33,7 +33,7 @@ This guide assumes you have a working Kubernetes cluster running on Linode. You - The [Linode Cloud Manager](/docs/products/compute/kubernetes/). - [Linode's API v4](/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/). - - [Terraform](/docs/products/compute/kubernetes/guides/deploy-cluster-using-terraform/), the popular infrastructure as code (IaC) tool. + - [Terraform](/docs/guides/deploy-lke-cluster-using-terraform/), the popular infrastructure as code (IaC) tool. 1. Deploy an [unmanaged Kubernetes cluster using Terraform](/docs/guides/how-to-provision-an-unmanaged-kubernetes-cluster-using-terraform/) and the [Kubernetes Terraform installer](https://registry.terraform.io/modules/linode/k8s/linode/0.1.2). diff --git a/docs/guides/kubernetes/how-to-configure-load-balancing-with-tls-encryption-on-a-kubernetes-cluster/index.md b/docs/guides/kubernetes/how-to-configure-load-balancing-with-tls-encryption-on-a-kubernetes-cluster/index.md index 035fbb7dfb6..4bdbbcf99eb 100644 --- a/docs/guides/kubernetes/how-to-configure-load-balancing-with-tls-encryption-on-a-kubernetes-cluster/index.md +++ b/docs/guides/kubernetes/how-to-configure-load-balancing-with-tls-encryption-on-a-kubernetes-cluster/index.md @@ -40,7 +40,7 @@ To learn about the various configurations available for Linode NodeBalancers via - [Cloud Manager LKE instructions](/docs/products/compute/kubernetes/) - [Linode API LKE instructions](/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/) - - [Terraform instructions](/docs/products/compute/kubernetes/guides/deploy-cluster-using-terraform/) + - [Terraform instructions](/docs/guides/deploy-lke-cluster-using-terraform/) You can also use an unmanaged Kubernetes cluster (that's not deployed through LKE). The instructions within this guide depend on the Linode Cloud Controller Manager (CCM), which is installed by default on LKE clusters but needs to be manually installed on unmanaged clusters. To learn how to install the Linode CCM on a cluster that was not deployed through LKE, see the [Installing the Linode CCM on an Unmanaged Kubernetes Cluster](/docs/guides/install-the-linode-ccm-on-unmanaged-kubernetes/) guide. diff --git a/docs/guides/networking/dns/dns-primary-and-secondary-server-setup/index.md b/docs/guides/networking/dns/dns-primary-and-secondary-server-setup/index.md index 64992b61ffb..2cbdba8c6ab 100644 --- a/docs/guides/networking/dns/dns-primary-and-secondary-server-setup/index.md +++ b/docs/guides/networking/dns/dns-primary-and-secondary-server-setup/index.md @@ -178,7 +178,7 @@ The new server can be in the same data center as the primary, but it doesn’t h sudo scp root@ns1.yourdomainhere.com:/etc/nsd/nsd.conf /etc/nsd ``` -1. Gather `ns2`'s external IPv4 and IPv6 addresses. Follow this guide to [Find Your Linode's IP Address](/docs/guides/find-your-linodes-ip-address) or use the following command: +1. Gather `ns2`'s external IPv4 and IPv6 addresses. Follow this guide to [Find Your Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) or use the following command: ```command {title="ns2"} ip a @@ -410,7 +410,7 @@ There is no requirement that the hidden primary reside in the same data center a sudo scp -r root@ns1.yourdomainhere.com:/etc/nsd/zones /etc/nsd ``` -1. Gather `ns3`'s external IPv4 and IPv6 addresses. Follow this guide to [Find Your Linode's IP Address](/docs/guides/find-your-linodes-ip-address) or use the following command: +1. Gather `ns3`'s external IPv4 and IPv6 addresses. Follow this guide to [Find Your Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) or use the following command: ```command {title="ns3"} ip a diff --git a/docs/guides/networking/dns/introduction-to-dns-on-linux/index.md b/docs/guides/networking/dns/introduction-to-dns-on-linux/index.md index f31ade0ec1a..bd33bc87d1d 100644 --- a/docs/guides/networking/dns/introduction-to-dns-on-linux/index.md +++ b/docs/guides/networking/dns/introduction-to-dns-on-linux/index.md @@ -154,7 +154,7 @@ As packaged for Ubuntu 22.04 LTS, NSD’s main configuration file (`nsd.conf`) p Since the NSD documentation already includes a fully annotated sample configuration file, copy that file and work from there. The sample file lists many options with plenty of comments, making it a useful learning tool. -1. First, gather your Linode's external IPv4 and IPv6 addresses. Follow this guide to [Find Your Linode's IP Address](/docs/guides/find-your-linodes-ip-address) or use the following command: +1. First, gather your Linode's external IPv4 and IPv6 addresses. Follow this guide to [Find Your Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) or use the following command: ```command ip a diff --git a/docs/guides/networking/vpn/set-up-wireguard-vpn-on-debian/index.md b/docs/guides/networking/vpn/set-up-wireguard-vpn-on-debian/index.md index 753d6eefedf..9748b45981b 100644 --- a/docs/guides/networking/vpn/set-up-wireguard-vpn-on-debian/index.md +++ b/docs/guides/networking/vpn/set-up-wireguard-vpn-on-debian/index.md @@ -58,7 +58,7 @@ Do not use WireGuard for critical applications. The project is still undergoing - Set your system's [hostname](/docs/products/compute/compute-instances/guides/set-up-and-secure/#configure-a-custom-hostname). {{< note >}} -The `GRUB 2` kernel is required for this guide. All distributions for all new Linodes now boot with the `GRUB 2` kernel by default. However, if you are running an older distribution, you will need to check to see which kernel you are running. You can use the [Update Kernel Guide](/docs/products/compute/compute-instances/guides/manage-the-kernel/) to check your kernel version and change it using the Cloud Manager. Select `GRUB 2` from the *Boot Settings: Select a Kernel* dropdown menu in Step 4 of [Update Your Linode Kernel with Linode's Cloud Manager](/docs/products/compute/compute-instances/guides/manage-the-kernel/#view-and-modify-the-kernel-in-the-cloud-manager). +The `GRUB 2` kernel is required for this guide. All distributions for all new Linodes now boot with the `GRUB 2` kernel by default. However, if you are running an older distribution, you will need to check to see which kernel you are running. You can use the [Update Kernel Guide](/docs/products/compute/compute-instances/guides/manage-the-kernel/) to check your kernel version and change it using the Cloud Manager. Select `GRUB 2` from the *Boot Settings: Select a Kernel* dropdown menu in Step 4 of [Update Your Linode Kernel with Linode's Cloud Manager](/docs/products/compute/compute-instances/guides/manage-the-kernel/#view-and-modify-the-kernel-in-cloud-manager). {{< /note >}} ## Install WireGuard diff --git a/docs/guides/networking/vpn/set-up-wireguard-vpn-on-ubuntu/index.md b/docs/guides/networking/vpn/set-up-wireguard-vpn-on-ubuntu/index.md index 5b309242cf8..b366a672ede 100644 --- a/docs/guides/networking/vpn/set-up-wireguard-vpn-on-ubuntu/index.md +++ b/docs/guides/networking/vpn/set-up-wireguard-vpn-on-ubuntu/index.md @@ -34,7 +34,7 @@ Do not use WireGuard for critical applications. The project is still undergoing - Set your system's [hostname](/docs/products/compute/compute-instances/guides/set-up-and-secure/#configure-a-custom-hostname). {{< note >}} -The `GRUB 2` kernel is required for this guide. All distributions for all new Linodes now boot with the `GRUB 2` kernel by default. However, if you are running an older distribution, you will need to check to see which kernel you are running. You can use the [Update Kernel Guide](/docs/products/compute/compute-instances/guides/manage-the-kernel/) to check your kernel version and change it using the Cloud Manager. Select `GRUB 2` from the *Boot Settings: Select a Kernel* dropdown menu in Step 4 of [Update Your Linode Kernel with Linode's Cloud Manager](/docs/products/compute/compute-instances/guides/manage-the-kernel/#view-and-modify-the-kernel-in-the-cloud-manager). +The `GRUB 2` kernel is required for this guide. All distributions for all new Linodes now boot with the `GRUB 2` kernel by default. However, if you are running an older distribution, you will need to check to see which kernel you are running. You can use the [Update Kernel Guide](/docs/products/compute/compute-instances/guides/manage-the-kernel/) to check your kernel version and change it using the Cloud Manager. Select `GRUB 2` from the *Boot Settings: Select a Kernel* dropdown menu in Step 4 of [Update Your Linode Kernel with Linode's Cloud Manager](/docs/products/compute/compute-instances/guides/manage-the-kernel/#view-and-modify-the-kernel-in-cloud-manager). {{< /note >}} ## Install WireGuard diff --git a/docs/guides/platform/migrate-to-linode/how-to-migrate-from-gcp-to-linode/index.md b/docs/guides/platform/migrate-to-linode/how-to-migrate-from-gcp-to-linode/index.md index 6ccecc5dc15..41a238a3b97 100644 --- a/docs/guides/platform/migrate-to-linode/how-to-migrate-from-gcp-to-linode/index.md +++ b/docs/guides/platform/migrate-to-linode/how-to-migrate-from-gcp-to-linode/index.md @@ -467,7 +467,7 @@ You disabled the Google services from calling out before creating and migrating ### Optional: Transfer Disk to ext4 -As stated above, to take advantage of features like resizing your disks in Cloud Manager and Backup Service, you'll need to move your new disk to an ext4 formatted disk. To do this, follow the procedures in the Make the System Compatible section of the [Install a Custom Distribution on a Linode guide](/docs/products/compute/compute-instances/guides/install-a-custom-distribution/#make-the-system-compatible-with-the-linode-platform). +As stated above, to take advantage of features like resizing your disks in Cloud Manager and Backup Service, you'll need to move your new disk to an ext4 formatted disk. To do this, follow the procedures in the Make the System Compatible section of the [Install a Custom Distribution on a Linode guide](/docs/guides/install-a-custom-distribution/#make-the-system-compatible-with-the-linode-platform). ### Cleaning Up diff --git a/docs/guides/platform/migrate-to-linode/migrating-a-server-to-your-linode/index.md b/docs/guides/platform/migrate-to-linode/migrating-a-server-to-your-linode/index.md index edc15c208b2..5da0533913e 100644 --- a/docs/guides/platform/migrate-to-linode/migrating-a-server-to-your-linode/index.md +++ b/docs/guides/platform/migrate-to-linode/migrating-a-server-to-your-linode/index.md @@ -14,7 +14,7 @@ deprecated: true deprecated_link: '/docs/guides/best-practices-when-migrating-to-linode/' --- {{< note >}} -The process for migrating a server image to your Linode will vary depending upon how the image was created. We recommend making an `.iso` file from your existing image, and then following the steps in our updated [custom distribution](/docs/products/compute/compute-instances/guides/install-a-custom-distribution/) guide to deploy it on a Linode. This guide is no longer being maintained, and the procedure outlined here is not recommended for new migrations. +The process for migrating a server image to your Linode will vary depending upon how the image was created. We recommend making an `.iso` file from your existing image, and then following the steps in our updated [custom distribution](/docs/guides/install-a-custom-distribution/) guide to deploy it on a Linode. This guide is no longer being maintained, and the procedure outlined here is not recommended for new migrations. {{< /note >}} You can migrate an existing server to your Linode from another hosting provider or a local machine. This is a great option if you're moving to Linode from another hosting provider or if you've built a custom server on your local machine. You can even migrate virtualized servers created with products like VirtualBox or VMware. This guide shows you how to prepare the Linode to receive the files, copy the files from the existing server to the Linode, and then make the disks bootable. diff --git a/docs/guides/security/monitoring/how-to-use-the-linode-api-with-twilio/index.md b/docs/guides/security/monitoring/how-to-use-the-linode-api-with-twilio/index.md index 04f490f3698..d23afaaadcb 100644 --- a/docs/guides/security/monitoring/how-to-use-the-linode-api-with-twilio/index.md +++ b/docs/guides/security/monitoring/how-to-use-the-linode-api-with-twilio/index.md @@ -98,7 +98,7 @@ Before you can work with the Linode API, you need a personal access token that i Your Linode account does not have any personal access tokens by default. To create a new token: -1. Follow our [Get an API Access Token](/docs/products/tools/api/guides/manage-api-tokens/) instructions. For the code example in this guide, you should create a token that has **Read Only** access to the **Account** resource. +1. Follow our [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/) instructions. For the code example in this guide, you should create a token that has **Read Only** access to the **Account** resource. 1. When you have created the token, it is displayed in your browser. Unlike the Twilio access token, you are not able to view the token in your browser after you have closed this page. Be sure to copy the token into a temporary text file or a password manager on your computer. Later in this guide, you add this token to the example code. diff --git a/docs/guides/security/selinux/a-beginners-guide-to-selinux-on-centos-7/index.md b/docs/guides/security/selinux/a-beginners-guide-to-selinux-on-centos-7/index.md index 84d2f33e623..d905a7edcfe 100644 --- a/docs/guides/security/selinux/a-beginners-guide-to-selinux-on-centos-7/index.md +++ b/docs/guides/security/selinux/a-beginners-guide-to-selinux-on-centos-7/index.md @@ -107,7 +107,7 @@ You can update the `SELINUX` directive with any of the available SELinux [states sudo reboot -- Connect to your Linode via SSH (replace `192.0.2.0` with your own [Linode's IP address](/docs/guides/find-your-linodes-ip-address/)) and verify your SELinux installation's status: +- Connect to your Linode via SSH (replace `192.0.2.0` with your own [Linode's IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/)) and verify your SELinux installation's status: ssh example_user@192.0.2.0 sudo sestatus diff --git a/docs/guides/security/selinux/a-beginners-guide-to-selinux-on-centos-8/index.md b/docs/guides/security/selinux/a-beginners-guide-to-selinux-on-centos-8/index.md index 5ffbd6c3250..d863b6d7ff4 100644 --- a/docs/guides/security/selinux/a-beginners-guide-to-selinux-on-centos-8/index.md +++ b/docs/guides/security/selinux/a-beginners-guide-to-selinux-on-centos-8/index.md @@ -105,7 +105,7 @@ You can update the `SELINUX` directive with any of the available SELinux [states sudo reboot -- Connect to your Linode via SSH (replace `192.0.2.0` with your own [Linode's IP address](/docs/guides/find-your-linodes-ip-address/)) and verify your SELinux installation's status: +- Connect to your Linode via SSH (replace `192.0.2.0` with your own [Linode's IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/)) and verify your SELinux installation's status: ssh example_user@192.0.2.0 sudo sestatus diff --git a/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-xen-linode/index.md b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-xen-linode/index.md index 3d50c51ab47..05c0afe57ae 100644 --- a/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-xen-linode/index.md +++ b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-xen-linode/index.md @@ -17,7 +17,7 @@ If you'd like to run a Linux distribution on your Linode that isn't available fr {{% content "all-linodes-kvm-shortguide" %}} {{< note >}} -This guide is intended for Linodes using our older Xen hypervisor. To install a custom distribution on a new KVM Linode, see [this guide](/docs/products/compute/compute-instances/guides/install-a-custom-distribution/). +This guide is intended for Linodes using our older Xen hypervisor. To install a custom distribution on a new KVM Linode, see [this guide](/docs/guides/install-a-custom-distribution/). {{< /note >}} ## Creating the Virtual Machine diff --git a/docs/guides/tools-reference/custom-kernels-distros/run-a-distributionsupplied-kernel-with-pvgrub/index.md b/docs/guides/tools-reference/custom-kernels-distros/run-a-distributionsupplied-kernel-with-pvgrub/index.md index e20385fdec1..1d6be8cd2b7 100644 --- a/docs/guides/tools-reference/custom-kernels-distros/run-a-distributionsupplied-kernel-with-pvgrub/index.md +++ b/docs/guides/tools-reference/custom-kernels-distros/run-a-distributionsupplied-kernel-with-pvgrub/index.md @@ -20,7 +20,7 @@ This guide is for legacy Xen Linodes. For newer Linodes, consult our [How to Cha PV-GRUB makes it possible to run your own kernel on your Linode, instead of using a host-supplied kernel. This is useful in cases where you'd like to enable specific kernel features, or you'd prefer to handle kernel upgrades directly. -If you'd like to run a custom distro on your Linode in combination with PV-GRUB, please follow our [Custom Distro](/docs/products/compute/compute-instances/guides/install-a-custom-distribution/) guide before taking these steps. +If you'd like to run a custom distro on your Linode in combination with PV-GRUB, please follow our [Custom Distro](/docs/guides/install-a-custom-distribution/) guide before taking these steps. Before you get started, make sure you follow the steps outlined in our [Getting Started](/docs/products/platform/get-started/) guide. Your Linode needs to be in a functional state. These steps should be performed as `root` on your Linode, via an SSH session. diff --git a/docs/guides/uptime/analytics/plausible/index.md b/docs/guides/uptime/analytics/plausible/index.md index ae008eea12d..2cd10902f36 100644 --- a/docs/guides/uptime/analytics/plausible/index.md +++ b/docs/guides/uptime/analytics/plausible/index.md @@ -15,7 +15,7 @@ license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' 1. If you have not already done so, create a Linode account and Compute Instance. See our [Getting Started with Linode](/docs/products/platform/get-started/). -1. You need to generate an [API Token](/docs/products/tools/api/guides/manage-api-tokens/). +1. You need to generate an [API Token](/docs/products/platform/accounts/guides/manage-api-tokens/). 1. [Deploy a Docker Marketplace App](/docs/products/tools/marketplace/guides/docker/). This includes creating your limited sudo user, your SSH public key, the previously generated API token, the domain you'd like to use and an email address, the preferred image, region, plan, and root password. There are additional options for opening ports to allow email, however this is only needed if you'll be allowing others to register for this Plausible instance. Once ready click on *Create Linode*. The process will take about 5-10 minutes to complete. diff --git a/docs/guides/uptime/monitoring/_index.md b/docs/guides/uptime/monitoring/_index.md index 5d209a5351b..e1f718b480a 100644 --- a/docs/guides/uptime/monitoring/_index.md +++ b/docs/guides/uptime/monitoring/_index.md @@ -1,6 +1,6 @@ --- title: Server Monitoring -description: "Whether you need to watch basic usage stats or need more advanced functionality, these guides will help you deploy open source server monitoring solutions on your Linux cloud server. The [Linode Longview](/docs/products/tools/longview/get-started/) tool also offers system metrics and graphing, which can be used in conjunction with any of these monitoring tools, or with the [Linode Manager email alerts](/docs/products/compute/compute-instances/guides/monitor-and-maintain/#configuring-linode-manager-email-alerts) to keep an eye on your system." +description: "Whether you need to watch basic usage stats or need more advanced functionality, these guides will help you deploy open source server monitoring solutions on your Linux cloud server. The [Linode Longview](/docs/products/tools/longview/get-started/) tool also offers system metrics and graphing, which can be used in conjunction with any of these monitoring tools, or with the [Linode Manager email alerts](/docs/products/compute/compute-instances/guides/monitor-and-maintain/#configure-cloud-manager-email-alerts) to keep an eye on your system." authors: ["Linode"] contributors: ["Linode"] published: 2009-07-16 diff --git a/docs/guides/uptime/monitoring/how-to-use-monitorix-for-system-monitoring/index.md b/docs/guides/uptime/monitoring/how-to-use-monitorix-for-system-monitoring/index.md index f87de0d2a25..af095867716 100644 --- a/docs/guides/uptime/monitoring/how-to-use-monitorix-for-system-monitoring/index.md +++ b/docs/guides/uptime/monitoring/how-to-use-monitorix-for-system-monitoring/index.md @@ -75,7 +75,7 @@ By default, Monitorix uses its built-in web server. However, it can be set to wo Monitorix is meant to be used as an interactive program. It's not suitable for use in shell programs. In this section, you access the Monitorix graphical user interface (GUI) to view some of the monitoring information provided by Monitorix. -1. To access the Monitorix interface running on your Linode, [find your Linode's IP address](/docs/guides/find-your-linodes-ip-address/). Open a browser window and navigate to the following URL, `http://192.0.2.0:8080/monitorix`. Replace `192.0.2.0` with your own IP address. +1. To access the Monitorix interface running on your Linode, [find your Linode's IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). Open a browser window and navigate to the following URL, `http://192.0.2.0:8080/monitorix`. Replace `192.0.2.0` with your own IP address. {{< note respectIndent=false >}} If you are running Monitorix on your computer, instead, navigate to `http://localhost:8080/monitorix`. diff --git a/docs/guides/web-servers/lamp/how-to-create-a-lamp-stack-application/index.md b/docs/guides/web-servers/lamp/how-to-create-a-lamp-stack-application/index.md index 7e250608920..48a57897843 100644 --- a/docs/guides/web-servers/lamp/how-to-create-a-lamp-stack-application/index.md +++ b/docs/guides/web-servers/lamp/how-to-create-a-lamp-stack-application/index.md @@ -78,7 +78,7 @@ sudo service mysql start Confirm that Apache is running with the following steps: -1. You need to [identify the IP address](/docs/guides/find-your-linodes-ip-address/) of the host and enter it in your web browser as a URL, such as `http://localhost` or `http://192.0.2.1` or a similar address. +1. You need to [identify the IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) of the host and enter it in your web browser as a URL, such as `http://localhost` or `http://192.0.2.1` or a similar address. 1. After visiting this URL, your web browser should display the default Apache2 page with the message "It works!" indicating that Apache is running correctly. diff --git a/docs/guides/web-servers/lemp/how-to-create-a-lemp-stack-application/index.md b/docs/guides/web-servers/lemp/how-to-create-a-lemp-stack-application/index.md index 9ce73bd4b6a..1d50be0bdbe 100644 --- a/docs/guides/web-servers/lemp/how-to-create-a-lemp-stack-application/index.md +++ b/docs/guides/web-servers/lemp/how-to-create-a-lemp-stack-application/index.md @@ -148,7 +148,7 @@ This demonstrates that PHP is installed and that the modules needed to communica ### Verify NGINX -Verification of NGINX service is a little more involved. The first step is [identification of the IP address](/docs/guides/find-your-linodes-ip-address/) of the host. +Verification of NGINX service is a little more involved. The first step is [identification of the IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) of the host. 1. Navigate a browser to a URL such as `http://localhost` or `http://23.77.NNN.NNN`, henceforth referred to as `$LEMP_HOST` diff --git a/docs/guides/websites/cms/strapi/using-strapi-cms/index.md b/docs/guides/websites/cms/strapi/using-strapi-cms/index.md index 6dcec2a32a9..13e4722fe43 100644 --- a/docs/guides/websites/cms/strapi/using-strapi-cms/index.md +++ b/docs/guides/websites/cms/strapi/using-strapi-cms/index.md @@ -60,7 +60,7 @@ This guide follows Strapi's Node.js setup process, Strapi's preferred installati Strapi runs as a Node.js project, which this guide sets up using the Node Package Manager (NPM). Once you run the Strapi project-setup script, you can start running your instance and create your administrator user. -1. Install the appropriate version of Node using NVM. Follow along with our [Installing and Using NVM](/docs/guides/how-to-install-use-node-version-manager-nvm/#installing-and-configuring-nvm) guide, and then use the following command to install Node: +1. Install the appropriate version of Node using NVM. Follow along with our [Installing and Using NVM](/docs/guides/how-to-install-use-node-version-manager-nvm/#install-nvm) guide, and then use the following command to install Node: ```command nvm install node diff --git a/docs/guides/websites/cms/wordpress/how-to-set-up-multiple-wordpress-sites-with-lxd-containers/index.md b/docs/guides/websites/cms/wordpress/how-to-set-up-multiple-wordpress-sites-with-lxd-containers/index.md index 6d143127e75..62b72c688eb 100644 --- a/docs/guides/websites/cms/wordpress/how-to-set-up-multiple-wordpress-sites-with-lxd-containers/index.md +++ b/docs/guides/websites/cms/wordpress/how-to-set-up-multiple-wordpress-sites-with-lxd-containers/index.md @@ -79,7 +79,7 @@ If the version is not 3.3 or later, or if your preferred distribution does not h 1. This guide requires you to own a domain name. This guide uses the hostnames `apache1.example.com` and `nginx1.example.com` for the two example WordPress websites. Throughout this guide, replace these names with subdomains under the domain that you own. Be sure to set up their DNS entries to point them to the IP address of your server. Specifically, create [A records](/docs/guides/dns-overview/#a-and-aaaa) for your subdomains. - If you're not familiar with DNS, review our [DNS Records: An Introduction](/docs/guides/dns-overview/) guide. After you have registered a domain name, you can choose to use Linode's [DNS Manager](https://www.linode.com/products/dns-manager/) to manage your DNS records. For help with this service, see our [DNS Manager guide](/docs/products/networking/dns-manager/). Your server's IP address can be found in the Cloud Manager; see our [Find Your Linode's IP Address](/docs/guides/find-your-linodes-ip-address/) guide for help. If you prefer to use a different DNS management service, follow their instructions for creating A records. + If you're not familiar with DNS, review our [DNS Records: An Introduction](/docs/guides/dns-overview/) guide. After you have registered a domain name, you can choose to use Linode's [DNS Manager](https://www.linode.com/products/dns-manager/) to manage your DNS records. For help with this service, see our [DNS Manager guide](/docs/products/networking/dns-manager/). Your server's IP address can be found in the Cloud Manager; see our [Find Your Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) guide for help. If you prefer to use a different DNS management service, follow their instructions for creating A records. 1. Complete the [Set Up a Reverse Proxy in an LXD Container to Host Multiple Websites](/docs/guides/beginners-guide-to-lxd-reverse-proxy/) guide. The guide instructs you to create a reverse proxy in a `proxy` container, and two web server containers, `apache1` and `nginx1`. These containers run the Apache 2 and NGINX web servers respectively. Then, the guide sets up Let's Encrypt TLS certificates for both websites. diff --git a/docs/guides/websites/erp/install-an-odoo-13-stack-on-debian-10/index.md b/docs/guides/websites/erp/install-an-odoo-13-stack-on-debian-10/index.md index dd24b9654be..b7e5b62d300 100644 --- a/docs/guides/websites/erp/install-an-odoo-13-stack-on-debian-10/index.md +++ b/docs/guides/websites/erp/install-an-odoo-13-stack-on-debian-10/index.md @@ -121,7 +121,7 @@ In order to simplify communication between Linodes, set hostnames for each serve | Odoo 13 | odoo | odoo.yourdomain.com | | PostgreSQL | postgresql | postgresql.yourdomain.com | -On each server, append the following lines to the `/etc/hosts` file. For the second line in each of these snippets, substitute your Linodes' IP addresses. If both servers are in the same Linode data center, then you can use private IP addresses for each Linode. Otherwise, use the public IP addresses of each Linode. Follow our [Find your Linode's IP Address](/docs/guides/find-your-linodes-ip-address/) guide to locate your addresses. +On each server, append the following lines to the `/etc/hosts` file. For the second line in each of these snippets, substitute your Linodes' IP addresses. If both servers are in the same Linode data center, then you can use private IP addresses for each Linode. Otherwise, use the public IP addresses of each Linode. Follow our [Find your Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) guide to locate your addresses. {{< note >}} A Linode does not come with a private IP address assigned to it by default. Private IPs are free to set up. If you would like to, follow our [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/#adding-an-ip-address) guide to set up a private IP address on each Linode. Please note that you need to add the new private address inside your Linodes' networking configuration after it is assigned to your server. diff --git a/docs/guides/websites/hosting/secure-website-lets-encrypt-acme-sh/index.md b/docs/guides/websites/hosting/secure-website-lets-encrypt-acme-sh/index.md index 89ead1d9485..36922b395eb 100644 --- a/docs/guides/websites/hosting/secure-website-lets-encrypt-acme-sh/index.md +++ b/docs/guides/websites/hosting/secure-website-lets-encrypt-acme-sh/index.md @@ -87,7 +87,7 @@ v2.8.7 ## Create an API token -acme.sh can use the [Linode v4 API](/docs/api) to create and remove temporary DNS records for a Domain. Follow the steps [Get An API Access Token](/docs/products/tools/api/guides/manage-api-tokens/) product documentation to create a Linode API v4 token. +acme.sh can use the [Linode v4 API](/docs/api) to create and remove temporary DNS records for a Domain. Follow the steps [Get An API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/) product documentation to create a Linode API v4 token. {{< note >}} Ensure the token you create has **Read/Write** access to **Domains**. diff --git a/docs/guides/websites/hosting/set-up-web-server-host-website/index.md b/docs/guides/websites/hosting/set-up-web-server-host-website/index.md index 16e504085d8..ed3ee1db096 100644 --- a/docs/guides/websites/hosting/set-up-web-server-host-website/index.md +++ b/docs/guides/websites/hosting/set-up-web-server-host-website/index.md @@ -162,7 +162,7 @@ The exact form fields will vary depending on the type of DNS record you select. 1. Enter a hostname in the **Hostname** field. -1. Enter the IP address of your server in the **IP Address** field. See [this quick answer page](/docs/guides/find-your-linodes-ip-address/) to find your Linode's IP address. +1. Enter the IP address of your server in the **IP Address** field. See [this quick answer page](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) to find your Linode's IP address. 1. Select a time interval from the **TTL** menu. *TTL* stands for *time to live*, and affects how long DNS records are cached by DNS resolvers. When the designated time to live is reached, the resolver must query the authoritative name servers for new records. diff --git a/docs/products/compute/compute-instances/get-started/index.md b/docs/products/compute/compute-instances/get-started/index.md index 6476aba52c5..4b2c7aca155 100644 --- a/docs/products/compute/compute-instances/get-started/index.md +++ b/docs/products/compute/compute-instances/get-started/index.md @@ -25,7 +25,7 @@ Consider deploying an app from the [Linode Marketplace](https://www.linode.com/m After the Compute Instance is finished provisioning and has fully booted up, you can connect to it through the built-in Lish Console in Cloud Manager (or via the SSH Lish Gateway) or SSH directly to your new system. -- **Weblish (via Cloud Manager):** Click the **Launch LISH Console** link at the top right corner of the Compute Instance's detail page. See [Using the Lish Console > Through a Browser](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish). +- **Weblish (via Cloud Manager):** Click the **Launch LISH Console** link at the top right corner of the Compute Instance's detail page. See [Using the Lish Console > Through a Browser](/docs/products/compute/compute-instances/guides/lish/#through-cloud-manager-weblish). - **SSH:** Copy the command from the *SSH Access* field that is available in Cloud Manager under the **Access** section on the Compute Instance's detail page. Paste the command into your local computer's terminal. The command should look similar to the following, only with the IP address of your newly created instance. diff --git a/docs/products/compute/compute-instances/guides/_index.md b/docs/products/compute/compute-instances/guides/_index.md index 0d0968f96b7..15df95b925f 100644 --- a/docs/products/compute/compute-instances/guides/_index.md +++ b/docs/products/compute/compute-instances/guides/_index.md @@ -32,7 +32,7 @@ aliases: ['/products/compute/shared-linodes/guides/','/products/compute/shared-c - [Choosing a Linux Distribution](/docs/products/compute/compute-instances/guides/distributions/) - [Packages Included on Linode Distribution Images](/docs/products/compute/compute-instances/guides/default-packages/) - [Linode Packages Mirrors for Various Distributions](/docs/products/compute/compute-instances/guides/package-mirrors/) -- [Install a Custom Linux Distribution](/docs/products/compute/compute-instances/guides/install-a-custom-distribution/) +- [Install a Custom Linux Distribution](/docs/guides/install-a-custom-distribution/) ## Disks and Configurations diff --git a/docs/products/compute/compute-instances/guides/disks-and-storage/index.md b/docs/products/compute/compute-instances/guides/disks-and-storage/index.md index f0ea4adca0a..bb1ff03fa5b 100644 --- a/docs/products/compute/compute-instances/guides/disks-and-storage/index.md +++ b/docs/products/compute/compute-instances/guides/disks-and-storage/index.md @@ -65,7 +65,7 @@ If you wish to deploy an Image to a new disk, see the [Deploy an Image to a Disk 1. Select from either the **Create Empty Disk** or **Create from Image** options. - **Empty disks:** An empty disk can store additional data, be used as a swap disk, or it can be used to manually [install a custom distribution](/docs/products/compute/compute-instances/guides/install-a-custom-distribution/). When creating an empty disk, select the desired *Filesystem*. In most cases, it's recommended to use the *ext4* filesystem. This ensures compatibility with our Backups service. If needed, *ext3* and *raw* disks are also available. If creating a swap disk, select the *swap* option. + **Empty disks:** An empty disk can store additional data, be used as a swap disk, or it can be used to manually [install a custom distribution](/docs/guides/install-a-custom-distribution/). When creating an empty disk, select the desired *Filesystem*. In most cases, it's recommended to use the *ext4* filesystem. This ensures compatibility with our Backups service. If needed, *ext3* and *raw* disks are also available. If creating a swap disk, select the *swap* option. **Images:** Selecting an Image lets you deploy a [Distribution Image](https://www.linode.com/distributions/), a [Custom Image](/docs/products/tools/images/), or a Recovery Image to the new disk. When creating a disk based on an Image, select the *Image*, *Root Password*, and optionally add *SSH Keys*. diff --git a/docs/products/compute/compute-instances/guides/distributions/index.md b/docs/products/compute/compute-instances/guides/distributions/index.md index b6758563a01..b9835b96382 100644 --- a/docs/products/compute/compute-instances/guides/distributions/index.md +++ b/docs/products/compute/compute-instances/guides/distributions/index.md @@ -33,5 +33,5 @@ Below is a full list of distributions. Once you've decided on a distribution, it | [Ubuntu](https://ubuntu.com/) | Arguably the most popular Linux distribution, widely regarded for it's ease of use. The LTS versions of Ubuntu are featured heavily in Linode's guides and across the community. | {{< note >}} -Though this list covers most popular distributions, creating a Linode using a distribution that we do not provide is possible. Feel free to follow our [Custom Distribution Guide](/docs/products/compute/compute-instances/guides/install-a-custom-distribution/) for more information. +Though this list covers most popular distributions, creating a Linode using a distribution that we do not provide is possible. Feel free to follow our [Custom Distribution Guide](/docs/guides/install-a-custom-distribution/) for more information. {{< /note >}} \ No newline at end of file diff --git a/docs/products/compute/compute-instances/guides/failover-bgp-frr/index.md b/docs/products/compute/compute-instances/guides/failover-bgp-frr/index.md index c6daa5ef1cd..91fa4f100d0 100644 --- a/docs/products/compute/compute-instances/guides/failover-bgp-frr/index.md +++ b/docs/products/compute/compute-instances/guides/failover-bgp-frr/index.md @@ -31,9 +31,9 @@ These instructions enable you to configure failover using FRR, which is very con To configure failover, complete each section in the order shown: -1. [Configuring Failover on a Compute Instance > Create and Share the Shared IP Address](/docs/products/compute/compute-instances/guides/failover/#create-and-share-the-shared-ip-address) +1. [Configuring Failover on a Compute Instance > Create and Share the Shared IP Address](/docs/products/compute/compute-instances/guides/failover/#1-create-and-share-the-shared-ip-address) 1. For *each* Compute Instance: - - [Configuring Failover on a Compute Instance > Add the Shared IP to the Networking Configuration](/docs/products/compute/compute-instances/guides/failover/#add-the-shared-ip-to-the-networking-configuration) + - [Configuring Failover on a Compute Instance > Add the Shared IP to the Networking Configuration](/docs/products/compute/compute-instances/guides/failover/#2-add-the-shared-ip-to-the-networking-configuration) - [Install FRR](#install-frr) - [Configure FRR](#configure-frr) 1. [Configuring Failover on a Compute Instance > Test Failover](/docs/products/compute/compute-instances/guides/failover/#test-failover) diff --git a/docs/products/compute/compute-instances/guides/manual-network-configuration/index.md b/docs/products/compute/compute-instances/guides/manual-network-configuration/index.md index c167746d32f..995a5cbe1e6 100644 --- a/docs/products/compute/compute-instances/guides/manual-network-configuration/index.md +++ b/docs/products/compute/compute-instances/guides/manual-network-configuration/index.md @@ -55,7 +55,7 @@ IP addresses can be statically configured or dynamically configured through DHCP - **VPC interfaces**: DHCP can be used to automatically configure the VPC IP address. {{< note >}} - If you do enable DHCP and are using a firewall (such as Cloud Firewalls), you must configure the firewall to allow communication with our DHCP servers. See the [DHCP IP Address Reference](/docs/guides/dhcp-ip-address-reference/) guide for a list of IP addresses to allow. + If you do enable DHCP and are using a firewall (such as Cloud Firewalls), you must configure the firewall to allow communication with our DHCP servers. See the [DHCP IP Address Reference](/docs/products/compute/compute-instances/guides/dhcp-ip-address-reference/) guide for a list of IP addresses to allow. {{< /note >}} {{< note >}} diff --git a/docs/products/compute/compute-instances/guides/metadata/index.md b/docs/products/compute/compute-instances/guides/metadata/index.md index c6d65f5bf88..d6935ca3e38 100644 --- a/docs/products/compute/compute-instances/guides/metadata/index.md +++ b/docs/products/compute/compute-instances/guides/metadata/index.md @@ -73,7 +73,7 @@ linode-cli linodes create \ Replace *[your-root-password]* with a strong root password and *[your-user-data]* with the cloud-config data or script you wish to use. When using the CLI, user data must be a Base64-encoded string. Review the [Base64 Encoded](#base64-encoded) section below to generate the string. {{< /tab >}} {{< tab "Linode API" >}} -Run the API curl request below, making sure to properly paste in or reference your [API token](/docs/products/tools/api/guides/manage-api-tokens/). +Run the API curl request below, making sure to properly paste in or reference your [API token](/docs/products/platform/accounts/guides/manage-api-tokens/). ```command curl -H "Content-Type: application/json" \ diff --git a/docs/products/compute/compute-instances/guides/migrate-to-different-dc/index.md b/docs/products/compute/compute-instances/guides/migrate-to-different-dc/index.md index 2c6dfb7d18f..70c02978ea8 100644 --- a/docs/products/compute/compute-instances/guides/migrate-to-different-dc/index.md +++ b/docs/products/compute/compute-instances/guides/migrate-to-different-dc/index.md @@ -20,7 +20,7 @@ Review the [Choosing a Data Center](/docs/products/platform/get-started/guides/c Various changes applied by the migration can impact your instance's configuration and the devices connected to it. They can all be seen in a caution message before proceeding with your migration within Cloud Manager. Here are some changes you should be aware of: -- **IP addresses are not transferrable** They aren't migrated to the new data center with your Compute Instance. Akamai issues a new IPv4 and IPv6 address for your instance, and you can access them once the migration completes. When your instance enters the migration queue, new IP addresses are reserved and you can see them in your instance's **Networking** detail page. See the [Find Your Linode's IP Address](/docs/guides/find-your-linodes-ip-address/) guide to learn how to access Networking information in Cloud Manager. +- **IP addresses are not transferrable** They aren't migrated to the new data center with your Compute Instance. Akamai issues a new IPv4 and IPv6 address for your instance, and you can access them once the migration completes. When your instance enters the migration queue, new IP addresses are reserved and you can see them in your instance's **Networking** detail page. See the [Find Your Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) guide to learn how to access Networking information in Cloud Manager. - **DNS records need to be updated**. You need to update DNS records with the new IP address once migrated. If you're hosting your DNS with us, this can be done through the [DNS Manager](/docs/products/networking/dns-manager/), while [rDNS](/docs/products/compute/compute-instances/guides/configure-rdns/) can be configured directly on each Compute Instance's Networking detail page. diff --git a/docs/products/compute/compute-instances/guides/placement-groups/index.md b/docs/products/compute/compute-instances/guides/placement-groups/index.md index 1b134aa0353..423aa2ee9c4 100644 --- a/docs/products/compute/compute-instances/guides/placement-groups/index.md +++ b/docs/products/compute/compute-instances/guides/placement-groups/index.md @@ -132,7 +132,7 @@ Here, we combine API operations to create a new placement group and add existing #### List regions -Run this API curl request, making sure to properly paste in or reference your [API token](/docs/products/tools/api/guides/manage-api-tokens/). Store the `id` and `label` values for the region where your target compute instances live. +Run this API curl request, making sure to properly paste in or reference your [API token](/docs/products/platform/accounts/guides/manage-api-tokens/). Store the `id` and `label` values for the region where your target compute instances live. ```command curl -H "Authorization: Bearer $TOKEN" \ https://api.linode.com/v4/regions diff --git a/docs/products/compute/compute-instances/guides/rescue-and-rebuild/index.md b/docs/products/compute/compute-instances/guides/rescue-and-rebuild/index.md index c7f0b8c8ccb..347c5b9d960 100644 --- a/docs/products/compute/compute-instances/guides/rescue-and-rebuild/index.md +++ b/docs/products/compute/compute-instances/guides/rescue-and-rebuild/index.md @@ -214,7 +214,7 @@ The software packages you install is available as long as the Compute Instance i ### Mounting Disks {{< note >}} -Before you mount the disk check the location of the root partition in the `/etc/fstab` file and update it accordingly. In the following example `/dev/sda` is the location of the disk. For more information, see the [Update your fstab](/docs/products/compute/compute-instances/guides/install-a-custom-distribution/#additional-system-configuration) guide. +Before you mount the disk check the location of the root partition in the `/etc/fstab` file and update it accordingly. In the following example `/dev/sda` is the location of the disk. For more information, see the [Update your fstab](/docs/guides/install-a-custom-distribution/#additional-system-configuration) guide. {{< /note >}} By default, your disks are not mounted when your Compute Instance boots into Rescue Mode. However, you can manually mount a disk under Rescue Mode to perform system recovery and maintenance tasks. diff --git a/docs/products/compute/compute-instances/guides/set-up-and-secure/index.md b/docs/products/compute/compute-instances/guides/set-up-and-secure/index.md index a6d53570d1a..bb2a2462ef5 100644 --- a/docs/products/compute/compute-instances/guides/set-up-and-secure/index.md +++ b/docs/products/compute/compute-instances/guides/set-up-and-secure/index.md @@ -44,7 +44,7 @@ Log in to [Cloud Manager](https://cloud.linode.com/), click the **Linodes** link Once the Compute Instance has been created and has finished booting up, you can connect to it. Connecting to your instance is usually done through the SSH (Secure Shell) protocol, though you can use the [Lish Console](/docs/products/compute/compute-instances/guides/lish/) to bypass SSH and connect directly to your instance. The Lish Console can be accessed through a web browser (Weblish) or via SSH on the command line. -- **Weblish (via Cloud Manager):** Click the **Launch LISH Console** link at the top right corner of the Compute Instance's detail page. See [Using the Lish Console > Through a Browser](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish). +- **Weblish (via Cloud Manager):** Click the **Launch LISH Console** link at the top right corner of the Compute Instance's detail page. See [Using the Lish Console > Through a Browser](/docs/products/compute/compute-instances/guides/lish/#through-cloud-manager-weblish). - **SSH:** Copy the command from the *SSH Access* field under the **Access** section on the Compute Instance's detail page (see screenshot above) and paste it into your local computer's terminal. The command should look similar to the following, only with the IP address of your newly created instance. diff --git a/docs/products/compute/compute-instances/guides/troubleshooting-connection-issues/index.md b/docs/products/compute/compute-instances/guides/troubleshooting-connection-issues/index.md index c4336a12364..ba0a4f963ad 100644 --- a/docs/products/compute/compute-instances/guides/troubleshooting-connection-issues/index.md +++ b/docs/products/compute/compute-instances/guides/troubleshooting-connection-issues/index.md @@ -31,7 +31,7 @@ There are a few core troubleshooting tools you should familiarize yourself with [*Lish*](/docs/products/compute/compute-instances/guides/lish/) is a shell that provides access to your Compute Instance's serial console. Lish does not establish a network connection to your Compute Instance, so you can use it when your networking is down or SSH is inaccessible. Much of your troubleshooting for basic connection issues will be performed from the Lish console. -To learn about Lish in more detail, and for instructions on how to connect to your Compute Instance via Lish, review the [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/) guide. In particular, [using your web browser](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish) is a fast and simple way to access Lish. +To learn about Lish in more detail, and for instructions on how to connect to your Compute Instance via Lish, review the [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/) guide. In particular, [using your web browser](/docs/products/compute/compute-instances/guides/lish/#through-cloud-manager-weblish) is a fast and simple way to access Lish. ### MTR diff --git a/docs/products/compute/compute-instances/guides/troubleshooting-firewall-issues/index.md b/docs/products/compute/compute-instances/guides/troubleshooting-firewall-issues/index.md index 6d186f087e6..6105a023062 100644 --- a/docs/products/compute/compute-instances/guides/troubleshooting-firewall-issues/index.md +++ b/docs/products/compute/compute-instances/guides/troubleshooting-firewall-issues/index.md @@ -19,7 +19,7 @@ While a firewall is often responsible for cases of limited access, these issues [*Lish*](/docs/products/compute/compute-instances/guides/lish/) is a shell that provides access to your Compute Instance's serial console and is a helpful tool for diagnosing and troubleshooting connection problems. Lish does not establish a network connection to your instance, so you can use it when your networking is down or your Compute Instance's Secure Shell (SSH) port is inaccessible. If you find yourself locked out of SSH, you can use Lish to perform much of the troubleshooting for basic connection issues. -To learn about Lish in more detail, and for instructions on how to connect to your Compute Instance via Lish, review the [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/) guide. A fast and simple way to access Lish is by [the your web browser option](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish). +To learn about Lish in more detail, and for instructions on how to connect to your Compute Instance via Lish, review the [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/) guide. A fast and simple way to access Lish is by [the your web browser option](/docs/products/compute/compute-instances/guides/lish/#through-cloud-manager-weblish). {{< note >}} When using Lish, you can log in to your Compute Instance with the `root` user, even if `root` user login is disabled by your system's SSH configuration file. diff --git a/docs/products/compute/compute-instances/guides/troubleshooting-ssh-issues/index.md b/docs/products/compute/compute-instances/guides/troubleshooting-ssh-issues/index.md index 195b9009cbc..ab50688fd4b 100644 --- a/docs/products/compute/compute-instances/guides/troubleshooting-ssh-issues/index.md +++ b/docs/products/compute/compute-instances/guides/troubleshooting-ssh-issues/index.md @@ -29,7 +29,7 @@ Before troubleshooting your SSH service, familiarize yourself with the Linode Sh [*Lish*](/docs/products/compute/compute-instances/guides/lish/) is a shell that provides access to your Compute Instance's serial console. Lish does not establish a network connection to your Compute Instance, so you can use it when your networking is down or SSH is inaccessible. While troubleshooting SSH, all commands you enter on your system will be performed from the Lish console. -To learn about Lish in more detail, and for instructions on how to connect to your Compute Instance via Lish, review the [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/) guide. In particular, [using your web browser](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish) is a fast and simple way to access Lish. +To learn about Lish in more detail, and for instructions on how to connect to your Compute Instance via Lish, review the [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/) guide. In particular, [using your web browser](/docs/products/compute/compute-instances/guides/lish/#through-cloud-manager-weblish) is a fast and simple way to access Lish. ### Forgotten your Password? diff --git a/docs/products/compute/kubernetes/developers/index.md b/docs/products/compute/kubernetes/developers/index.md index 298bfbf55ea..ab0dfa2ea7b 100644 --- a/docs/products/compute/kubernetes/developers/index.md +++ b/docs/products/compute/kubernetes/developers/index.md @@ -20,4 +20,4 @@ The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the L ## Third Party Tools & Integrations -**Terraform**: Terraform is an Infrastructure-as-code tool that includes management features for various types of Linode resources. Use Linode’s [official Terraform Provider](https://www.terraform.io/docs/providers/linode/r/volume.html) to [provision Linode Kubernetes Engine Clusters](/docs/products/compute/kubernetes/guides/deploy-cluster-using-terraform/). +**Terraform**: Terraform is an Infrastructure-as-code tool that includes management features for various types of Linode resources. Use Linode’s [official Terraform Provider](https://www.terraform.io/docs/providers/linode/r/volume.html) to [provision Linode Kubernetes Engine Clusters](/docs/guides/deploy-lke-cluster-using-terraform/). diff --git a/docs/products/compute/kubernetes/guides/_index.md b/docs/products/compute/kubernetes/guides/_index.md index a169386deda..4836161ec31 100644 --- a/docs/products/compute/kubernetes/guides/_index.md +++ b/docs/products/compute/kubernetes/guides/_index.md @@ -28,9 +28,9 @@ tab_group_main: - [Deploy and Manage a Kubernetes Cluster with the Linode API](/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/) -- [Deploy an LKE Cluster Using Pulumi](/docs/products/compute/kubernetes/guides/deploy-cluster-using-pulumi/) +- [Deploy an LKE Cluster Using Pulumi](/docs/guides/deploy-lke-cluster-using-pulumi/) -- [Deploy an LKE Cluster Using Terraform](/docs/products/compute/kubernetes/guides/deploy-cluster-using-terraform/) +- [Deploy an LKE Cluster Using Terraform](/docs/guides/deploy-lke-cluster-using-terraform/) - [Reset Kubeconfig](/docs/products/compute/kubernetes/guides/reset-kubeconfig/) diff --git a/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/index.md b/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/index.md index 8c0ae49616f..c763b887515 100644 --- a/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/index.md +++ b/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/index.md @@ -44,7 +44,7 @@ This guide covers how to use the Linode API to: 1. [Familiarize yourself with the Linode Kubernetes Engine service](https://www.linode.com/products/kubernetes/). This information helps you understand the benefits and limitations of LKE. -1. [Create an API Token](/docs/products/tools/api/guides/manage-api-tokens/#create-an-api-token). You need this to access the LKE service. +1. [Create an API Token](/docs/products/platform/accounts/guides/manage-api-tokens/#create-an-api-token). You need this to access the LKE service. 1. [Install kubectl](#install-kubectl) on your computer. You use kubectl to interact with your cluster once it's deployed. diff --git a/docs/products/compute/kubernetes/guides/load-balancing/index.md b/docs/products/compute/kubernetes/guides/load-balancing/index.md index 8fbe9efb8e9..3bde5eb233f 100644 --- a/docs/products/compute/kubernetes/guides/load-balancing/index.md +++ b/docs/products/compute/kubernetes/guides/load-balancing/index.md @@ -42,7 +42,7 @@ This guide assumes you have a working Kubernetes cluster that was deployed using - The [Linode Cloud Manager](/docs/products/compute/kubernetes/). - [Linode's API v4](/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/). -- [Terraform](/docs/products/compute/kubernetes/guides/deploy-cluster-using-terraform/), the popular infrastructure as code (IaC) tool. +- [Terraform](/docs/guides/deploy-lke-cluster-using-terraform/), the popular infrastructure as code (IaC) tool. {{< note >}} An LKE cluster will already have Linode's Cloud Controller Manager installed in the cluster's control plane. If you **did not** deploy your Kubernetes cluster using LKE and would like to make use of the Linode Cloud Controller Manager, see [Installing the Linode CCM on an Unmanaged Kubernetes Cluster - A Tutorial](/docs/guides/install-the-linode-ccm-on-unmanaged-kubernetes/). diff --git a/docs/products/compute/kubernetes/guides/secure-a-cluster-with-rbac/index.md b/docs/products/compute/kubernetes/guides/secure-a-cluster-with-rbac/index.md index 77856f564db..1015bdbdc90 100644 --- a/docs/products/compute/kubernetes/guides/secure-a-cluster-with-rbac/index.md +++ b/docs/products/compute/kubernetes/guides/secure-a-cluster-with-rbac/index.md @@ -26,7 +26,7 @@ This guide assumes you have a working Kubernetes cluster that was deployed using - The [Linode Cloud Manager](/docs/products/compute/kubernetes/). - [Linode's API v4](/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/). -- [Terraform](/docs/products/compute/kubernetes/guides/deploy-cluster-using-terraform/), the popular infrastructure as code (IaC) tool. +- [Terraform](/docs/guides/deploy-lke-cluster-using-terraform/), the popular infrastructure as code (IaC) tool. {{< note >}} An LKE cluster will already have Linode's Cloud Controller Manager installed in the cluster's control plane. If you **did not** deploy your Kubernetes cluster using LKE and would like to make use of the Linode Cloud Controller Manager, see [Installing the Linode CCM on an Unmanaged Kubernetes Cluster - A Tutorial](/docs/guides/install-the-linode-ccm-on-unmanaged-kubernetes/). diff --git a/docs/products/compute/kubernetes/guides/upgrade-kubernetes-version/index.md b/docs/products/compute/kubernetes/guides/upgrade-kubernetes-version/index.md index 4845102e304..7e2a43452e2 100644 --- a/docs/products/compute/kubernetes/guides/upgrade-kubernetes-version/index.md +++ b/docs/products/compute/kubernetes/guides/upgrade-kubernetes-version/index.md @@ -179,7 +179,7 @@ Once you are ready to perform an upgrade, you can start the upgrade process. Thi {{< /tab >}} {{< tab "Linode API" >}} -1. Identify the ID of the cluster you wish to upgrade. Run the API curl request below, making sure to properly paste in or reference your [API token](/docs/products/tools/api/guides/manage-api-tokens/). +1. Identify the ID of the cluster you wish to upgrade. Run the API curl request below, making sure to properly paste in or reference your [API token](/docs/products/platform/accounts/guides/manage-api-tokens/). ```command curl -H "Authorization: Bearer $TOKEN" \ diff --git a/docs/products/networking/cloud-firewall/guides/apply-to-service/index.md b/docs/products/networking/cloud-firewall/guides/apply-to-service/index.md index 1b75d61ca6b..61bc3532090 100644 --- a/docs/products/networking/cloud-firewall/guides/apply-to-service/index.md +++ b/docs/products/networking/cloud-firewall/guides/apply-to-service/index.md @@ -24,7 +24,7 @@ You can apply the Cloud Firewall to more than one Linode service at a time. Repe {{< /note >}} {{< note type="alert" >}} -If [Network Helper](/docs/products/compute/compute-instances/guides/network-helper/) has been disabled on your Compute Instance and the internal networking configuration uses DHCP for IPv4 address assignment, some additional firewall rules are necessary. You must edit the Cloud Firewall to allow DHCP traffic through port 67 and 68. If needed, a full list of IP addresses for our DHCP servers can be found in our [DHCP IP Address Reference Guide](/docs/guides/dhcp-ip-address-reference/). +If [Network Helper](/docs/products/compute/compute-instances/guides/network-helper/) has been disabled on your Compute Instance and the internal networking configuration uses DHCP for IPv4 address assignment, some additional firewall rules are necessary. You must edit the Cloud Firewall to allow DHCP traffic through port 67 and 68. If needed, a full list of IP addresses for our DHCP servers can be found in our [DHCP IP Address Reference Guide](/docs/products/compute/compute-instances/guides/dhcp-ip-address-reference/). {{< /note >}} ## Remove a Service diff --git a/docs/products/networking/dns-manager/guides/a-record/index.md b/docs/products/networking/dns-manager/guides/a-record/index.md index 61a5a610972..5c8e19bafbe 100644 --- a/docs/products/networking/dns-manager/guides/a-record/index.md +++ b/docs/products/networking/dns-manager/guides/a-record/index.md @@ -17,7 +17,7 @@ An **A** (*Address*) record matches a domain name to an IPv4 address, specifical - For the root domain (such as *example.com*), enter the `@` character or leave the field blank. - For a subdomain (such as *host.example.com*), enter a string that's 1-63 characters in length and contains only letters, numbers, and underscores. Hyphens can also be used, but the string cannot start with one. -- **IP Address:** The IPv4 or IPv6 address of the target server, such as a Linode Compute Instance. The Linode DNS Manager automatically creates either an A record or AAAA record depending on the type of IP address. See the [Find Your Linode's IP Address](/docs/guides/find-your-linodes-ip-address/) guide for help locating an IP address on your Linode Compute Instance. +- **IP Address:** The IPv4 or IPv6 address of the target server, such as a Linode Compute Instance. The Linode DNS Manager automatically creates either an A record or AAAA record depending on the type of IP address. See the [Find Your Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) guide for help locating an IP address on your Linode Compute Instance. - **TTL** (*Time To Live*): The length of time that DNS resolvers should store the DNS record *before* revalidating it with Linode's name servers. Setting the TTL to **5 minutes** is recommended for many use cases. If **Default** is selected, the TTL is set to **24 hours**. diff --git a/docs/products/networking/nodebalancers/guides/manage-nodebalancers-with-linode-api/index.md b/docs/products/networking/nodebalancers/guides/manage-nodebalancers-with-linode-api/index.md index 0c991fd3574..ba8c9359084 100644 --- a/docs/products/networking/nodebalancers/guides/manage-nodebalancers-with-linode-api/index.md +++ b/docs/products/networking/nodebalancers/guides/manage-nodebalancers-with-linode-api/index.md @@ -14,7 +14,7 @@ aliases: ['/platform/api/nodebalancers/','/guides/nodebalancers/','/products/too [NodeBalancers](https://www.linode.com/nodebalancers) can be used to provide high availability load balancing for almost any type of website or service hosted on a Compute Instance. This guide will demonstrate how to use the Linode API to create a NodeBalancer with two back end nodes. {{< note >}} -You need a Personal Access Token for the Linode API to complete the steps in this guide. See [Manage Personal Access Tokens](/docs/products/tools/api/guides/manage-api-tokens/#create-an-api-token) for more information. +You need a Personal Access Token for the Linode API to complete the steps in this guide. See [Manage Personal Access Tokens](/docs/products/platform/accounts/guides/manage-api-tokens/#create-an-api-token) for more information. {{< /note >}} ## Create a NodeBalancer diff --git a/docs/products/networking/vpc/guides/assign-services/index.md b/docs/products/networking/vpc/guides/assign-services/index.md index 26d5ae5e9ad..6bb057d4b0c 100644 --- a/docs/products/networking/vpc/guides/assign-services/index.md +++ b/docs/products/networking/vpc/guides/assign-services/index.md @@ -17,7 +17,7 @@ There are three main ways to assign a Compute Instance to a VPC: - VPCs, along with VLANs and the public internet, are configured as network interfaces within a Compute Instance's configuration profile. These network interfaces are configured automatically when creating a Compute Instance with a VPC or when interacting with the VPC directly to assign and remove existing Compute Instances. You can also edit the Configuration Profile directly to manually configure these network interfaces to suit specific use cases. Manually editing a Configuration Profile on a Compute Instance is typically the preferred way to assign a VPC to an existing instance. -- VPC resources requiring public internet access should be configured as a 1:1 NAT or use a [forward proxy](/docs/guides/forward-proxy-for-vpc/). It is not recommended to configure a separate network interface with public internet access (in addition to the VPC interface). +- VPC resources requiring public internet access should be configured as a 1:1 NAT or use a [forward proxy](/docs/products/networking/vpc/guides/forward-proxy-for-vpc/). It is not recommended to configure a separate network interface with public internet access (in addition to the VPC interface). - Compute Instances can only be assigned to a single subnet of a single VPC, though they can communicate with other instances on any subnet within the same VPC. Multiple VPC interfaces on an instance are not allowed. diff --git a/docs/products/networking/vpc/guides/create/index.md b/docs/products/networking/vpc/guides/create/index.md index 17913e65781..5e1a445fbfe 100644 --- a/docs/products/networking/vpc/guides/create/index.md +++ b/docs/products/networking/vpc/guides/create/index.md @@ -35,7 +35,7 @@ linode-cli vpcs create \ ``` {{< /tab >}} {{< tab "Linode API" >}} -Within your terminal, enter the API curl request below. Make sure to properly paste in or reference your [API token](/docs/products/tools/api/guides/manage-api-tokens/). For a complete API reference, see the [VPC API endpoints](/docs/api/vpcs/) documentation. **Before submitting the request, read through the rest of this document.** +Within your terminal, enter the API curl request below. Make sure to properly paste in or reference your [API token](/docs/products/platform/accounts/guides/manage-api-tokens/). For a complete API reference, see the [VPC API endpoints](/docs/api/vpcs/) documentation. **Before submitting the request, read through the rest of this document.** ```command curl https://api.linode.com/v4/vpcs \ diff --git a/docs/products/platform/get-started/_index.md b/docs/products/platform/get-started/_index.md index bfdaf9699dd..615cd4d93df 100644 --- a/docs/products/platform/get-started/_index.md +++ b/docs/products/platform/get-started/_index.md @@ -66,7 +66,7 @@ Linode's [Cloud Manager](https://cloud.linode.com/) is the primary gateway to ou - [Help & Support](https://cloud.linode.com/support): Search through our guides, find answers on the Community Site, or open a ticket to reach our 24/7 award-winning [Support Team](https://www.linode.com/support-experience/). -For a full overview of Cloud Manager and its core features, see the [Overview of Cloud Manager](/docs/products/tools/cloud-manager/guides/an-overview-of-the-cloud-manager/) guide. +For a full overview of Cloud Manager and its core features, see the [Overview of Cloud Manager](/docs/products/tools/cloud-manager/guides/overview-of-cloud-manager/) guide. ## Create Your First Compute Instance diff --git a/docs/products/storage/block-storage/guides/manage-block-storage-with-linode-api/index.md b/docs/products/storage/block-storage/guides/manage-block-storage-with-linode-api/index.md index 445cbbd6568..b5bb1fb577b 100644 --- a/docs/products/storage/block-storage/guides/manage-block-storage-with-linode-api/index.md +++ b/docs/products/storage/block-storage/guides/manage-block-storage-with-linode-api/index.md @@ -15,7 +15,7 @@ The Linode API lets you create, delete, attach, detach, clone, and resize Block ## Before You Begin -You need a Personal Access Token for the Linode API to complete the steps in this guide. See [Manage Personal Access Tokens](/docs/products/tools/api/guides/manage-api-tokens/#create-an-api-token) for more information. +You need a Personal Access Token for the Linode API to complete the steps in this guide. See [Manage Personal Access Tokens](/docs/products/platform/accounts/guides/manage-api-tokens/#create-an-api-token) for more information. Store the token as a temporary shell variable to simplify repeated requests. Replace `` in this example with your token: diff --git a/docs/products/tools/api/get-started/index.md b/docs/products/tools/api/get-started/index.md index 14c1f98f91a..e15bc45aa6f 100644 --- a/docs/products/tools/api/get-started/index.md +++ b/docs/products/tools/api/get-started/index.md @@ -38,7 +38,7 @@ Authorization for the Linode API is handled through personal access tokens. Pers If you are building an application which needs to authenticate multiple users (for example, a custom interface to Linode's infrastructure for your organization), you can set up an [OAuth authentication flow](/docs/api/#oauth) to generate tokens for each user. {{< /note >}} -For full instructions on creating and managing personal access tokens, see [Manage Personal Access Tokens](/docs/products/tools/api/guides/manage-api-tokens/#create-an-api-token). +For full instructions on creating and managing personal access tokens, see [Manage Personal Access Tokens](/docs/products/platform/accounts/guides/manage-api-tokens/#create-an-api-token). 1. Log in to Cloud Manager. diff --git a/docs/products/tools/api/guides/_index.md b/docs/products/tools/api/guides/_index.md index 42a8c7f4c6b..382942e8cdf 100644 --- a/docs/products/tools/api/guides/_index.md +++ b/docs/products/tools/api/guides/_index.md @@ -11,7 +11,7 @@ aliases: ['/products/tools/linode-api/guides/'] ## Basics -- [Manage API Tokens](/docs/products/tools/api/guides/manage-api-tokens/): View and manage personal access tokens +- [Manage API Tokens](/docs/products/platform/accounts/guides/manage-api-tokens/): View and manage personal access tokens - [Send an API Request with cURL](/docs/products/tools/api/guides/curl/): Learn how to use cURL to quickly send an API call diff --git a/docs/products/tools/cli/guides/cli-v3/index.md b/docs/products/tools/cli/guides/cli-v3/index.md index 31793e6a27c..01b5315f131 100644 --- a/docs/products/tools/cli/guides/cli-v3/index.md +++ b/docs/products/tools/cli/guides/cli-v3/index.md @@ -6,7 +6,7 @@ modified: 2022-11-30 image: linode-cli.png external_resources: - '[Github Linode CLI](https://github.com/linode/cli)' - - '[Linode API Key](/docs/products/tools/api/guides/manage-api-tokens/)' + - '[Linode API Key](/docs/products/platform/accounts/guides/manage-api-tokens/)' keywords: ["linode cli", " command line interface", " man pages", " api key"] tags: ["linode platform"] aliases: ['/platform/api/using-the-linode-cli-api-v3/','/guides/using-the-linode-cli-api-v3/'] @@ -16,7 +16,7 @@ deprecated_link: 'platform/api/linode-cli/' The Linode Command Line Interface (**CLI**) is an [open-source](https://github.com/linode/cli) command line tool for managing your Linode services. You can reboot your Linode, update an MX record for your domain, manage your NodeBalancers, create a StackScript and more from the command line on any computer, without logging in to the [Linode Manager](https://manager.linode.com/) graphical user interface. -Your Linode [API key](/docs/products/tools/api/guides/manage-api-tokens/) is required for the CLI to function. +Your Linode [API key](/docs/products/platform/accounts/guides/manage-api-tokens/) is required for the CLI to function. ## Install the CLI @@ -217,7 +217,7 @@ If you don't run the configuration tool, you can add these options manually in t ### API Key -The Linode CLI requires your API key to function. If you need to generate an API key manually, read the [API Key](/docs/products/tools/api/guides/manage-api-tokens/) article. There are three ways to provide the key to the CLI. The configuration tool generates a new key and adds it to the `.linodecli/config` file automatically. +The Linode CLI requires your API key to function. If you need to generate an API key manually, read the [API Key](/docs/products/platform/accounts/guides/manage-api-tokens/) article. There are three ways to provide the key to the CLI. The configuration tool generates a new key and adds it to the `.linodecli/config` file automatically. - In the `.linodecli/config` file: diff --git a/docs/products/tools/cli/guides/install/index.md b/docs/products/tools/cli/guides/install/index.md index 2fabd1d2326..e10009320ee 100644 --- a/docs/products/tools/cli/guides/install/index.md +++ b/docs/products/tools/cli/guides/install/index.md @@ -56,7 +56,7 @@ The first time you interact with the Linode CLI, you need to complete the initia linode-cli configure ``` - - **Manually create a personal access token:** Prompts you for a token that you need to manually create. See [Linode API Keys and Tokens](/docs/products/tools/api/guides/manage-api-tokens/). + - **Manually create a personal access token:** Prompts you for a token that you need to manually create. See [Linode API Keys and Tokens](/docs/products/platform/accounts/guides/manage-api-tokens/). ```command linode-cli configure --token @@ -66,7 +66,7 @@ The first time you interact with the Linode CLI, you need to complete the initia ### Non-interactive Configuration -To configure the CLI without any interactive prompts, you can set the token through the following environment variable, replacing *[token]* with the token you've manually generated. See [Linode API Keys and Tokens](/docs/products/tools/api/guides/manage-api-tokens/). +To configure the CLI without any interactive prompts, you can set the token through the following environment variable, replacing *[token]* with the token you've manually generated. See [Linode API Keys and Tokens](/docs/products/platform/accounts/guides/manage-api-tokens/). ```command export LINODE_CLI_TOKEN="[token]" diff --git a/docs/products/tools/images/guides/_index.md b/docs/products/tools/images/guides/_index.md index 66003f22dd9..013a0b50ea4 100644 --- a/docs/products/tools/images/guides/_index.md +++ b/docs/products/tools/images/guides/_index.md @@ -36,7 +36,7 @@ tab_group_main: ### Custom Distributions -- [Install a Custom Distribution on a Linode](/docs/products/compute/compute-instances/guides/install-a-custom-distribution/) +- [Install a Custom Distribution on a Linode](/docs/guides/install-a-custom-distribution/) ### Migration diff --git a/docs/products/tools/images/guides/deploy-image-to-existing-linode/index.md b/docs/products/tools/images/guides/deploy-image-to-existing-linode/index.md index c9580f46eb3..54055e9596a 100644 --- a/docs/products/tools/images/guides/deploy-image-to-existing-linode/index.md +++ b/docs/products/tools/images/guides/deploy-image-to-existing-linode/index.md @@ -60,7 +60,7 @@ If you instead wish to retain the data on your Compute Instance, you can add a d | /dev/sda | Choose the disk for the new Image that was just deployed. | | /dev/sdb | Choose the swap disk, if one is available. | - For all of Linode's standard distribution images, the other fields can retain their default values. For Custom Images, you may need to update other parts of the configuration profile. Review the [Managing Configuration Profiles on a Linode](/docs/products/compute/compute-instances/guides/configuration-profiles//#editing-a-configuration-profile) and [Install a Custom Distribution on a Linode](/docs/products/compute/compute-instances/guides/install-a-custom-distribution/) guides for further guidance. + For all of Linode's standard distribution images, the other fields can retain their default values. For Custom Images, you may need to update other parts of the configuration profile. Review the [Managing Configuration Profiles on a Linode](/docs/products/compute/compute-instances/guides/configuration-profiles//#editing-a-configuration-profile) and [Install a Custom Distribution on a Linode](/docs/guides/install-a-custom-distribution/) guides for further guidance. 1. Reboot the Compute Instance using the new Image. Navigate to the **Configuration** tab, find the new configuration profile in the list, and click the corresponding **Boot** link. This link may be displayed with the **More Options** ellipsis dropdown menu. diff --git a/docs/products/tools/marketplace/_shortguides/marketplace-custom-domain-fields-shortguide/index.md b/docs/products/tools/marketplace/_shortguides/marketplace-custom-domain-fields-shortguide/index.md index dccc8105c5c..ea129765253 100644 --- a/docs/products/tools/marketplace/_shortguides/marketplace-custom-domain-fields-shortguide/index.md +++ b/docs/products/tools/marketplace/_shortguides/marketplace-custom-domain-fields-shortguide/index.md @@ -9,6 +9,6 @@ show_on_rss_feed: false If you wish to automatically configure a custom domain, you first need to configure your domain to use Linode's name servers. This is typically accomplished directly through your registrar. See [Use Linode’s Name Servers with Your Domain](/docs/products/networking/dns-manager/guides/authoritative-name-servers/). Once that is finished, you can fill out the following fields for the Marketplace App: -- **Linode API Token:** If you wish to use the Linode's [DNS Manager](/docs/products/networking/dns-manager/) to manage DNS records for your custom domain, create a Linode API *Personal Access Token* on your account with Read/Write access to *Domains*. If this is provided along with the subdomain and domain fields (outlined below), the installation attempts to create DNS records via the Linode API. See [Get an API Access Token](/docs/products/tools/api/guides/manage-api-tokens/). If you do not provide this field, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance. +- **Linode API Token:** If you wish to use the Linode's [DNS Manager](/docs/products/networking/dns-manager/) to manage DNS records for your custom domain, create a Linode API *Personal Access Token* on your account with Read/Write access to *Domains*. If this is provided along with the subdomain and domain fields (outlined below), the installation attempts to create DNS records via the Linode API. See [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/). If you do not provide this field, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance. - **Subdomain:** The subdomain you wish to use, such as *www* for `www.example.com`. - **Domain:** The domain name you wish to use, such as *example.com*. \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/apache-kafka-cluster/index.md b/docs/products/tools/marketplace/guides/apache-kafka-cluster/index.md index 7fb73278607..597e4d7a9d1 100644 --- a/docs/products/tools/marketplace/guides/apache-kafka-cluster/index.md +++ b/docs/products/tools/marketplace/guides/apache-kafka-cluster/index.md @@ -41,7 +41,7 @@ Our marketplace application allows the deployment of a Kafka cluster using Kafka ### Kafka Options -- **[Linode API Token](/docs/products/tools/api/guides/manage-api-tokens/#create-an-api-token):** The provisioner node uses an authenticated API token to create the additional components to the cluster. This is required to fully create the Kafka cluster. +- **[Linode API Token](/docs/products/platform/accounts/guides/manage-api-tokens/#create-an-api-token):** The provisioner node uses an authenticated API token to create the additional components to the cluster. This is required to fully create the Kafka cluster. {{% content "marketplace-required-limited-user-fields-shortguide" %}} diff --git a/docs/products/tools/marketplace/guides/chevereto/index.md b/docs/products/tools/marketplace/guides/chevereto/index.md index ba72f4af4cc..1dcdbe4983d 100644 --- a/docs/products/tools/marketplace/guides/chevereto/index.md +++ b/docs/products/tools/marketplace/guides/chevereto/index.md @@ -36,7 +36,7 @@ Chevereto requires a valid license to use the software. To purchase a license, v ### Access your Chevereto App -1. After Chevereto has finished installing, log in to your Linode via SSH, replacing `192.0.2.0` with your [Linode's IP address](/docs/guides/find-your-linodes-ip-address/), and entering your Linode's root password when prompted: +1. After Chevereto has finished installing, log in to your Linode via SSH, replacing `192.0.2.0` with your [Linode's IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/), and entering your Linode's root password when prompted: ssh root@192.0.2.0 diff --git a/docs/products/tools/marketplace/guides/cyberpanel/index.md b/docs/products/tools/marketplace/guides/cyberpanel/index.md index 46ea0c00806..9a70cf53582 100644 --- a/docs/products/tools/marketplace/guides/cyberpanel/index.md +++ b/docs/products/tools/marketplace/guides/cyberpanel/index.md @@ -34,7 +34,7 @@ aliases: ['/guides/deploy-cyberpanel-with-marketplace-apps/','/guides/cyberpanel ### Access your CyberPanel App -1. When the installation completes, log in to your Linode via SSH, replacing `192.0.2.1` with your [Linode's IP address](/docs/guides/find-your-linodes-ip-address/), and entering your Linode's root password when prompted: +1. When the installation completes, log in to your Linode via SSH, replacing `192.0.2.1` with your [Linode's IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/), and entering your Linode's root password when prompted: ```command ssh root@192.0.2.1 diff --git a/docs/products/tools/marketplace/guides/discourse/index.md b/docs/products/tools/marketplace/guides/discourse/index.md index 3d628b9bf94..21244bf8e2d 100644 --- a/docs/products/tools/marketplace/guides/discourse/index.md +++ b/docs/products/tools/marketplace/guides/discourse/index.md @@ -56,7 +56,7 @@ Discourse requires that you have a domain name and access to a personal SMTP ema Discourse requires that you have a domain name and SMTP email. These fields are required for a successful installation and are marked *Required*. Additionally, the SMTP user must be able to send email from `noreply@your-fully-qualified-domain.com` for account verification. -- **Linode API Token:** If you wish to use the Linode's [DNS Manager](/docs/products/networking/dns-manager/) to manage DNS records for your custom domain, create a Linode API *Personal Access Token* on your account with Read/Write access to *Domains*. If this is provided along with the subdomain and domain fields (outlined below), the installation attempts to create DNS records via the Linode API. See [Get an API Access Token](/docs/products/tools/api/guides/manage-api-tokens/). If you do not provide this field, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance. +- **Linode API Token:** If you wish to use the Linode's [DNS Manager](/docs/products/networking/dns-manager/) to manage DNS records for your custom domain, create a Linode API *Personal Access Token* on your account with Read/Write access to *Domains*. If this is provided along with the subdomain and domain fields (outlined below), the installation attempts to create DNS records via the Linode API. See [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/). If you do not provide this field, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance. - **Subdomain:** The subdomain you wish to use, such as *www* for `www.example.com`. - **Domain:** The domain name you wish to use, such as *example.com*. diff --git a/docs/products/tools/marketplace/guides/flask/index.md b/docs/products/tools/marketplace/guides/flask/index.md index 24518a82b94..df46e891a50 100644 --- a/docs/products/tools/marketplace/guides/flask/index.md +++ b/docs/products/tools/marketplace/guides/flask/index.md @@ -36,7 +36,7 @@ aliases: ['/platform/marketplace/how-to-deploy-flask-with-marketplace-apps/', '/ In addition to installing Flask, this Marketplace app installs and configures software to support running Flask in a production environment. Below is a list of the installed software: - The [NGINX](/docs/guides/getting-started-with-nginx-part-1-installation-and-basic-setup/) web server is installed with a basic NGINX configuration, located in `/etc/nginx/sites-enabled/flask_app`, and listening on your Linode's IP address. -- An example Flask application is downloaded to your Linode's `/home/flask_app_project` directory. If you visit your [Linode's IP address](/docs/guides/find-your-linodes-ip-address/), you will see the example Flask application running and serving boiler plate blog content. +- An example Flask application is downloaded to your Linode's `/home/flask_app_project` directory. If you visit your [Linode's IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/), you will see the example Flask application running and serving boiler plate blog content. - Your example Flask application's environment will be configured with basic settings located in the `/etc/config.json` file. - [Gunicorn](https://gunicorn.org/), a Python WSGI (web server gateway interface) HTTP Server for UNIX, is installed and running. It is used to forward requests from your NGINX web server to your Flask application. - [Supervisor](http://supervisord.org/), a client/server system that allows its users to monitor and control a number of processes on UNIX-like operating systems, is installed and running on your Linode. Its configuration file can be found in the following location, `/etc/supervisor/conf.d/flask_app.conf`. diff --git a/docs/products/tools/marketplace/guides/galera-cluster/index.md b/docs/products/tools/marketplace/guides/galera-cluster/index.md index 1e53cbfd7d0..8ce8104f166 100644 --- a/docs/products/tools/marketplace/guides/galera-cluster/index.md +++ b/docs/products/tools/marketplace/guides/galera-cluster/index.md @@ -36,7 +36,7 @@ This Marketplace App deploys 3 Compute Instances to create a highly available an - **Cluster Name** *(required)*: Enter the name you wish to use for this cluster deployment. -- **Linode API Token** *(required)*: Your API token is used to deploy additional Compute Instances as part of this cluster. At a minimum, this token must have Read/Write access to *Linodes*. If you do not yet have an API token, see [Get an API Access Token](/docs/products/tools/api/guides/manage-api-tokens/) to create one. +- **Linode API Token** *(required)*: Your API token is used to deploy additional Compute Instances as part of this cluster. At a minimum, this token must have Read/Write access to *Linodes*. If you do not yet have an API token, see [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/) to create one. - **Add SSH Keys to all nodes** *(required)*: If you select *yes*, any SSH Keys that are added to the root user account (in the **SSH Keys** section), are also added to your limited user account on all deployed Compute Instances. diff --git a/docs/products/tools/marketplace/guides/gitea/index.md b/docs/products/tools/marketplace/guides/gitea/index.md index a0a46a20fb3..7913a44511c 100644 --- a/docs/products/tools/marketplace/guides/gitea/index.md +++ b/docs/products/tools/marketplace/guides/gitea/index.md @@ -59,7 +59,7 @@ Self-hosting your software development with the Gitea Marketplace App offers tot After Gitea has finished installing, you can access your Gitea site using a web browser to complete setup and begin using your app. -1. Enter your Linode's fully qualified domain name (for example, `https://www.example.com`) or [IPv4 address](/docs/guides/find-your-linodes-ip-address/) (for example, `http://192.0.2.0`) into a browser window to access the Gitea welcome page. Select the **Register** link to reach the initial configuration screen. +1. Enter your Linode's fully qualified domain name (for example, `https://www.example.com`) or [IPv4 address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) (for example, `http://192.0.2.0`) into a browser window to access the Gitea welcome page. Select the **Register** link to reach the initial configuration screen. ![The Gitea welcome page.](gitea-welcome-page.png 'Gitea welcome page') diff --git a/docs/products/tools/marketplace/guides/glusterfs-cluster/index.md b/docs/products/tools/marketplace/guides/glusterfs-cluster/index.md index 1bb450c08fd..6fa10e84642 100644 --- a/docs/products/tools/marketplace/guides/glusterfs-cluster/index.md +++ b/docs/products/tools/marketplace/guides/glusterfs-cluster/index.md @@ -32,7 +32,7 @@ external_resources: ### GlusterFS Options -- **[Linode API Token](/docs/products/tools/api/guides/manage-api-tokens/#create-an-api-token):** The provisioner node will use an authenticated API token to create the additional components to the cluster. This is required to fully create the GlusterFS cluster. +- **[Linode API Token](/docs/products/platform/accounts/guides/manage-api-tokens/#create-an-api-token):** The provisioner node will use an authenticated API token to create the additional components to the cluster. This is required to fully create the GlusterFS cluster. {{% content "marketplace-required-limited-user-fields-shortguide" %}} diff --git a/docs/products/tools/marketplace/guides/hashicorp-nomad-clients-cluster/index.md b/docs/products/tools/marketplace/guides/hashicorp-nomad-clients-cluster/index.md index 63722e86e1c..09a2698d042 100644 --- a/docs/products/tools/marketplace/guides/hashicorp-nomad-clients-cluster/index.md +++ b/docs/products/tools/marketplace/guides/hashicorp-nomad-clients-cluster/index.md @@ -35,7 +35,7 @@ Please be aware that each Compute Instance will appear on your invoice as a sepa ### Nomad Client Options -- **Linode API Token** *(required)*: Your API token is used to deploy additional Compute Instances as part of this cluster. At a minimum, this token must have Read/Write access to *Linodes*. If you do not yet have an API token, see [Get an API Access Token](/docs/products/tools/api/guides/manage-api-tokens/) to create one. +- **Linode API Token** *(required)*: Your API token is used to deploy additional Compute Instances as part of this cluster. At a minimum, this token must have Read/Write access to *Linodes*. If you do not yet have an API token, see [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/) to create one. - **Limited sudo user** *(required)*: A limited user account with sudo access is created as part of this cluster deployment. Enter your preferred username for this limited user. The password is automatically created. diff --git a/docs/products/tools/marketplace/guides/hashicorp-nomad-cluster/index.md b/docs/products/tools/marketplace/guides/hashicorp-nomad-cluster/index.md index 0df07ac97b0..6c715a454d7 100644 --- a/docs/products/tools/marketplace/guides/hashicorp-nomad-cluster/index.md +++ b/docs/products/tools/marketplace/guides/hashicorp-nomad-cluster/index.md @@ -34,7 +34,7 @@ Please be aware that each Compute Instance will appear on your invoice as a sepa ### Nomad Cluster Options -- **Linode API Token** *(required)*: Your API token is used to deploy additional Compute Instances as part of this cluster. At a minimum, this token must have Read/Write access to *Linodes*. If you do not yet have an API token, see [Get an API Access Token](/docs/products/tools/api/guides/manage-api-tokens/) to create one. +- **Linode API Token** *(required)*: Your API token is used to deploy additional Compute Instances as part of this cluster. At a minimum, this token must have Read/Write access to *Linodes*. If you do not yet have an API token, see [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/) to create one. - **Limited sudo user** *(required)*: A limited user account with sudo access is created as part of this cluster deployment. Enter your preferred username for this limited user. The sudo password is automatically created and stored in the `~/.deployment_secrets.txt` file. See [Accessing the Nomad Web UI](#accessing-the-nomad-web-ui) below. diff --git a/docs/products/tools/marketplace/guides/jenkins/index.md b/docs/products/tools/marketplace/guides/jenkins/index.md index 8a59dcc4477..6f575bcb968 100644 --- a/docs/products/tools/marketplace/guides/jenkins/index.md +++ b/docs/products/tools/marketplace/guides/jenkins/index.md @@ -49,7 +49,7 @@ After deploying your Jenkins instance, you are ready to log in and continue the 0f6fed516bc4ceab24373fe5de513dc ``` -1. Open a browser and navigate to `http://192.0.2.0:8080/`. Replace `192.0.2.0` with your [Linode's IP address](/docs/guides/find-your-linodes-ip-address/). This will bring you the *Unlock Jenkins* page. Enter the password you retrieved in the previous step and click **continue**. +1. Open a browser and navigate to `http://192.0.2.0:8080/`. Replace `192.0.2.0` with your [Linode's IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). This will bring you the *Unlock Jenkins* page. Enter the password you retrieved in the previous step and click **continue**. ![Log into Jenkins with your admin password](jenkins-admin-login.png) diff --git a/docs/products/tools/marketplace/guides/jupyterlab/index.md b/docs/products/tools/marketplace/guides/jupyterlab/index.md index ea8f1418da1..d918c103554 100644 --- a/docs/products/tools/marketplace/guides/jupyterlab/index.md +++ b/docs/products/tools/marketplace/guides/jupyterlab/index.md @@ -44,7 +44,7 @@ Launch your web browser and navigate to the custom domain you set during deploym ## Obtaining the Jupyter Token -By default, Jupyter issues a token for authentication. The Jupyter access token was automatically generated during the initial install process and is stored in the `/home/$USERNAME/.credentials` file. To view the default token, log in to your Compute Instance either through the [LISH Console](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish) or via SSH, and check the contents of the file: +By default, Jupyter issues a token for authentication. The Jupyter access token was automatically generated during the initial install process and is stored in the `/home/$USERNAME/.credentials` file. To view the default token, log in to your Compute Instance either through the [LISH Console](/docs/products/compute/compute-instances/guides/lish/#through-cloud-manager-weblish) or via SSH, and check the contents of the file: ```command cat /home/$USERNAME/.credentials diff --git a/docs/products/tools/marketplace/guides/linuxgsm/index.md b/docs/products/tools/marketplace/guides/linuxgsm/index.md index a2690786c76..fa1e9fd6599 100644 --- a/docs/products/tools/marketplace/guides/linuxgsm/index.md +++ b/docs/products/tools/marketplace/guides/linuxgsm/index.md @@ -41,7 +41,7 @@ external_resources: ### Obtaining the Admin Password -The password for the sudo user account was automatically generated during the initial install process. To find this password, log in to your Compute Instance through the [LISH Console](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish), or with SSH if you provided an [Account Key](/docs/products/platform/accounts/guides/manage-ssh-keys/). The credentials are available in the file `/home/$USERNAME/.credentials`: +The password for the sudo user account was automatically generated during the initial install process. To find this password, log in to your Compute Instance through the [LISH Console](/docs/products/compute/compute-instances/guides/lish/#through-cloud-manager-weblish), or with SSH if you provided an [Account Key](/docs/products/platform/accounts/guides/manage-ssh-keys/). The credentials are available in the file `/home/$USERNAME/.credentials`: ```command cat /home/$USERNAME/.credentials diff --git a/docs/products/tools/marketplace/guides/mastodon/index.md b/docs/products/tools/marketplace/guides/mastodon/index.md index 34c8a972c46..620ba6d942b 100644 --- a/docs/products/tools/marketplace/guides/mastodon/index.md +++ b/docs/products/tools/marketplace/guides/mastodon/index.md @@ -44,7 +44,7 @@ The Mastodon Marketplace App *requires* a custom domain. After deploying Mastodo {{% content "marketplace-required-limited-user-fields-shortguide" %}} - **Domain** (*required*): The domain name you wish to use for the mastodon server, such as *example.com*. -- **Linode API Token** (*required*): A personal access token for your account. The Linode API is used to create DNS records for your custom domain through the [DNS Manager](/docs/products/networking/dns-manager/). See [Get an API Access Token](/docs/products/tools/api/guides/manage-api-tokens/). +- **Linode API Token** (*required*): A personal access token for your account. The Linode API is used to create DNS records for your custom domain through the [DNS Manager](/docs/products/networking/dns-manager/). See [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/). - **Email for the Let's Encrypt certificate** (*required*): The email you wish to use when creating your TLS/SSL certificate through Let's Encrypt. This email address receives notifications when the certificate needs to be renewed. - **Username for the Mastodon Owner** (*required*): The username for the Owner user that will be created for the Mastodon server. - **Email Address for the Mastodon Owner** (*required*): The contact email for the Mastodon server's owner. diff --git a/docs/products/tools/marketplace/guides/mistio/index.md b/docs/products/tools/marketplace/guides/mistio/index.md index 25a1dc4dad7..810fc815714 100644 --- a/docs/products/tools/marketplace/guides/mistio/index.md +++ b/docs/products/tools/marketplace/guides/mistio/index.md @@ -48,7 +48,7 @@ Once the Mist.io server is successfully created, a few additional steps must be ### Log In to Mist.io -1. In a web browser, enter your Linode's [IP address](/docs/guides/find-your-linodes-ip-address/) or the [Domain](/docs/products/networking/dns-manager/) associated with it to access your Mist.io App's login screen. +1. In a web browser, enter your Linode's [IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) or the [Domain](/docs/products/networking/dns-manager/) associated with it to access your Mist.io App's login screen. 1. Click on the **Sign in** button at the top right of the page. diff --git a/docs/products/tools/marketplace/guides/mongodb-cluster/index.md b/docs/products/tools/marketplace/guides/mongodb-cluster/index.md index 8d027bdc675..b636e12f114 100644 --- a/docs/products/tools/marketplace/guides/mongodb-cluster/index.md +++ b/docs/products/tools/marketplace/guides/mongodb-cluster/index.md @@ -36,7 +36,7 @@ This Marketplace App deploys 3 Compute Instances to create a highly available an ### MongoDB Options -- **Linode API Token** *(required)*: Your API token is used to deploy additional Compute Instances as part of this cluster. At a minimum, this token must have Read/Write access to *Linodes*. If you do not yet have an API token, see [Get an API Access Token](/docs/products/tools/api/guides/manage-api-tokens/) to create one. +- **Linode API Token** *(required)*: Your API token is used to deploy additional Compute Instances as part of this cluster. At a minimum, this token must have Read/Write access to *Linodes*. If you do not yet have an API token, see [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/) to create one. - **Limited sudo user** *(required)*: A limited user account with sudo access is created as part of this cluster deployment. Enter your preferred username for this limited user. The password is automatically created. See [Obtaining Usernames and Passwords](#obtaining-usernames-and-passwords). diff --git a/docs/products/tools/marketplace/guides/nats-single-node/index.md b/docs/products/tools/marketplace/guides/nats-single-node/index.md index 5c2bb3dda99..ea5bc19481b 100644 --- a/docs/products/tools/marketplace/guides/nats-single-node/index.md +++ b/docs/products/tools/marketplace/guides/nats-single-node/index.md @@ -50,7 +50,7 @@ Open your web browser and go to the custom domain you specified during deploymen ## Obtaining the NATS users passwords. -By default, this NATS deployment creates 2 users, one named "example" and another system user named "system". The passwords for these users are generated during the initial install process. To obtain these password, log in to your Compute Instance either through the [LISH Console](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish) or via SSH, then just read the `/home/$USERNAME/.credentials` file, ie: +By default, this NATS deployment creates 2 users, one named "example" and another system user named "system". The passwords for these users are generated during the initial install process. To obtain these password, log in to your Compute Instance either through the [LISH Console](/docs/products/compute/compute-instances/guides/lish/#through-cloud-manager-weblish) or via SSH, then just read the `/home/$USERNAME/.credentials` file, ie: ```command cat /home/$USERNAME/.credentials diff --git a/docs/products/tools/marketplace/guides/openvpn/index.md b/docs/products/tools/marketplace/guides/openvpn/index.md index bc7ad512a88..10e3818240d 100644 --- a/docs/products/tools/marketplace/guides/openvpn/index.md +++ b/docs/products/tools/marketplace/guides/openvpn/index.md @@ -64,7 +64,7 @@ For more details on logging in to the OpenVPN admin interface for the first time ### Obtaining the Admin Password -The password for the main administrator account was automatically generated during the initial install process. To find this password, log in to your Compute Instance through the [LISH Console](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish). The credentials are available in the file `/root/.credentials` +The password for the main administrator account was automatically generated during the initial install process. To find this password, log in to your Compute Instance through the [LISH Console](/docs/products/compute/compute-instances/guides/lish/#through-cloud-manager-weblish). The credentials are available in the file `/root/.credentials` ``` cat /root/.credentials Sudo Username: $SUDO_USER diff --git a/docs/products/tools/marketplace/guides/percona-monitoring-management/index.md b/docs/products/tools/marketplace/guides/percona-monitoring-management/index.md index 4754b2a7d8e..2ade9369fae 100644 --- a/docs/products/tools/marketplace/guides/percona-monitoring-management/index.md +++ b/docs/products/tools/marketplace/guides/percona-monitoring-management/index.md @@ -137,7 +137,7 @@ The PMM Server deployed with Linode's Percona (PMM) Marketplace App is compatibl 1. Connect your database node to the PMM Server. Replace `admin_password` with your PMM Server's [Grafana password](#access-your-PMM-server-s-grafana-dashboard), and `192.0.2.0` with your PMM Server's IPv4 address. {{< note >}} - Follow the steps in [Find Your Linode's IP Address](/docs/guides/find-your-linodes-ip-address/) to retrieve your PMM Server's IPv4 address. + Follow the steps in [Find Your Linode's IP Address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) to retrieve your PMM Server's IPv4 address. {{< /note >}} pmm-admin \ diff --git a/docs/products/tools/marketplace/guides/plex/index.md b/docs/products/tools/marketplace/guides/plex/index.md index 5a885d4d718..a50043d2d6d 100644 --- a/docs/products/tools/marketplace/guides/plex/index.md +++ b/docs/products/tools/marketplace/guides/plex/index.md @@ -75,7 +75,7 @@ Your shell then interprets `$IP_ADDRESS` as the value you have provided in follo ``` {{< /note >}} -1. From your workstation [terminal](/docs/guides/using-the-terminal/), enter the following the command, substituting `$USERNAME` with your Linux [Limited User Name](#plex-marketplace-app-options), and `$IP_ADDRESS` with the [IP address](/docs/guides/find-your-linodes-ip-address/) of your Plex Server Linode: +1. From your workstation [terminal](/docs/guides/using-the-terminal/), enter the following the command, substituting `$USERNAME` with your Linux [Limited User Name](#plex-marketplace-app-options), and `$IP_ADDRESS` with the [IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) of your Plex Server Linode: ssh $USERNAME@$IP_ADDRESS -L 8888:localhost:32400 @@ -176,7 +176,7 @@ This section directs you to run commands either on your Plex Server Linode throu mkdir ~/plex/media/movies -1. From your media workstation, use the `scp` command to move media to your Plex Server's media subdirectory, substituting `$USERNAME` with your Linux [Limited User Name](#plex-marketplace-app-options), and `$IP_ADDRESS` with the [IP address](/docs/guides/find-your-linodes-ip-address/) of your Plex Server Linode: +1. From your media workstation, use the `scp` command to move media to your Plex Server's media subdirectory, substituting `$USERNAME` with your Linux [Limited User Name](#plex-marketplace-app-options), and `$IP_ADDRESS` with the [IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) of your Plex Server Linode: scp example_video.mp4 $USERNAME@$IP_ADDRESS:~/plex/media/movies diff --git a/docs/products/tools/marketplace/guides/postgresql-cluster/index.md b/docs/products/tools/marketplace/guides/postgresql-cluster/index.md index f80868263f0..92036ca5cda 100644 --- a/docs/products/tools/marketplace/guides/postgresql-cluster/index.md +++ b/docs/products/tools/marketplace/guides/postgresql-cluster/index.md @@ -32,7 +32,7 @@ This Marketplace App deploys 3 Compute Instances to create a highly available an ### PostgreSQL Options -- **Linode API Token** *(required)*: Your API token is used to deploy additional Compute Instances as part of this cluster. At a minimum, this token must have Read/Write access to *Linodes*. If you do not yet have an API token, see [Get an API Access Token](/docs/products/tools/api/guides/manage-api-tokens/) to create one. +- **Linode API Token** *(required)*: Your API token is used to deploy additional Compute Instances as part of this cluster. At a minimum, this token must have Read/Write access to *Linodes*. If you do not yet have an API token, see [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/) to create one. - **Limited sudo user** *(required)*: A limited user account with sudo access is created as part of this cluster deployment. Enter your preferred username for this limited user. The password is automatically created. See [Obtaining Usernames and Passwords](#obtaining-usernames-and-passwords). diff --git a/docs/products/tools/marketplace/guides/redis-cluster/index.md b/docs/products/tools/marketplace/guides/redis-cluster/index.md index ab1b3a8f3dc..c358a8fa578 100644 --- a/docs/products/tools/marketplace/guides/redis-cluster/index.md +++ b/docs/products/tools/marketplace/guides/redis-cluster/index.md @@ -32,7 +32,7 @@ This Marketplace App deploys 3 or 5 Compute Instances to create a highly availab ### Redis Sentinel Options -- **Linode API Token** *(required)*: Your API token is used to deploy additional Compute Instances as part of this cluster. At a minimum, this token must have Read/Write access to *Linodes*. If you do not yet have an API token, see [Get an API Access Token](/docs/products/tools/api/guides/manage-api-tokens/) to create one. +- **Linode API Token** *(required)*: Your API token is used to deploy additional Compute Instances as part of this cluster. At a minimum, this token must have Read/Write access to *Linodes*. If you do not yet have an API token, see [Get an API Access Token](/docs/products/platform/accounts/guides/manage-api-tokens/) to create one. - **Limited sudo user** *(required)*: A limited user account with sudo access is created as part of this cluster deployment. Enter your preferred username for this limited user. The password is automatically created. See [Obtaining Usernames and Passwords](#obtaining-usernames-and-passwords). diff --git a/docs/products/tools/marketplace/guides/splunk/index.md b/docs/products/tools/marketplace/guides/splunk/index.md index e44975743f7..55d9dc3671b 100644 --- a/docs/products/tools/marketplace/guides/splunk/index.md +++ b/docs/products/tools/marketplace/guides/splunk/index.md @@ -49,7 +49,7 @@ The Akamai Connected Cloud Splunk Marketplace App includes support for the [Akam ### Obtaining the Admin Password -The password for the sudo user account was automatically generated during the initial install process. To find this password, log in to your Compute Instance through the [LISH Console](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish). The credentials are available in the file `/home/$USERNAME/.credentials` +The password for the sudo user account was automatically generated during the initial install process. To find this password, log in to your Compute Instance through the [LISH Console](/docs/products/compute/compute-instances/guides/lish/#through-cloud-manager-weblish). The credentials are available in the file `/home/$USERNAME/.credentials` ``` cat /home/$USERNAME/.credentials sudo username: $USERNAME