News:

SMF - Just Installed!

Main Menu

Recent posts

#41
Webserver / Apache is failing to start in ...
Last post by Suhitha - Sep 29, 2025, 05:40 AM
Question: Apache is failing to start in Plesk: Error: New configuration files for the Apache web server were not created due to the errors in configuration templates: AH00112: Warning: DocumentRoot [/usr/share/plesk-service.localdomain] does not exist


Symptoms

  • The following error message is displayed in Plesk:

Error: New configuration files for the Apache web server were not created due to the errors in configuration templates: AH00112: Warning: DocumentRoot [/usr/share/plesk-service.localdomain] does not exist AH00112: Warning: DocumentRoot [/usr/share/plesk-service.localdomain] does not exist AH00526: Syntax error on line 22 of /etc/apache2/plesk.conf.d/vhosts/example.com.conf: SuexecUserGroup configured, but suEXEC is disabled: Missing suexec binary /usr/lib/apache2/suexec. Search in KB
  • Errors like below can be found in the /var/log/apt/term.log:

Removing plesk-awstats-configurator (18.0-v.ubuntu.22.04+p18.0.56.0+t230919.0744) ...
Removing plesk-roundcube (1.6.5-v.ubuntu.22.04+p18.0.57.0+t231107.0857) ...
Removing plesk-web-hosting (18.0-v.ubuntu.22.04+p18.0.57.0+t231106.2014) ...
Removing psa-proftpd (1.3.8a-v.ubuntu.22.04+p18.0.57.0+t231106.2014) ...


Cause


plesk-web-hosting package is missing or was uninstalled accidentally during another package installation.
For example the unsupported vsftpd package was installed recently and it has removed several Plesk packages during its installation.


Resolution

1.Connect to the server via SSH

2.Remove the recently installed package, on this example vsftpd, Plesk uses ProFTPd instead:

# apt remove vsftpd
3.Navigate to Tools & Settings > Updates and press Add/Remove Components button.

4.Select required components for installation (for example, if plesk-roundcube was removed, select Webmail services/Roundcube for installation.

5.Press Continue button to install the packages. Missing plesk-web-hosting package will be installed automatically.
#42
Web Application / How to Convert an Existing Vul...
Last post by Suhitha - Sep 29, 2025, 05:28 AM
Question: How to Convert an Existing Vultr Instance IP Address to a Reserved IP


Learn how to convert an existing IP address on your Vultr instance to a different type of IP address.

Converting an existing instance IP address to a reserved IP enables it as a dedicated address you can attach or detach to other instances in your Vultr account. A reserved IP is compatible with any instance you can attach or detach it to.

Follow this guide to convert an existing Vultr instance IP Address to a reserved IP using the Vultr Customer Portal, API, or CLI.


Vultr Customer Portal

1.Navigate to Products, expand the Network drop-down and select Reserved IPs from the list of options.

2.Click Add Reserved IP to set up a new reserved IP address.

3.Click the IPv4 Address or IPv6 subnet drop-down to select your existing IP and click Convert.

4.Click Convert IP Address in the confirmation prompt to create a new reserved IP using the existing IP.


Vultr API

1.Send a GET request to the List Instances endpoint and note the target instance IP.

console


$ curl "https://api.vultr.com/v2/instances" \
  -X GET \
  -H "Authorization: Bearer ${VULTR_API_KEY}"


2.Send a POST request to the Convert Existing IP endpoint to create a new reserved IP using the instance's IP address.

console


$ curl "https://api.vultr.com/v2/reserved-ips/convert" \
   -X POST \
   -H "Authorization: Bearer ${VULTR_API_KEY}"
   -H "Content-Type: application/json" \
   --data '{
     "ip_address": "<instance-ip>",
     "label": "<label>"
   }'


Vultr CLI

1.List all instances in your Vultr account and note the target instance's IP.

console


$ vultr-cli instance list

