• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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.
 
Back
Top