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

Recent content by administrierNix

  1. A

    Issue Server Error 502 Bad Gateway /

    ok I purchased the support licence. And wanted to install the software for Support access. Welll .... here the result: # plesk bin extension --install support-access /usr/bin/sw-engine: error while loading shared libraries: libodbc.so.2: cannot open shared object file: No such file or...
  2. A

    Issue Server Error 502 Bad Gateway /

    I cannot enter the licence key: plesk bin keyinfo --list | grep plesk_key_id | awk {'print $2'} /usr/bin/sw-engine: error while loading shared libraries: libodbc.so.2: cannot open shared object file: No such file or directory exit status 127 What to do now ?
  3. A

    Issue Server Error 502 Bad Gateway /

    ok, now tryed to uninstall with sudo apt-get remove libodbccr2 libodbcinst2 The result: Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet...
  4. A

    Issue Server Error 502 Bad Gateway /

    and now I need your help :) Peter, How can I solve this issue ?
  5. A

    Issue Server Error 502 Bad Gateway /

    So I tryed to install the missing files via sudo apt update sudo apt install unixodbc-dev This is the result: Hit:1 Index of /KAV_8.9.2 jammy InRelease Hit:2 Index of /pool/PSA_18.0.55_12681 jammy InRelease Hit:3 Index of /PHP80_17 jammy InRelease Hit:4 Index of /PHP82_17 jammy InRelease...
  6. A

    Issue Server Error 502 Bad Gateway /

    I also tryed # plesk repair all THe result; /usr/bin/sw-engine: error while loading shared libraries: libodbc.so.2: cannot open shared object file: No such file or directory exit status 127
  7. A

    Issue Server Error 502 Bad Gateway /

    additionally in ran # journalctl -xeu sw-engine.service Here is the result: # journalctl -xeu sw-engine.service Sep 21 11:56:18 xxxx.plesk.page sw-engine-fpm[67546]:> Sep 21 11:56:18 xxxx.plesk.page systemd[1]: sw-engine> ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support...
  8. A

    Issue Server Error 502 Bad Gateway /

    When I try to access plesk. I get this errormessage: Server Error 502 Bad Gateway Web server received an invalid response while acting as a gateway or proxy server. =============== I tryed to restart 'sw-engine.service' : # service sw-engine status ● sw-engine.service - Startup script for...
Back
Top