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

    Resolved Plesk Migration Issue....

    I reloaded the WP files again (except for Content) and the toolbar at the top is in the right place. But functions in the Dashboard displaying a JavaScript routine, drop-down, are broken. There shouldn't be any URL changes since it's the same URL on a different server. Peace, Gene
  2. G

    Resolved Plesk Migration Issue....

    So I migrated a domain from a cPanel server (version 98.0.9) to the latest Plesk Obsidian (18.0.39) on a Ubuntu 20.04.2 LTS server. Site running WordPress 5.8.1. So when logged in to the admin panel, I should be seeing the toolbar at the top. Instead I see the toolbar stuck at the bottom...
  3. G

    Resolved The component perl is not installed on the destination server.

    Remember this is installed via the browser /installer/install.cgi I saw noting in the logs that appeared relevant.
  4. G

    Resolved The component perl is not installed on the destination server.

    Progress. But now I get this when trying to run the installer: Server Error 500 Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator to inform of the time the error occurred and of...
  5. G

    Resolved The component perl is not installed on the destination server.

    Response: usr/local/psa/admin/sbin/autoinstaller: option '--install' is ambiguous; possibilities: '--installation-type' '--install-component' '--install-everything' '--install-system-only' ERROR: An unknown option was specified. Run Plesk Installer with the --help-options option to see...
  6. G

    Resolved The component perl is not installed on the destination server.

    I don't see it listed in the former. What command should I use?
  7. G

    Resolved The component perl is not installed on the destination server.

    Well this goes back to the original question: I see nothing in the Plesk interface that allows you to do this. How?
  8. G

    Resolved The component perl is not installed on the destination server.

    ?????? I've never seen the need on previous servers. Is there a setting I'm missing in Plesk for this?
  9. G

    Resolved The component perl is not installed on the destination server.

    Precisely, as I have always done in the years I've used it on other servers.
  10. G

    Resolved The component perl is not installed on the destination server.

    Look above. That's what I see when I try to run the install.cgi file.
  11. G

    Resolved The component perl is not installed on the destination server.

    It appears it is, but I'm still not able to run the command to make DadaMail work.
  12. G

    Resolved The component perl is not installed on the destination server.

    The command cited above does not work. What I get when I try to run the installer/updater for DadaMail is this: #!/usr/bin/perl use strict; use 5.10.1; use FindBin; use lib "$FindBin::Bin/../"; use lib "$FindBin::Bin/../DADA/perllib"; use lib "$FindBin::Bin/lib"; BEGIN { my $b__dir = (...
  13. G

    Resolved The component perl is not installed on the destination server.

    Still no answer. Very disappointing.
  14. G

    Question iTunes Podcast Feeds and HTTP HEAD requests

    I'm running a Plesk Linux server with latest Obsidian release. I've had to do a workaround for the RSS feed for our podcasts due to Apple's requirements that it support HTTP Head Requests. I've turned off all 301 HTTPS redirects that I can see while still supporting SSL on my sites, but I'm...
  15. G

    Input About that MariaDB 10.4.x Problem....

    A few weeks back, I posted a message about installing MariaDB — listed at the MariaDB site as a stable version — and being unable to create/modify databases and users on my Plesk Obsidian server. In response, rather than try to help, I was taken to task by a couple of forum regulars for...
  16. G

    Question Upgrade MariaDB

    I finally got a solution, but not from here. The one posted in these forums contained incorrect SQL commands that could have wrecked my Plesk installation. I will not say it was deliberate, but I am not terribly happy with the way this forum handles questions from people seeking advice. Gene...
  17. G

    Resolved Take Two! Error: SQLSTATE[HY000]: General error: 1449 The user specified as a definer ('root'@'localhost') does not exist

    Sorry, I don't know why you want to try to force me to have to reload my server because of this horrible transgression. I think it is reasonable to assume that the current stable version will be supported eventually. Meantime, I did find a workable solution, and have come to realize that you...
  18. G

    Resolved maria db connection

    That is not the issue obviously.
  19. G

    Resolved maria db connection

    Surprise: It may not be supported yet but it is listed at the MariaDB site is stable. They are at 10.5 beta now. So it's up to Plesk to decide when they will support it, and it would seem they will at some point in time.
  20. G

    Resolved Take Two! Error: SQLSTATE[HY000]: General error: 1449 The user specified as a definer ('root'@'localhost') does not exist

    It says: Error MySQL said: #1064 - You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'mysql> CREATE ALGORITHM=UNDEFINED DEFINER=`admin`@`localhost` SQL SECURITY DEFIN' at line 1 Try again.
Back
Top