2.Convert the target instance IP to a reserved IP address.

console


$ vultr-cli reserved-ip convert --ip="<instance-ip>" --label="<label>"
#43
Web Application / How to Delete a Reserved IP
Last post by Suhitha - Sep 29, 2025, 05:16 AM
Question: How to Delete a Reserved IP


Permanently removes a resource from your Vultr account.

Deleting a reserved IP detaches it from any linked instances and removes it from your Vultr account. You can re-create a reserved IP after deletion if it's available in the specific Vultr location.

Follow this guide to delete a reserved IP using the Vultr Customer Portal, API, CLI, or Terraform.

Vultr Customer Portal

1.Navigate to Products, expand the Network drop-down and select Reserved IPs from the list of options.

2.Click your target reserved IP to open its management page.

3.Click Remove Reserved IP in the top-right corner.

4.Click Remove Reserved IP in the confirmation prompt to delete the reserved IP.


Vultr API

1.Send a GET request to the List Reserved IPs endpoint and note the target reserved IP's ID in your output.

console


$ curl "https://api.vultr.com/v2/reserved-ips" \
   -X GET \
   -H "Authorization: Bearer ${VULTR_API_KEY}"


2.Send a DELETE request to the Delete Reserved IP endpoint to delete the reserved IP.

console


$ curl "https://api.vultr.com/v2/reserved-ips/{reserved-ip}" \
  -X DELETE \
  -H "Authorization: Bearer ${VULTR_API_KEY}"


Vultr CLI

1.Send a GET request to the List Reserved IPs endpoint and note the target reserved IP's ID in your output.

console


$ curl "https://api.vultr.com/v2/reserved-ips" \
   -X GET \
   -H "Authorization: Bearer ${VULTR_API_KEY}"

2.Send a DELETE request to the Delete Reserved IP endpoint to delete the reserved IP.

console


$ curl "https://api.vultr.com/v2/reserved-ips/{reserved-ip}" \
  -X DELETE \
  -H "Authorization: Bearer ${VULTR_API_KEY}"


Terraform

1.Open your Terraform configuration where the Reserved IP is defined.

2.Remove the vultr_reserved_ip resource block, or destroy it by target.

terraform


resource "vultr_reserved_ip" "rip" {
    region  = "ewr"
    ip_type = "v4"
    label   = "web-rip"
}

# To delete, either remove this block from configuration
# or run: terraform destroy -target vultr_reserved_ip.rip

3.Apply the configuration and observe the following output:

Apply complete! Resources: 0 added, 0 changed, 1 destroyed.
#44
Web Application / How to Manage Automatic Backup...
Last post by Suhitha - Sep 29, 2025, 05:05 AM
Question: How to Manage Automatic Backups for Vultr Cloud Compute


The process of setting up and configuring a new server or service to make it ready for use.

Automatic Backups for Vultr instances are scheduled point-in-time data recovery solutions that allow you to backup your Cloud Compute instances' data with minimal intervention. These backups are suitable for mission-critical applications because they aid in data protection, disaster recovery, compliance, and auditing. Vultr supports daily, every other day, weekly, and monthly backup schedules.

Follow this guide to manage Automatic Backups for Vultr instances using the Vultr Customer Portal, API, CLI, or Terraform.


Vultr Customer Portal

1.Navigate to Products and select Compute.

2.Select your target Cloud Compute instance from the list.

3.Navigate to Backups and click Enable Backups.

4.Click Enable Backups to confirm.

5.Navigate to Backup Schedule. Then, select daily, weekly, or every other day backup schedule. Set the day of the week and time and click Update.

6.From this point forward, any new backup appears under the backup history. Click Convert to convert the backup to a manual snapshot or Restore to restore the backup to the cloud compute instance.

7.Navigate to Products, select Orchestration, then click Backups. Click the camera icon to convert the backup to a snapshot.


Vultr API

1.Send a GET request to the List Instances endpoint to get the Cloud Compute instance ID.

