- Welcome to Cobra Forum.
Recent posts
#11
Web Application / How to Link a Vultr Firewall G...
Last post by Suhitha - Sep 30, 2025, 07:55 AMQuestion: How to Link a Vultr Firewall Group to an Instance
A feature that allows you to connect your Vultr account with third-party services for enhanced functionality and integrations.
Linking a Vultr Firewall group to an instance enables the group's filtering rules to the main network interface. A Vultr Firewall group consists of multiple rules that define the flow of traffic and enable filtering of specific requests when linked to an instance.
Follow this guide to link a Vultr Firewall group to an instance using the Vultr Customer Portal, API, or CLI.
Vultr Customer Portal
1.Navigate to Products, expand the Network drop-down and select Firewall from the list of options.
2.Select your target firewall group to manage it.
3.Click Linked Instances on the left navigation menu.
4.Click the Server drop-down and select your target instance from the list and click Add to link the firewall group to the instance.
Vultr API
1.Send a GET request to the List Firewall Groups endpoint and note the target firewall group's ID in your output.
2.Send a GET request to the List Instances endpoint and note the target instance ID.
3.Send a PATCH request to the Update Instance endpoint with a new firewall_group_id value to link the instance to the firewall group.
Vultr CLI
1.List all firewall groups in your Vultr account and note the target firewall group ID..
2.List all instances in your Vultr account and note the target instance ID.
3.Link the firewall group to the instance.
A feature that allows you to connect your Vultr account with third-party services for enhanced functionality and integrations.
Linking a Vultr Firewall group to an instance enables the group's filtering rules to the main network interface. A Vultr Firewall group consists of multiple rules that define the flow of traffic and enable filtering of specific requests when linked to an instance.
Follow this guide to link a Vultr Firewall group to an instance using the Vultr Customer Portal, API, or CLI.
Vultr Customer Portal
1.Navigate to Products, expand the Network drop-down and select Firewall from the list of options.
2.Select your target firewall group to manage it.
3.Click Linked Instances on the left navigation menu.
4.Click the Server drop-down and select your target instance from the list and click Add to link the firewall group to the instance.
Vultr API
1.Send a GET request to the List Firewall Groups endpoint and note the target firewall group's ID in your output.
Code Select
console
$ curl "https://api.vultr.com/v2/firewalls" \
-X GET \
-H "Authorization: Bearer ${VULTR_API_KEY}"
2.Send a GET request to the List Instances endpoint and note the target instance ID.
Code Select
console
$ curl "https://api.vultr.com/v2/instances" \
-X GET \
-H "Authorization: Bearer ${VULTR_API_KEY}"
3.Send a PATCH request to the Update Instance endpoint with a new firewall_group_id value to link the instance to the firewall group.
Code Select
console
$ curl "https://api.vultr.com/v2/instances/{instance-id}" \
-X PATCH \
-H "Authorization: Bearer ${VULTR_API_KEY}" \
-H "Content-Type: application/json" \
--data '{
"firewall_group_id" : "<target-firewall-group>"
}'Vultr CLI
1.List all firewall groups in your Vultr account and note the target firewall group ID..
Code Select
console
$ vultr-cli firewall group list2.List all instances in your Vultr account and note the target instance ID.
Code Select
console
$ vultr-cli instance list
3.Link the firewall group to the instance.
Code Select
console
$ vultr-cli instance update-firewall-group --instance-id <target-instance> --firewall-group-id <target-firewall-
#12
Others / An alias can enable mail servi...
Last post by senthil - Sep 30, 2025, 07:45 AMSymptoms
Recognized as bug PPPM-14467.
Resolution
The issue will be fixed in one of the next Plesk updates.
There is no workaround currently.
- An alias can enable mail service, despite being disabled on a subscription level.
Recognized as bug PPPM-14467.
Resolution
The issue will be fixed in one of the next Plesk updates.
There is no workaround currently.
#13
Web Application / How to Manage Vultr Firewall G...
Last post by Suhitha - Sep 30, 2025, 07:44 AMQuestion: How to Manage Vultr Firewall Groups
A feature that allows you to organize and manage multiple resources collectively for easier administration and access control.
Vultr Firewall groups enable the creation and application of network filtering rules that apply to attached instances. A firewall group can consist of multiple rules that filter IPv4 and IPv6 network traffic when attached to an instance.
Follow this guide to manage Vultr Firewall groups using the Vultr Customer Portal, API, CLI, or Terraform.
Vultr Customer Portal
1.Navigate to Products, expand the Network drop-down and select Firewall from the list of options.
2.Select your target firewall group to manage it.
Vultr API
1.Send a GET request to the List Firewall Groups endpoint to view all firewall groups in your Vultr account.
Vultr CLI
1.List all firewall groups in your Vultr account.
Terraform
1.Open your Terraform configuration for the existing Firewall groups.
2.Add or update a vultr_firewall_group with example rules, then apply.
3.Apply the configuration and observe the following output:
Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
A feature that allows you to organize and manage multiple resources collectively for easier administration and access control.
Vultr Firewall groups enable the creation and application of network filtering rules that apply to attached instances. A firewall group can consist of multiple rules that filter IPv4 and IPv6 network traffic when attached to an instance.
Follow this guide to manage Vultr Firewall groups using the Vultr Customer Portal, API, CLI, or Terraform.
Vultr Customer Portal
1.Navigate to Products, expand the Network drop-down and select Firewall from the list of options.
2.Select your target firewall group to manage it.
Vultr API
1.Send a GET request to the List Firewall Groups endpoint to view all firewall groups in your Vultr account.
Code Select
console
$ curl "https://api.vultr.com/v2/firewalls" \
-X GET \
-H "Authorization: Bearer ${VULTR_API_KEY}"Vultr CLI
1.List all firewall groups in your Vultr account.
Code Select
console
$ vultr-cli firewall group listTerraform
1.Open your Terraform configuration for the existing Firewall groups.
2.Add or update a vultr_firewall_group with example rules, then apply.
Code Select
terraform
resource "vultr_firewall_group" "default" {
description = "default-fw"
}
resource "vultr_firewall_rule" "allow_http" {
firewall_group_id = vultr_firewall_group.default.id
protocol = "tcp"
port = "80"
ip_type = "v4"
subnet = "0.0.0.0"
subnet_size = 0
notes = "Allow HTTP"
}
resource "vultr_firewall_rule" "allow_https" {
firewall_group_id = vultr_firewall_group.default.id
protocol = "tcp"
port = "443"
ip_type = "v4"
subnet = "0.0.0.0"
subnet_size = 0
notes = "Allow HTTPS"
}
3.Apply the configuration and observe the following output:
Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
#14
Others / Does Plesk support Trend Micro...
Last post by senthil - Sep 30, 2025, 07:43 AMApplicable to:
Does Plesk support Trend Micro Cloud One?
Answer
No, Trend Micro Cloud One from Trend Micro is not supported by Plesk.
- Plesk for Linux
- Plesk for Windows
Does Plesk support Trend Micro Cloud One?
Answer
No, Trend Micro Cloud One from Trend Micro is not supported by Plesk.
#15
Others / Unable to activate WP Guardian...
Last post by senthil - Sep 30, 2025, 07:38 AMSymptoms
Unable to activate WP Guardian vulnerability protection option in WordPress > example. com:
Vulnerability protection limit reached: your current plan allows to use vulnerability protection on 0 site(s).
Upgrade your hosting plan to use vulnerability protection on more sites.
Cause
Subscriptions > example. com > Account > Service plan > [name of the service plan] > Resources > Wordpress
websites with vulnerability protection is set to 0.
A bug ID EXTWPTOOLK-11928 has been reported in order to improve the error message.
Resolution
Unable to activate WP Guardian vulnerability protection option in WordPress > example. com:
Vulnerability protection limit reached: your current plan allows to use vulnerability protection on 0 site(s).
Upgrade your hosting plan to use vulnerability protection on more sites.
Cause
Subscriptions > example. com > Account > Service plan > [name of the service plan] > Resources > Wordpress
websites with vulnerability protection is set to 0.
A bug ID EXTWPTOOLK-11928 has been reported in order to improve the error message.
Resolution
- Log in to Plesk.
- Go to Subscriptions > example. com > Account > Service plan > [name of the service plan] > Resources >
Wordpress websites with vulnerability protection and enter a value higher than zero. - Click on "Update & Sync".
#16
Others / Attempt to convert CentOS into...
Last post by senthil - Sep 30, 2025, 07:31 AMSymptoms
yum update command installs the python2-leapp-0.16.0-2.el7.noarch package, while the leapp-0.14.0-
1.el7.noarch specifically requires python2-leapp = 0.14.0-1.el7. The downloaded version is causing the
conversion to fail due to inconsistency.
This is a bug with ID #PAUX-6405, which is fixed in the latest script iteration 1.4.0.
Resolution
Download the latest script version from the article How to make an in-place upgrade of a Plesk server from
CentOS 7 to AlmaLinux 8? and re-run the conversion.
- Attempt to convert CentOS 7.9 into AlmaLinux 8 with the centos2alma script crashes with errors like below:Code Select
2024-08-09 00:01:58,428 - INFO - --> Running transaction check 2024-08-09 00:01:58,428 -
INFO - ---> Package leapp.noarch 0:0.14.0-1.el7 will be installed 2024-08-09 00:01:58,428
- INFO - --> Processing Dependency: python2-leapp = 0.14.0-1.el7 for package: leapp-
0.14.0-1.el7.noarch 2024-08-09 00:01:58,430 - INFO - ---> Package leapp-upgrade-el7toel8-
deps.noarch 1:0.19.0-7.1.el7 will be installed 2024-08-09 00:01:58,433 - INFO - -->
Processing Dependency: pciutils for package: 1:leapp-upgrade-el7toel8-deps-0.19.0-
7.1.el7.noarch 2024-08-09 00:01:59,881 - INFO - --> Finished Dependency Resolution 2024-
08-09 00:01:59,923 - INFO - Error: Package: leapp-0.14.0-1.el7.noarch (elevate) 2024-08-
09 00:01:59,923 - INFO - Requires: python2-leapp = 0.14.0-1.el7 2024-08-09 00:01:59,923 -
INFO - Installed: python2-leapp-0.16.0-2.el7.noarch (@elevate) 2024-08-09 00:01:59,923 -
INFO - python2-leapp = 0.16.0-2.el7 2024-08-09 00:01:59,923 - INFO - Available: python2-
leapp-0.12.1-100.20210924142320684911.master.28.g1f03432.el7.noarch (elevate) 2024-08-09
00:01:59,923 - INFO - python2-leapp = 0.12.1-
100.20210924142320684911.master.28.g1f03432.el7 2024-08-09 00:01:59,923 - INFO -
Available: python2-leapp-0.14.0-1.el7.noarch (elevate) 2024-08-09 00:01:59,923 - INFO -
python2-leapp = 0.14.0-1.el7 2024-08-09 00:01:59,924 - INFO - Error: Package: 1:leapp-
upgrade-el7toel8-deps-0.19.0-7.1.el7.noarch (elevate) 2024-08-09 00:01:59,924 - INFO -
Requires: pciutils 2024-08-09 00:01:59,924 - INFO - You could try using --skip-broken to
work around the problem 2024-08-09 00:02:00,429 - INFO - You could try running: rpm -Va -
-nofiles --nodigest 2024-08-09 00:02:00,474 - ERROR - Command ['/usr/bin/yum', 'install',
'-y', 'leapp-0.14.0-1.el7', 'python2-leapp-0.14.0-1.el7', 'leapp-data-almalinux-0.1-
6.el7'] failed with return code 1 2024-08-09 00:02:00,475 - ERROR - Failed: installing
leapp. The reason: Command '['/usr/bin/yum', 'install', '-y', 'leapp-0.14.0-1.el7',
'python2-leapp-0.14.0-1.el7', 'leapp-data-almalinux-0.1-6.el7']' returned non-zero exit
status 1. 2024-08-09 00:02:01,039 - DEBUG - Going to write json
'/usr/local/psa/var/centos2alma/actions.json' with new data 2024-08-09 00:02:02,167 -
DEBUG - Sent error report 2024-08-09 00:02:02,168 - WARNING - Conversion status flag file
does not exist. Skip sending conversion status 2024-08-09 00:02:02,168 - ERROR -
centos2alma process has failed. Error: Failed: installing leapp. The reason: Command
'['/usr/bin/yum', 'install', '-y', 'leapp-0.14.0-1.el7', 'python2-leapp-0.14.0-1.el7',
'leapp-data-almalinux-0.1-6.el7']' returned non-zero exit status 1. 2024-08-09
00:02:02,170 - INFO - Going to free lockfile
'/usr/local/psa/var/centos2alma/centos2alma.lock'... ...
yum update command installs the python2-leapp-0.16.0-2.el7.noarch package, while the leapp-0.14.0-
1.el7.noarch specifically requires python2-leapp = 0.14.0-1.el7. The downloaded version is causing the
conversion to fail due to inconsistency.
This is a bug with ID #PAUX-6405, which is fixed in the latest script iteration 1.4.0.
Resolution
Download the latest script version from the article How to make an in-place upgrade of a Plesk server from
CentOS 7 to AlmaLinux 8? and re-run the conversion.
#17
Web Application / How to Create Vultr Reserved I...
Last post by Suhitha - Sep 30, 2025, 07:15 AMQuestion: How to Create Vultr Reserved IPs
The process of setting up and configuring a new server or service to make it ready for use.
Reserved IPs enable dedicated IP Addresses that are isolated from the public pool of Vultr's public IP addresses for attachment to your instances. Reserved IPs enable you to reserve a specific public IP address in a single Vultr location you can attach and use with your instances.
Follow this guide to create reserved IPs in your Vultr account 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 Add Reserved IP to create a new reserved IP address.
3.Click the Location drop-down and select your target Vultr location.
4.Click the Type drop-down and select the reserved IP address type.
5.Enter a new descriptive label in the Label field and click Add to create the reserved IP.
Vultr API
1.Send a GET request to the List Reserved IPs endpoint to view all reserved IPs active in your Vultr account.
2.Send a POST request to the Create Reserved IP endpoint to create a new reserved IP address in a specific Vultr location.
Visit the Create Reserved IP API page to view additional attributes to apply on the reserved IP.
Vultr CLI
1.List all active reserved IPs in your Vultr account.
Run vultr-cli reserved-ip create --help to view additional options to apply on the reserved IP.
Terraform
1.Ensure the Vultr Terraform provider is configured in your Terraform project.
2.Create a reserved IP (optionally attach to an instance), then apply.
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The process of setting up and configuring a new server or service to make it ready for use.
Reserved IPs enable dedicated IP Addresses that are isolated from the public pool of Vultr's public IP addresses for attachment to your instances. Reserved IPs enable you to reserve a specific public IP address in a single Vultr location you can attach and use with your instances.
Follow this guide to create reserved IPs in your Vultr account 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 Add Reserved IP to create a new reserved IP address.
3.Click the Location drop-down and select your target Vultr location.
4.Click the Type drop-down and select the reserved IP address type.
5.Enter a new descriptive label in the Label field and click Add to create the reserved IP.
Vultr API
1.Send a GET request to the List Reserved IPs endpoint to view all reserved IPs active in your Vultr account.
Code Select
console
$ curl "https://api.vultr.com/v2/reserved-ips" \
-X GET \
-H "Authorization: Bearer ${VULTR_API_KEY}"2.Send a POST request to the Create Reserved IP endpoint to create a new reserved IP address in a specific Vultr location.
Code Select
console
$ curl "https://api.vultr.com/v2/reserved-ips" \
-X POST \
-H "Authorization: Bearer ${VULTR_API_KEY}" \
-H "Content-Type: application/json" \
--data '{
"region" : "<location>",
"ip_type" : "<address_type>",
"label" : "<label>"
}'
Visit the Create Reserved IP API page to view additional attributes to apply on the reserved IP.
Vultr CLI
1.List all active reserved IPs in your Vultr account.
Code Select
console
$ vultr-cli reserved-ip list
2.Create a new reserved IP in a specific Vultr location.Code Select
console
$ vultr-cli reserved-ip create --label <label> --region <location> --type <address_type>
Run vultr-cli reserved-ip create --help to view additional options to apply on the reserved IP.
Terraform
1.Ensure the Vultr Terraform provider is configured in your Terraform project.
2.Create a reserved IP (optionally attach to an instance), then apply.
Code Select
terraform
resource "vultr_reserved_ip" "rip" {
region = "ewr"
ip_type = "v4" # v4 | v6
label = "web-rip"
# instance_id = vultr_instance.server.id
}
3.Apply the configuration and observe the following output:Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
#18
Others / Unable to edit wp-config.php v...
Last post by senthil - Sep 30, 2025, 07:13 AMSymptoms
Cause
The wp-config.php editing is blocked by Cloudflare, the message shown in the editor is an HTML document,
which translates to the following page:
Resolution
Contact Cloudflare support team or disable proxy for Plesk interface domain.
- Unable to edit wp-config.php for any domain via Plesk interface with the following error:
<!DOCTYPE html> <!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]--> <!--[if IE 7]> <html
class="no-js ie7 oldie" lang="en-US"> <![endif]--> <!--[if IE 8]> <html class="no-js ie8 oldie" lang="en-US">
<![endif]--> <!--[if gt IE 8]><!--> <html class="no-js" lang="en-US"> <!--<![endif]--> <head> <title>Attention
Required! | Cloudflare</title> <meta charset="UTF-8" /> <meta http-equiv="Content-Type"
content="text/html; charset=UTF-8" /> <meta http-equiv="X-UA-Compatible" content="IE=Edge" /> <meta
name="robots" content="noindex, nofollow" /> <meta name="viewport" content="width=device-width,initial-
scale=1" /> <link rel="stylesheet" id="cf_styles-css" href="/cdn-cgi/styles/cf.errors.css" /> <!--[if lt IE 9]><link
rel="stylesheet" id='cf_styles-ie-css' href="/cdn-cgi/styles/cf.errors.ie.css" /><![endif]-->
<style>body{margin:0;padding:0}</style> <!--[if gte IE 10]><!--> <script> if (!navigator.cookieEnabled) {
window.addEventListener('DOMContentLoaded', function () { var cookieEl =
document.getElementById('cookie-alert'); cookieEl. style.display = 'block'; }) } </script> <!--<![endif]-->
</head> <body> <div id="cf-wrapper"> <div class="cf-alert cf-alert-error cf-cookie-error" id="cookie-alert"
data-translate="enable_cookies">Please enable cookies.</div> <div id="cf-error-details" class="cf-error-
details-wrapper"> <div class="cf-wrapper cf-header cf-error-overview"> <h1 data-
translate="block_headline">Sorry, you have been blocked</h1> <h2 class="cf-subheadline"><span data-
translate="unable_to_access">You are unable to access</span> example. com </h2> </div><!-- /.header --
> <div class="cf-section cf-highlight"> <div class="cf-wrapper"> <div class="cf-screenshot-container cf-
screenshot-full"> <span class="cf-no-screenshot error"></span> </div> </div> </div><!-- /.captcha-
container --> <div class="cf-section cf-wrapper"> <div class="cf-columns two"> <div class="cf-column"> <h2
data-translate="blocked_why_headline">Why have I been blocked?</h2> <p data-
translate="blocked_why_detail">This website is using a security service to protect itself from online attacks.
The action you just performed triggered the security solution. There are several actions that could trigger
this block including submitting a certain word or phrase, a SQL command or malformed data.</p> </div>
<div class="cf-column"> <h2 data-translate="blocked_resolve_headline">What can I do to resolve this?
</h2> <p data-translate="blocked_resolve_detail">You can email the site owner to let them know you were
blocked. Please include what you were doing when this page came up and the Cloudflare Ray ID found at
the bottom of this page.</p> </div> </div> </div><!-- /.section --> <div class="cf-error-footer cf-wrapper w-
240 lg:w-full py-10 sm:py-4 sm:px-8 mx-auto text-center sm:text-left border-solid border-0 border-t border-
gray-300"> <p class="text-13"> <span class="cf-footer-item sm:block sm:mb-1">Cloudflare Ray ID: <strong
class="font-semibold">8ba359d0ffd49748</strong></span> <span class="cf-footer-separator
sm:hidden">•</span> <span id="cf-footer-item-ip" class="cf-footer-item hidden sm:block sm:mb-1"> Your IP:
<button type="button" id="cf-footer-ip-reveal" class="cf-footer-ip-reveal-btn">Click to reveal</button>
<span class="hidden" id="cf-footer-ip">195.214.233.8</span> <span class="cf-footer-separator
sm:hidden">•</span> </span> <span class="cf-footer-item sm:block sm:mb-1"><span>Performance &
security by</span> <a rel="noopener noreferrer" href="https: //www .cloudflare. com/5xx-error-landing"
id="brand_link" target="_blank">Cloudflare</a></span> </p> <script>(function(){function d(){var
b=a.getElementById("cf-footer-item-ip"),c=a.getElementById("cf-footer-ip-reveal");b&&"classList"in b&&
(b.classList.remove("hidden"),c.addEventListener("click",function()
{c.classList.add("hidden");a.getElementById("cf-footer-ip").classList.remove("hidden")}))}var
a=document;document.addEventListener&&a.addEventListener("DOMContentLoaded",d)})();</script>
</div><!-- /.error-footer --> </div><!-- /#cf-error-details --> </div><!-- /#cf-wrapper --> <script>
window._cf_translation = {}; </script> </body> </html> - This behavior is not reproducible when accessing Plesk interface directly via server IP.
- Plesk interface is behind Cloudflare proxy
Cause
The wp-config.php editing is blocked by Cloudflare, the message shown in the editor is an HTML document,
which translates to the following page:
Code Select
Sorry, you have been blocked
You are unable to access example.com
Why have I been blocked?
This website is using a security service to protect itself from online attacks. The action
you just performed triggered the security solution. There are several actions that could
trigger this block, including submitting a certain word or phrase, a SQL command or
malformed data.
What can I do to resolve this?
You can email the site owner to let them know you were blocked. Please include what you were doing when
this page came up and the Cloudflare Ray ID found at the bottom of this page.
Cloudflare Ray ID: hfdd73ghg94hf78 • Your IP:
203.0.113.2 • Performance & security by Cloudflare
Resolution
Contact Cloudflare support team or disable proxy for Plesk interface domain.
#19
Web Application / How to Attach Reserved IPs to ...
Last post by Suhitha - Sep 30, 2025, 07:05 AMQuestion: How to Attach Reserved IPs to a Vultr Instance
A storage volume that can be mounted to a Vultr instance to provide additional disk space.
Attaching a reserved IP to an instance enables a new public network address on the instance's main network interface. You can attach multiple reserved IPs on an instance to enable fast resolution and system management.
Follow this guide to attach reserved IPs to a Vultr instance 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 the Attach to Server drop-down, select your target instance and click Attach.
4.Click Attach Reserved IP in the confirmation prompt to apply the reserved IP to your instance
Vultr API
1.Send a GET request to the List Reserved IPs endpoint and note the target reserved IP's ID.
2.Send a GET request to the List Instances endpoint and note the target instance ID.
3.Send a POST request to the Attach Reserved IP endpoint to attach the reserved IP to the instance.
Vultr CLI
1.List all active reserved IPs in your Vultr account and note the target reserved IP ID.
2.List all instances in your Vultr account and note the target instance ID.
3.Attach the reserved IP to the instance.
Terraform
1.Open your Terraform configuration for the existing instance and reserved IP.
2.Set instance_id on the vultr_reserved_ip to attach, then apply.
3.Apply the configuration and observe:
Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
A storage volume that can be mounted to a Vultr instance to provide additional disk space.
Attaching a reserved IP to an instance enables a new public network address on the instance's main network interface. You can attach multiple reserved IPs on an instance to enable fast resolution and system management.
Follow this guide to attach reserved IPs to a Vultr instance 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 the Attach to Server drop-down, select your target instance and click Attach.
4.Click Attach Reserved IP in the confirmation prompt to apply the reserved IP to your instance
Vultr API
1.Send a GET request to the List Reserved IPs endpoint and note the target reserved IP's ID.
Code Select
console
$ curl "https://api.vultr.com/v2/reserved-ips" \
-X GET \
-H "Authorization: Bearer ${VULTR_API_KEY}"
2.Send a GET request to the List Instances endpoint and note the target instance ID.
Code Select
console
$ curl "https://api.vultr.com/v2/instances" \
-X GET \
-H "Authorization: Bearer ${VULTR_API_KEY}"
3.Send a POST request to the Attach Reserved IP endpoint to attach the reserved IP to the instance.
Code Select
console
$ curl "https://api.vultr.com/v2/reserved-ips/{reserved-ip}/attach" \
-X POST \
-H "Authorization: Bearer ${VULTR_API_KEY}" \
-H "Content-Type: application/json" \
--data '{
"instance_id" : "<target-instance-id>"
}'
Vultr CLI
1.List all active reserved IPs in your Vultr account and note the target reserved IP ID.
Code Select
console
$ vultr-cli reserved-ip list2.List all instances in your Vultr account and note the target instance ID.
Code Select
console
$ vultr-cli instance list3.Attach the reserved IP to the instance.
Code Select
console
$ vultr-cli reserved-ip attach <reserved-ip-id> --instance-id="<target-instance-id>"Terraform
1.Open your Terraform configuration for the existing instance and reserved IP.
2.Set instance_id on the vultr_reserved_ip to attach, then apply.
Code Select
terraform
resource "vultr_instance" "server" {
# ...existing fields
}
resource "vultr_reserved_ip" "rip" {
region = "ewr"
ip_type = "v4"
label = "web-rip"
instance_id = vultr_instance.server.id
}
3.Apply the configuration and observe:
Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
#20
Webserver / Unable to connect to the Plesk...
Last post by Suhitha - Sep 30, 2025, 05:44 AMQuestion: Unable to connect to the Plesk server via FTP: ftp: connect: Connection timed out
Symptoms
Cause
The wrong range for passive ports is set in /etc/proftpd.d/55-passive-ports.conf file.
Resolution
1.Log in to the server via SSH
2.Open the /etc/proftpd.d/55-passive-ports.conf file with text editor of your choice, vi for example
3.Change the line with the PassivePorts directive to the following:
4.Restart xinetd service to apply the changes:
# service xinetd restart
Symptoms
- Unable to connect to the server via FTP, the process fails with the error:
Code Select
227 Entering Passive Mode (203,0,13,2,119,129).
ftp: connect: Connection timed out
Code Select
Error: Connection timed out after 20 seconds of inactivity Error: Failed to retrieve directory listing
- The nmap utility shows that the passive port range (49152-65535) is in the closed state:
Code Select
nmap -p49192,65535 203.0.13.2
Host is up (0.25s latency).
PORT STATE SERVICE
49192/tcp closed unknown
65535/tcp closed unknown- In an attempt to manually calculate the result of the passive FTP port((119*256)+129=30593), the value is not within the range (49152-65535)
Cause
The wrong range for passive ports is set in /etc/proftpd.d/55-passive-ports.conf file.
Resolution
1.Log in to the server via SSH
2.Open the /etc/proftpd.d/55-passive-ports.conf file with text editor of your choice, vi for example
3.Change the line with the PassivePorts directive to the following:
Code Select
PassivePorts 49152 65535
4.Restart xinetd service to apply the changes:
# service xinetd restart