• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

APS Catalog error: Unable to parse the ATOM content

S

Sergey Fomin (Seyfin)

New Pleskian
I am getting the following error in Plesk, on the Applications page:

"APS Catalog error: Unable to parse the ATOM content. DOMDocument::loadXML(): Opening and ending tag mismatch: hr line 5 and body in Entity, line: 6"

Clearing cache (as advised here: http://kb.parallels.com/en/119029) - does not help, unfortunately.

As I noticed, the error started to occur right after Plesk was updated to v11.5.30_build115130819.13

Found this error in files:

/opt/psa/var/cache# vi d3b08b981b493e5687c45518970bc225-1024-0.cache

a:3:{s:3:"url";s:108:"http://catalog.marketplace.parallels.com/all-app.atom?obsolete=hide&pageSize=999999&order=%2Bname%2C-version";s:4:"time";i:1390479055;s:7:"content";s:166:"<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
";}

In my browser, the API catalog URL gives the same "502 Bad Gateway" error:

http://catalog.marketplace.parallel...ete=hide&pageSize=999999&order=+name,-version

How do we solve the issue?
 
install new app

Sergey Fomin (Seyfin) said:
I am getting the following error in Plesk, on the Applications page:

"APS Catalog error: Unable to parse the ATOM content. DOMDocument::loadXML(): Opening and ending tag mismatch: hr line 5 and body in Entity, line: 6"

Clearing cache (as advised here: http://kb.parallels.com/en/119029) - does not help, unfortunately.

As I noticed, the error started to occur right after Plesk was updated to v11.5.30_build115130819.13

Found this error in files:

/opt/psa/var/cache# vi d3b08b981b493e5687c45518970bc225-1024-0.cache

a:3:{s:3:"url";s:108:"http://catalog.marketplace.parallels.com/all-app.atom?obsolete=hide&pageSize=999999&order=%2Bname%2C-version";s:4:"time";i:1390479055;s:7:"content";s:166:"<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
";}

In my browser, the API catalog URL gives the same "502 Bad Gateway" error:

http://catalog.marketplace.parallel...ete=hide&pageSize=999999&order=+name,-version

How do we solve the issue?
Click to expand...

install New App from http://apsstandard.org/applications#searchterm=BlogEngine.NET into server (download first to computer)

click on Application Vault / my Apps / add App / Upload an APS package ok ;) and Clearing cache
 
Sergey Fomin (Seyfin) said:
I am getting the following error in Plesk, on the Applications page:

"APS Catalog error: Unable to parse the ATOM content. DOMDocument::loadXML(): Opening and ending tag mismatch: hr line 5 and body in Entity, line: 6"

Clearing cache (as advised here: http://kb.parallels.com/en/119029) - does not help, unfortunately.

As I noticed, the error started to occur right after Plesk was updated to v11.5.30_build115130819.13

Found this error in files:

/opt/psa/var/cache# vi d3b08b981b493e5687c45518970bc225-1024-0.cache

a:3:{s:3:"url";s:108:"http://catalog.marketplace.parallels.com/all-app.atom?obsolete=hide&pageSize=999999&order=%2Bname%2C-version";s:4:"time";i:1390479055;s:7:"content";s:166:"<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
";}

In my browser, the API catalog URL gives the same "502 Bad Gateway" error:

http://catalog.marketplace.parallel...ete=hide&pageSize=999999&order=+name,-version

How do we solve the issue?
Click to expand...
install New App from http://apsstandard.org/applications#searchterm=BlogEngine.NET into server (download first to computer)

click on Application Vault / my Apps / add App / Upload an APS package ok ;) and Clearing cache
 
Any progress on this? I can't see the KB as its labeled as internal.

I see all the apps installed from the application vault link on the home page, but I can't get any customers access to any apps.
I've enabled applications and the internal license pool in permissions, but still nothing.
 
You must log in or register to reply here.

Similar threads

X
Issue Cloudflare DNS Extension Fails with JsonException when Cloudflare returns non-JSON errors (502/524)
Replies
1
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
P
Resolved ERROR: syntax error, unexpected '?' (Helper.php:76)
Replies
4
Views
4K
Gorehide
G
B
Forwarded to devs following support article to protect folder by IP, it does not allow access (always 403) and worse, PHPs get downloaded, not executed
Replies
2
Views
4K
briveira
B
B
Issue Plesk www is not accesible at all, please help!
Replies
1
Views
2K
Bitpalast
Bitpalast
M
Resolved Internal error ;-P - 502 Bad Gateway - nginx | when adding new Domain or renew Let's Encrypt
Replies
5
Views
26K
Martin_Berlin
M
Back
Top