console


$ curl "https://api.vultr.com/v2/instances" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"


2.Send a PATCH request to the Update Instance endpoint to turn on automatic backups.

console


$ curl "https://api.vultr.com/v2/instances/instance_id" \
    -X PATCH \
    -H "Authorization: Bearer ${VULTR_API_KEY}" \
    -H "Content-Type: application/json" \
    --data '{
        "backups" : "enabled",
        "backups_schedule" : {
            "type" : "daily",
            "hour" : "0"
        } 
    }'

3.Send a PATCH request to the Update Instance endpoint to turn off automatic backups.

console


$ curl "https://api.vultr.com/v2/instances/instance_id" \
    -X PATCH \
    -H "Authorization: Bearer ${VULTR_API_KEY}" \
    -H "Content-Type: application/json" \
    --data '{
        "backups" : "disabled"   
    }'

Visit the Update Instance endpoint to view additional attributes to add to your request.

4.Send a GET request to the List Backups endpoint and note the backup ID.

console


$ curl "https://api.vultr.com/v2/backups" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"


5.Send a GET request to the Get Backup endpoint and specify the backup ID to view the backup details.

console


$ curl "https://api.vultr.com/v2/backups/backup_id" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"


Vultr CLI

1.List all cloud compute instances and note the instance ID.

console


$ vultr-cli instance list


2.Update the backup schedule by specifying the instance_id.

console


$ vultr-cli instance backup create instance_id --type weekly --dow 0 --hour 0

3.List all backups by specifying a cloud compute instance ID.

console


$ vultr-cli instance backup get instace_id


4.List all Cloud Compute instance backups.

console


$ vultr-cli backups list


5.Get details of a specific backup by specifying the backup ID.

console


$ vultr-cli backups get backup_id

Run vultr-cli instance backup create --help to view all options.


Terraform

1.Open your Terraform configuration for the existing instance.

2.Enable automatic backups and optionally set a backup schedule.

terraform


resource "vultr_instance" "server" {
    # ...existing fields (region, plan, os_id or snapshot_id, label)

    backups = true

    # Optional: schedule (availability depends on plan)
    backups_schedule {
        type = "daily"    # daily | weekly | alternating
        hour = 0          # 0-23
        # dow = 0         # for weekly: 0=Sunday ... 6=Saturday
    }
}

3.Apply the configuration and observe the following output:

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
#45
Web Application / How to Manage ISO Images for V...
Last post by Suhitha - Sep 29, 2025, 04:27 AM
Question: How to Manage ISO Images for Vultr Instances


The process of setting up and configuring a new server or service to make it ready for use.

ISO Images for Vultr instances are compressed copies of an operating system's installer. These images allow you to install custom operating systems on Cloud Compute instances. The ISO files may contain pre-configured settings and software according to specific needs to streamline server setup. The Vultr library also allows you to choose and install various public standard ISOs including Finnix, GParted, Hiren's BootCD PE, and SystemRescue.

Follow this guide to manage ISO Images for Vultr instances using the Vultr Customer Portal, API, CLI, or Terraform.


Vultr Customer Portal

1.Navigate to Products and select Orchestration. Then, choose ISOs.

2.Click Add ISO.

3.Enter the remote URL of your ISO file and click Upload.


Vultr API

1.Send a POST request to the Create ISO endpoint and specify the remote ISO file URL.

console


$ curl "https://api.vultr.com/v2/iso" \
    -X POST \
    -H "Authorization: Bearer ${VULTR_API_KEY}" \
    -H "Content-Type: application/json" \
    --data '{
        "url" : "https://example.com/remote_iso_file_url.iso"
    }'

Visit the Create ISO endpoint to view additional attributes to add to your request.

2.Send a GET request to the List ISOs endpoint to list all ISOs.

console


$ curl "https://api.vultr.com/v2/iso" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"


Vultr CLI

