• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.

Plesk API receives 404 error

A

AndrewDH

Guest
Hi,

We use the Plesk API to add domains to the server. It has always worked great. Since yesterday, when making calls, we are getting 404 errors. We haven't touched the server in a while so this is very odd.

Can someone please help us identify the issue? We've been struggling to trying to figure this out.

Basically, when making the call to the same IP that has always worked, we're now getting no XML response a simply a 404 error. The server seems otherwise fine and Plesk itself is working normally.

Thanks for your help,

Andrew.
 
If I try to get any information about a domain and I use code that looks exactly like your samples (ie:
http://download1.parallels.com/Plesk/Plesk8.1/Doc/plesk-8.1-api-rpc-guide/33181.htm), the "parseResponse" function will not give the expected results and will not return valid XML.

If I print the output of "$response_string" from the above example, I will see simply get:
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>404 - Not Found</title>
</head>
<body>
<h1>404 - Not Found</h1>
</body>
</html>


Everything has always been working. And the panel (without the API) is otherwise working properly.

Thanks for your help,

Andrew.
 
No, I have version 10.3.1.

But note that the code has always worked with version 10.3.1. I don't seem to be getting errors... simply no response.
 
You must log in or register to reply here.

Similar threads

C
Issue Plesk Migrator Error(Failed to connect to target Plesk server by Plesk API: Plesk error [1005]: Protocol version '1.6.8.0' is not supported. Current
Replies
2
Views
7K
coffee34
C
O
Question Template Style Save Issues & 404 Error in T4 Framework
Replies
0
Views
2K
onghyr
O
K
Question Update Information to Plesk 18.0.79
Replies
1
Views
1K
Sofiia Kulish
Sofiia Kulish
A
Question Automate the migration process between Plesk servers using the XML/REST API
Replies
0
Views
2K
AndreyKashin
A
A
Question Developing a Plesk Extension to Serve Dynamic Content for roblaxmod Pages
Replies
1
Views
2K
Raul A.
R
Back
Top