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

  1. J

    Issue Node.js using plesk extension

    Just set Selinux to permissive and it does function. However shouldn't of setting the type of allowed it to run with Selinux enabled?
  2. J

    Issue Node.js using plesk extension

    After re-reading the article again, I noticed that it mention errors are posted to the main error_log and not the domains. So after pulling that up I found there is a permission error. [Tue Jan 24 23:00:30 2017] [notice] caught SIGTERM, shutting down [Tue Jan 24 23:00:30 2017] [notice] SELinux...
  3. J

    Issue Node.js using plesk extension

    That is actually the article I was referring to. The server.js contains const http = require('http'); http.createServer(function(request, response) { response.writeHead(200, {'Content-Type': 'text/plain'}); response.end("Hello, World!\n"); }).listen(process.env.PORT)...
  4. J

    Issue Node.js using plesk extension

    I have been working on a node.js webapp on my server for a while. I recently updated my plesk to onyx and noticed they had an extension. So I backed up my node.js app, uninstalled node.js from the server and proceeded to add the extension. I re-uploaded the app and added it via the plesk...
Back
Top