• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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

D
Issue 502 Bad Gateway - New Install - Restored from Backup
Replies
10
Views
567
MartinT
M
Mario Chamorro
Input Webmail 502 Bad Gateway
Replies
0
Views
1K
Mario Chamorro
Mario Chamorro
A
Issue 502 Gateway error with HTTP POST Requests but not GET requests
Replies
3
Views
976
Maarten
M
A
Issue Server Error 502 Bad Gateway /
Replies
11
Views
3K
dlabsnl
D
C
Issue 502 Bad Gateway - after applying updates
Replies
2
Views
2K
CChris
C
Back
Top