• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by MartinH

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