• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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

    Issue Opening SSH Terminal in Plesk fails

    Indeed, if I modify the internal record of the machine to bypass the reverse proxy, it works. I don't understand the problem, because my other server has the same configuration and doesn't have the problem. After investigation, I will get back to you in a few days, thank you.
  2. M

    Issue Opening SSH Terminal in Plesk fails

    The port is not opened directly, there is a forward reverse proxy with these properties: location / { proxy_set_header X-Forwarded-Host $host:$server_port; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for...
  3. M

    Issue Opening SSH Terminal in Plesk fails

    No I don't use the port; the domain is configured from the command : plesk bin admin --enable-access-domain plesk-hosting.mydom.org
  4. M

    Issue Opening SSH Terminal in Plesk fails

    if i use https://192.168.1.30/modules/ssh-terminal/ it works if i use https://plesk-hosting.mydom.org/modules/ssh-terminal/ it doesn't work Don't have message, only a black page with the pop-up 'connection broken' the best log I found is checkSameOrigin error: Origin header...
  5. M

    Issue Opening SSH Terminal in Plesk fails

    Hi all, I have access to the terminal with Putty or from the interface if I use the IP to access the UI, but if I go through the domain name the terminal is blank and a "broken connection" error pops up plesk-ssh-terminal.service - Plesk SSH Terminal Backend Service Loaded: loaded...
  6. M

    Resolved plesk repair fs libboost/sw-engine failed

    This is now resolved, thank you
  7. M

    Resolved plesk repair fs libboost/sw-engine failed

    Here, thank you for your help $ plesk -v Product version: Plesk Obsidian 18.0.69.0 OS version: Ubuntu 22.04 x86_64 Build date: 2025/04/11 09:00 Revision: 3e5c47e262e0a871eb2c4041858dae0bb565c959 $ dpkg -l | grep plesk-libboost ii plesk-libboost-1.84...
  8. M

    Resolved plesk repair fs libboost/sw-engine failed

    $ plesk installer --select-release-latest --upgrade-installed-components [...] You already have the latest version of product(s) and all the selected components installed. Installation will not continue. This doesn't fix the problem :/
  9. M

    Resolved plesk repair fs libboost/sw-engine failed

    Hi all, After update 18.0.69, impossible to use `plesk repair fs` or `plesk repair installation` Checking Linux system files The permissions on some of the files packaged by Plesk are incorrect[ERROR] WARNING: Skip fixing 'plesk-libboost-1.84': Cannot find deb-archive for package...
  10. M

    Question Update Phusion passenger

    Hi, How to update Phusion passenger on Plesk ? (6.0.13) of Phusion Passenger(R). We strongly recommend upgrading to version 6.0.18. [ E 2023-07-10 08:43:13.9333 435295/T5 age/Cor/SecurityUpdateChecker.h:526 ]: Additional security update check information: - [Fixed in 6.0.14] [CVE-2018-25032]...
  11. M

    Issue file 'plesk.list.ai_back' invalid filename extension

    I am still investigating the SSL issue since the Let's Encrypt update, and it appears that the problem stems from the ZScaler certification. Since the update, it requires domains to be whitelisted. Could you please provide me with the list of domains used for the update and maintenance of Plesk...
  12. M

    Issue file 'plesk.list.ai_back' invalid filename extension

    Arf no time for edit my post lol. So, i installed new server, but only core plesk is installed, impossible install extension or other dependencies. but all dependencies is installed ?! no wet, lol !? Repair : # plesk repair all -y Reconfiguring the Plesk installation Reconfiguring the...
  13. M

    Issue file 'plesk.list.ai_back' invalid filename extension

    New Thread N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension N: Skipping acquire of configured file 'all/binary-amd64/Packages' as repository 'http://autoinstall.plesk.com/pool/WPB_18.0.51_64 all InRelease' doesn't support...
  14. M

    Resolved URGENT Certificate location not specified in response Lets Encrypt

    Thank's, This fixed part of the problem. the situation remains unchanged. Maybe I'm wrong, but I still think I'm restricted by this SSL issue. - INFO: Executing upgrade task: 2015-06-23-17-35-48 (clean) - [2023-04-06 10:27:49.074] 174245:642e828511938 ERR [panel] Error in cURL...
  15. M

    Resolved URGENT Certificate location not specified in response Lets Encrypt

    With the error unable to complete the installation, the extensions are hibernated but inaccessible?! OS : Ubuntu 22.04.2 LTS Product : Plesk Obsidian - Version 18.0.51 Update #1 ----------------------------------------------------------- $ plesk bin extension --list...
  16. M

    Issue Nodejs App error EACCES on port 80

    thanks, no problem with deployment for nodejs. by adding the reverse proxy it works, but i never needed to do this before with my other applications in vuejs/nuxtjs/nextjs they are shared and globally developed on port 80 / 3000
  17. M

    Issue Nodejs App error EACCES on port 80

    My first topic for subject : Strapi on Plesk Windows, port redirect error
Back
Top