1.Create an ISO from an URL by defining the URL where you want to download the ISO file.

console


$ vultr-cli iso create --url https://releases.ubuntu.com/24.04/ubuntu-24.04-live-server-amd64.iso

2.List all ISOs.

console


$ vultr-cli iso list


3.List specific details about an ISO by specifying the ISO ID.

console


$ vultr-cli iso get iso_id


Run vultr-cli iso create --help to view all options.


Terraform

1.Define a custom ISO by URL and apply.

terraform


resource "vultr_iso" "custom_iso" {
    url = "https://example.com/remote_iso_file_url.iso"
}


2.Attach the ISO when creating an instance. Remember to set os_id = 159 for custom ISO boot.

terraform


resource "vultr_instance" "server" {
    region = "ewr"
    plan   = "vc2-2c-4gb"
    label  = "iso-boot"

    os_id = 159          # required for custom ISO
    iso_id = vultr_iso.custom_iso.id
}

3.Apply the configuration and observe the following output:

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.
#46
Web Application / How to Delete ISO Images for V...
Last post by Suhitha - Sep 29, 2025, 03:41 AM
Question: How to Delete ISO Images for Vultr Instances


Learn how to permanently remove custom ISO files from your Vultr account when theyre no longer needed.

Deleting ISO Images for Vultr instances allows you to completely remove the file from your account and make room for more images. Vultr only permits two ISO files at a time. Removing an ISO file doesn't affect any Cloud Compute instances you've provisioned using the image.

Follow this guide to delete ISO images for Vultr instances using the Vultr Customer Portal, API, CLI, or Terraform.


Vultr Customer Portal

1.Navigate to Products and select Orchestration. Then, choose ISOs.

2.Select the target ISO image from the list and click the delete icon.

3.Click Delete ISO to confirm.


Vultr API

1.Send a GET request to the List ISOs endpoint to list all ISOs.

console


$ curl "https://api.vultr.com/v2/iso" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"


2.Send a DELETE request to the Delete ISO endpoint and specify an ISO ID to delete the ISO file.

console


$ curl "https://api.vultr.com/v2/iso/iso_id" \
    -X DELETE \
    -H "Authorization: Bearer ${VULTR_API_KEY}"


Visit the Delete ISO endpoint to view additional attributes to add to your request.


Vultr CLI

1.List all cloud compute instances and note the instance ID.

console


$ vultr-cli instance list


2.List all ISOs and note the ISO ID.

console


$ vultr-cli iso list

3.Delete an ISO by specifying an ISO ID.

console


$ vultr-cli iso delete iso_id

Run vultr-cli iso delete --help to view all options.
#47
Web Application / How to Delete Backups for Vult...
Last post by Suhitha - Sep 29, 2025, 03:30 AM
Question: How to Delete Backups for Vultr Instances


Learn how to permanently remove backup snapshots from your Vultr account to free up storage space.

Deleting backups for Vultr instances completely removes the files from your account. You should perform this operation after restoring the required backup files. You can also consider converting a backup to a snapshot before deleting the backup. After deleting a backup, you can't undo the operation and you should take great care before making the decision.

Follow this guide to delete Backups for Vultr instances using the Vultr Customer Portal.


Vultr Customer Portal

1.Navigate to Products, select Orchestration, then click Backups.

2.Click the delete icon to remove the backup.

3.Click Remove Backup to confirm.
#48
Web Application / How to Manage Snapshots for Vu...
Last post by Suhitha - Sep 29, 2025, 03:25 AM
Question: How to Manage Snapshots for Vultr Instances


A process that prepares and configures a new server or service to make it ready for use.

Snapshots for Vultr instances are point-in-time images of your entire Cloud Compute instances hard drives. You can use snapshots to create backups or to replicate Cloud Compute instances. Unlike Automatic Backups for Vultr instances, you must take snapshots manually.

Follow this guide to manage Snapshots for Vultr instances using the Vultr Customer Portal, API, CLI, or Terraform.

