• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

plesk api 502 bad gateway

  1. D

    Issue 502 Bad Gateway on Git fetch/deploy via Plesk API

    Hello, i am facing a problem with Plesk API when i fetch and deploy from Git on multiple domains. The request is being made from another server (used to do it from the same, but thought that that was causing the 502), i also tried to put inside a single API call multiple fetch/deploy (domains)...
  2. M

    Resolved Xml api add domain 502 bad gateway response

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