• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

internal

  1. P

    Question Run a nodejs server internally without exposing online

    Hi. I'm moving from Pterodactyl to Plesk and I was wondering if it's possible to run a nodejs server internally (without exposing it to a domain) - so the nodejs server running on the domain can communicate with it, but it won't be publicly accessible. I suppose if not I'll have to expose it...
  2. P

    Issue [Plesk Obsidian] Internal redirects are now public?

    Hi there, Since we have updated plesk to obsidian, internal redirects (specified by .htaccess file) are public redirects: https://example.com/en/home -> https :// example.com/?q=en/home The browser of the user actually gets redirected by an internal redirect... Are internal redirects...
Back
Top