Vultr Customer Portal

1.Navigate to Products and select Compute.

2.Select your target Cloud Compute instance from the list.

3.Navigate to Snapshots, enter a label and click Take Snapshot.


Vultr API

1.Send a GET request to the List Instances endpoint to get the Cloud Compute instance ID.

console


$ curl "https://api.vultr.com/v2/instances" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"

2.Send a POST request to the Create Snapshot endpoint specifying a cloud compute instance ID to create a snapshot.

console


$ curl "https://api.vultr.com/v2/snapshots" \
    -X POST \
    -H "Authorization: Bearer ${VULTR_API_KEY}" \
        -H "Content-Type: application/json" \
        --data '{
            "instance_id" : "instance_id",
            "description" : "Weekly-Snapshot-14-08-2024"
        }'

Visit the Create Snapshot endpoint to view additional attributes to add to your request.

3.Send a GET request to the List Snapshots endpoint to view all snapshots.

console


$ curl "https://api.vultr.com/v2/snapshots" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"


Vultr CLI

1.List all cloud compute instances and note the instance ID.

console


$ vultr-cli instance list


2.Create a snapshot by specifying the Cloud Compute instance ID and the snapshot description.

console


$ vultr-cli snapshot create --id instance_id --description "Weekly Snapshot 14-08-2024"

3.List all snapshots.

console


$ vultr-cli snapshot list


Run vultr-cli snapshot create --help to view all options.


Terraform

1.Create a snapshot from an existing instance.

terraform


resource "vultr_snapshot" "weekly" {
    instance_id = var.instance_id
    description = "Weekly-Snapshot-14-08-2024"
}


2.Optionally, boot a new instance from a snapshot by setting snapshot_id.

terraform


resource "vultr_instance" "from_snapshot" {
    region      = "ewr"
    plan        = "vc2-2c-4gb"
    label       = "restored"
    snapshot_id = vultr_snapshot.weekly.id
}

3.Apply the configuration and observe the following output:

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
#49
Web Application / How to Delete Snapshots
Last post by Suhitha - Sep 29, 2025, 03:07 AM
Question: How to Delete Snapshots

Permanently removes the selected resource from your Vultr account.

Deleting snapshots completely removes the resource from your account. You should only do this operation after restoring a snapshot to a Vultr Cloud Compute instance or after provisioning a Vultr Cloud Compute instance using the snapshot image. After deleting a snapshot, you can't undo the operation, so you should take great care.

Follow this guide to delete snapshots using the Vultr Customer Portal, API, CLI, or Terraform.

Vultr Customer Portal


1.Navigate to Products and select Orchestration.

2.Click Snapshots. Select the target snapshot from the list and click the delete icon to remove the snapshot.

3.Click Remove Snapshot to confirm.


Vultr API

1.Send a GET request to the List Snapshots endpoint to list all snapshots.

console


$ curl "https://api.vultr.com/v2/snapshots" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"


2.Send a DELETE request to the Delete Snapshot endpoint specifying a snapshot ID to delete a snapshot.

console


$ curl "https://api.vultr.com/v2/snapshots/snapshot_id" \
    -X DELETE \
    -H "Authorization: Bearer ${VULTR_API_KEY}"


Visit the Delete Snapshot endpoint to view additional attributes to add to your request.


Vultr CLI

1.List all snapshots and note the target snapshot's ID.

console


$ vultr-cli snapshot list


2.Delete a snapshot by specifying a snapshot ID.

console


$ vultr-cli snapshot delete snapshot_id

Run vultr-cli snapshot delete --help to view all options.


Terraform

1.Open your Terraform configuration where the snapshot resource was created.

2.Remove the vultr_snapshot resource block, or destroy it by target.

terraform


resource "vultr_snapshot" "weekly" {
    instance_id = var.instance_id
    description = "Weekly-Snapshot-14-08-2024"
}

