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

Recent content by massin

  1. M

    Resolved Loads of messages "named[...]: network unreachable resolving '...': 2001:7fe::53#53"

    Thanks for this @tethis IT I had the same problem in AlmaLinux but in this Linux distribution I had to update the OPTIONS variable in /etc/sysconfig/named. OPTIONS="-4 -c /etc/named.conf -u named -n 2" I suspect it would be similar for RHEL/CentOS/Rocky Linux/etc.
  2. M

    Resolved transvhosts.pl fails to update apache default DocumentRoot

    Thanks, @Peter Debik - that was enough to point me in the right direction. I figured out the table via the daily mysql dump. Then I first ran an update on the DB table to change the HTTPD_VHOSTS_D variable, followed by re-running the transvhosts.pl script ... this time there were no errors and...
  3. M

    Resolved transvhosts.pl fails to update apache default DocumentRoot

    @Peter Debik - here is the output of running the repair (where Plesk is set to the default vhosts directory of /var/www/vhosts) and then running the transvhosts.pl script: # plesk repair web -y Checking Plesk version .............................................. [OK] Checking Apache...
  4. M

    Issue File dump-header not found on first position in archive.

    Recently I am getting an error report after a Scheduled Backup runs using an S3 repository. <?xml version="1.0"?> <execution-result log-location="/usr/local/psa/PMM/sessions/2023-04-13-020202.335/migration.result" local-dump-created="true" export-dump-created="true"...
  5. M

    Resolved transvhosts.pl fails to update apache default DocumentRoot

    To recap again: My GOAL (what I am tryng to achieve) is to move the vhosts from the default (/var/www/vhosts) to another drive (/mnt/data/vhosts). I USED transvhosts.pl to make this move (see first comment in this thread). The transvhosts.pl script did not change the DocumentRoot in Apache...
  6. M

    Resolved transvhosts.pl fails to update apache default DocumentRoot

    Peter - I'm not sure where I can be more clear. I am using transvhosts.pl to do the move.
  7. M

    Resolved transvhosts.pl fails to update apache default DocumentRoot

    I ran the script. I didn't do anything manually (except for the suggestion to manually create the missing htdocs directory AFTER the script failed).
  8. M

    Resolved transvhosts.pl fails to update apache default DocumentRoot

    To recap: I'm moving the HTTPD_VHOSTS_D from the default (/var/www/vhosts) to another drive (/mnt/data/vhosts). I got an error with apache after running the provided transvhosts.pl script (this is the initial comment in the thread) because the DocumentRoot didn't exist. You suggested...
  9. M

    Resolved transvhosts.pl fails to update apache default DocumentRoot

    Those directories shouldn't exist... I moved the VHOSTS directory to another drive.
  10. M

    Resolved transvhosts.pl fails to update apache default DocumentRoot

    Thanks, Peter. I did that and then ran the reconfigure script, but I still get errors: # /usr/local/psa/admin/bin/httpdmng --reconfigure-all Execution failed. Command: httpdmng Arguments: Array ( [0] => --reconfigure-domains [1] => example.com ) Details: [2023-04-12 10:11:47.554]...
  11. M

    Resolved transvhosts.pl fails to update apache default DocumentRoot

    Moving vhosts to a new drive following the documentation. The result is that the Apache default DocumentRoot is not updated: # plesk bin transvhosts.pl --dest-dir /mnt/data/vhosts/ --correct-scripts Moving files to new directory... Correct psa configuration file... Correct passwd file...
See more
Back
Top