• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. M

    Question How does location and proxy_pass work?

    Hi, for basic testing I have set up a simple node server listening on port 5100 and a nginx directive location /api/ { proxy_pass http://127.0.0.1:5100/api/; } I am pretty new at this, but doesn't this directive mean, that a request like https://myserver.com/api/xxxx will be redirected to...
  2. M

    Question Bad Gateway error (502) on nginx

    Maybe this will help whoever is faced with the same problem: The upstream error means that there is something wrong in the communication from nginx up to the receiver (in my case nodejs running on localhost). I was under the (wrong) impression, that the whole site needed to employ SSL and set up...
  3. M

    Question Bad Gateway error (502) on nginx

    I followed 502 Bad Gateway nginx : How to solve? but can not resolve my issue on Obsidian: My localhost is listening on port 5000 - netstat -aon shows tcp 0 0 127.0.0.1:5000 0.0.0.0:* LISTEN and Apache is up and running - (checked with service apache2 status), Fail2Ban is not installed...
Back
Top