# To delete, either remove this block from configuration
# or run: terraform destroy -target vultr_snapshot.weekly


3.Apply the configuration and observe the following output:

Apply complete! Resources: 0 added, 0 changed, 1 destroyed.


#50
Web Application / How to Restore Snapshots
Last post by Suhitha - Sep 29, 2025, 02:44 AM
Question: How to Restore Snapshots

Recover your server to a previous state using a backup or snapshot.

Restoring a snapshot involves recovering the exact state of a system at the time the snapshot was created. Snapshots capture the complete configuration, including the operating system, applications, and data, making it easy to revert to a specific point in time. This process is essential for system recovery, testing, or duplicating environments, ensuring consistency and minimizing downtime.

Follow this guide to restore snapshots using the Vultr Customer Portal, API, CLI, or Terraform.

Note
When restoring a server backup that uses a static IP, you must reset the network to DHCP to obtain a functional IP address. If network configuration needs to be reset after restoring a snapshot, refer to Return a Vultr Server to the Default DHCP Configuration. Restoring a snapshot on existing Vultr Cloud Compute servers or provisioning new servers using snapshots may take an additional 10-15 minutes compared to standard operations.


Vultr Customer Portal

1.Navigate to Products and click Compute.

2.Click your target Vultr Cloud Compute instance to open its management page.

3.Navigate to the Snapshots tab.

4.Choose any snapshot you want to restore.

Click "Restore Snapshot" to start the restoration procedure on that target Vultr Cloud Compute instance.

Optional: To provision a new Vultr Cloud Compute instance with snapshot, select Snapshot in the Choose Image section. How to Provision Vultr Cloud Compute Instance.


Vultr API

1.Send a GET request to the List Snapshots endpoint to list all snapshots.

console


$ curl "https://api.vultr.com/v2/snapshots" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"


2.Send a GET request to the List Instances endpoint to list all deployed Vultr Cloud Compute instances. Note the target instance's ID.

console


$ curl "https://api.vultr.com/v2/instances" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"

3.Send a POST request to the Restore Instances endpoint to start the restore procedure of the target Vultr Cloud Compute instance.

console


$ curl "https://api.vultr.com/v2/instances/<instance-id>/restore" \
    -X POST \
    -H "Authorization: Bearer ${VULTR_API_KEY}" \
    -H "Content-Type: application/json" \
    --data '{
        "snapshot_id": "<snapshot-id>"
    }'


4.Optional: Send a POST request to the Create Instances endpoint to provision a new Vultr Cloud Compute instance using snapshot.

console


$ curl "https://api.vultr.com/v2/instances" \
    -X POST \
    -H "Authorization: Bearer ${VULTR_API_KEY}" \
    -H "Content-Type: application/json" \
    --data '{
        "region" : "<region>",
        "plan" : "<plan>",
        "snapshot_id" : "<snapshot-id>",
        "label" : "<label>",
        "hostname": "<hostname>"
    }'


Vultr CLI

1.List all snapshots and note the target snapshot's ID.

console


$ vultr-cli snapshot list

2.List all Vultr Cloud Compute instances and note target instance's ID.

console


$ vultr-cli instance list

3.Restore a snapshot on the target Vultr Cloud Compute instance.

console


$ vultr-cli instance restore <instance-id> --snapshot <snapshot-id>


4.Optional: Provision a new Vultr Cloud Compute instance using snapshot.

console


$  vultr-cli instance create --region="<region>" --plan="<plan>" --snapshot="<snapshot-id>" --label="<label>"


Terraform

1.Boot a new instance from a snapshot by setting snapshot_id, or update an existing resource to change its boot image.

terraform


resource "vultr_instance" "restored" {
    region      = "ewr"
    plan        = "vc2-2c-4gb"
    label       = "restored-from-snap"
    snapshot_id = var.snapshot_id
}

2.Apply the configuration and observe the following output:

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.