Fixing error “Access to API is Disabled” in Plesk

When working with Plesk migrations, extensions, or automation scripts, you may encounter the error “Access to API is disabled for ::1“

At first glance, this can be confusing—especially since ::1 is the IPv6 loopback address, equivalent to 127.0.0.1 in IPv4. This post explains why the error occurs and walks through two reliable ways to fix it, using either the Plesk UI or the command line.

What Causes This Error “Access to API is Disabled for ::1” ?

Plesk restricts API access to a defined list of allowed IP addresses for security reasons.

The error appears when:

• A process attempts to access the Plesk API over IPv6
• The IPv6 address (::1) is not included in Plesk’s allowed administrative IPs

As a result, API calls originating from the local server are blocked.

Resolution Method 1: Fix via Plesk UI (Recommended)

This is the simplest and safest approach if you can log in to the Plesk admin interface.

Steps

1. Log in to your Plesk Control Panel as an administrator.
2. Go to Tools & Settings.
3. Under the Security section, click IP Access Restriction Management
   (in some versions this may appear as Restrict Administrative Access).
4. Click Add Network.
5. In the Subnet or IP address field, enter: ::1
6. Click OK to save the changes.

Result

Plesk will now allow API access from the local server over IPv6, and the error should be resolved immediately.

Resolution Method 2: Fix via panel.ini (CLI / Recovery Option)

If you cannot access the Plesk UI or prefer managing configuration via SSH, you can manually enable API access by editing the panel.ini file.

Steps

1. Connect to your server via SSH and Open the Plesk panel configuration file: 

vi /usr/local/psa/admin/conf/panel.ini

2. Add or modify the following configuration:

[api]
enabled = on
allowedIPs = ::1

3. If allowedIPs already exists, append ::1 to the list without spaces:

allowedIPs = 203.0.113.2,::1

4. Save the file and exit the editor.

You can also edit the panel.ini file directly from the Plesk UI by navigating to Plesk → Extensions → My Extensions → panel.ini Editor, which provides a safe, web-based way to modify Plesk configuration without using SSH.

Important Final Step: Restart the Migration

After applying either fix:

• Cancel any active migration or API-related tasks
• Restart the process from scratch

This ensures the new API access rules are picked up correctly.

Security Notes

• Only add IPs you trust to the API allowlist
• ::1 is safe because it represents local access only
• Avoid enabling unrestricted API access unless absolutely necessary

Conclusion

The error “Access to API is disabled for ::1” is a configuration issue—not a bug. By explicitly allowing the IPv6 loopback address in Plesk’s API access rules, you restore local API functionality while maintaining security.

If you’re still facing the error “Access to API is disabled for ::1” in Plesk and need expert help, it’s best to consult professionals who deal with such issues daily. With reliable Plesk server support services, our experienced engineers can quickly diagnose API permission problems, misconfigurations, or security restrictions and resolve them without downtime. Don’t let a Plesk error disrupt your server operations—reach out to us and ensure your Plesk environment remains secure, stable, and fully functional.