• 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.

Resolved Xml api add domain 502 bad gateway response

M

mywebmanavgat

New Pleskian
Hello there. I am adding a new domain with Plesk xml api. On the same server. but when apache is restarted when new domain is added, api response returns as 502 bad gateway.

Elegant reboot from Apache settings. Apache restart cycle 86400 entered. pipe logs are activated. but I still get 502 bad gateway answers.

Domain is being registered successfully, but I cannot continue other operations.

Plesk Obsidian Web Host Edition
Versiyon 18.0.27 CENTOS 7


Başparmak:
105670211_143150714047639_7891456378643894732_o.jpg 105381061_143150580714319_2123185384960997319_o.jpg
 
You must log in or register to reply here.

Similar threads

H
Resolved Laravel app "502 Bad Gateway" on page reload only
Replies
2
Views
4K
halnex
H
Z
Resolved Plesk updates failing: 502 Bad Gateway after installer update + “Unable to receive update information” error
Replies
1
Views
2K
zihniates
Z
T
502 bad gateway problem
Replies
7
Views
5K
Tempest
T
I
Issue 502 error Node and Angular SSR
Replies
2
Views
6K
igorosabel
I
T
Input [Feature Request] Add php_handler_id to Plesk Rest API [GET] /domains
Replies
4
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top