DomainGurus Forums: Forum: Plesk Parallels Control Panel

DomainGurus Forums: Forum: Plesk Parallels Control Panel - Recent Topics http://forums.domaingurus.com/ Our Community en Thu, 09 Sep 2010 07:17:00 +0000 k1ll3r on "Recovery Windows admin password Plesk" http://forums.domaingurus.com/topic/recovery-windows-admin-password-plesk#post-319 Fri, 08 Jan 2010 09:45:49 +0000 k1ll3r 319@http://forums.domaingurus.com/ The easiest way to recover the admin password on a Windows server with a Plesk installation is accessed by a shell or terminal server and run this command. "%plesk_bin%"\plesksrvclient.exe -get the window wont open with the Plesk admin password. You can also assign a new credential with: "%plesk_bin%"\plesksrvclient.exe -set If we add the final true also change the password of the Plesk database. Finally, if we use instead of drawing -nogui the result by the display screen in the console and send the password to the clipboard. JC on "recalculating statistics on Plesk" http://forums.domaingurus.com/topic/recalculating-statistics-on-plesk#post-227 Fri, 16 Oct 2009 14:31:26 +0000 JC 227@http://forums.domaingurus.com/ How to recalculate statistics for my domain in Plesk? korpa on "How do I change my Plesk password?" http://forums.domaingurus.com/topic/how-do-i-change-my-plesk-password#post-216 Wed, 12 Aug 2009 22:28:04 +0000 korpa 216@http://forums.domaingurus.com/ How do I change my Plesk password? admin on "How do I perform a disk-to-disk migration?" http://forums.domaingurus.com/topic/how-do-i-perform-a-disk-to-disk-migration#post-150 Sun, 14 Jun 2009 15:46:06 +0000 admin 150@http://forums.domaingurus.com/ <h1>How do I perform a disk-to-disk (chroot) migration?</h1> Plesk for Linux versions 8 and above support a disk-to-disk migration by exportingdata in a chroot shell and then importing it using the Plesk Migration Manager. (There is currently no method to perform a disk-to-disk migration on Plesk for Windows.If you have a Windows Plesk server, the only migration method is server-to-server. Youwill need to purchase a second server.) <hr />   NOTE: This procedure requires you to login to your server via SSH and use thecommand line. You should be fairly comfortable with using the command lineof a Linux server prior to performing this procedure. Some directory or file locations my be different on your server. You will need to be able toassess your server's configuration and adjust the following instructions as necessary to fityour server's configuration. If you are NOT comfortable using the command line on a Linux server, you should consider one of the following options: 1. Hire a qualified consultant with Linux experience to perform this procedure.2. Purchase a second server and perform a server-to-server migration instead. This can be completed entirely within the Plesk interface. Server-to-server Migration    using the Plesk Migration Manager from within the Plesk interface will yield identical results to this procedure DomainGurus is not responsible for data loss as a result of failure to completethis procedure correctly for your server and cannot recover any lost data.  This migration typically takes 2 hours or so to complete and performs a full migration of *ALL* Plesk related data including Plesk configuration, user accounts, mail boxes, Plesk-installed Web Applications, MySQL databases created from within Plesk, etcThis process may take longer than the above estimate. The actual time to completionwill vary, depending on the amount of data on your server. However this will result inmost complete and accurate migration possible. <hr />   NOTE: The Plesk export should be completed in a screen session to avoid interruption of theexport process should your SSH session become disconnected for any reason. The screenutility allows your shell to continue even if your SSH session is disconnected.Use your distribution's package manager to install the "screen" utilityEX: Fedora/CentOSyum install screenMandrivaurpmi screenSuSEzypper install screenDebian/Ubuntuapt-get install screen To start a screen session, simply typescreenShould you become disconnected from your SSH session, you can reconnect to your previouslystarted session by typingscreen -rTo end your screen session, simply typeexitPlease review the man page for your distribution's screen utility for additional usage information. <hr /> # These instructions assume that your old (slaved) disk is /dev/sdb. Depending on the# number of drives installed in your server, your old disk may not be /dev/sdb.# Replace /dev/sdb with the appropriate device name for your old (slaved) drive. # First be sure that your old disk is not mounted somewhere else. (Command is issued# twice, since /dev/sdb2 cannot be unmounted until other partitions are unmounted): <address>umount /dev/sdb*</address><address>umount /dev/sdb*</address> # Make a mount point for the old drive under /mnt <address>mkdir /mnt/old_disk</address> # Mount old partitions in proper structure under /mnt/old_disk <address>mount /dev/sdb2 /mnt/old_disk</address><address>mount /dev/sdb3 /mnt/old_disk/var</address><address>mount /dev/sdb6 /mnt/old_disk/home</address> # Stop Plesk and all related services <address>/etc/init.d/psa stopall</address> # Create a migration directory on the old drive (preferably on the /home partition# since that partition has the most space) and copy the Migration Manager components# to the migration directory <address>mkdir /mnt/old_disk/home/migration</address><address>cp -r /usr/local/psa/PMM/agents/shared/* /mnt/old_disk/home/migration</address><address>cp -r /usr/local/psa/PMM/agents/PleskX/* /mnt/old_disk/home/migration</address><address></address> ## NOTE: Begin screen session described above## chroot to the old disk# (Directory "/mnt/old_disk" now becomes "/" for the current shell) <address>export SHELL=/bin/bash</address><address>chroot /mnt/old_disk</address> # Start MySQL (Since you are chroot'ed to /mnt/old_disk, this will# start MySQL on your old drive and make that data available) <address>/etc/init.d/mysqld start</address> # NOTE: On SuSE and some other distributions, the MySQL process is simply named "mysql"# so you would simply enter# /etc/init.d/mysql start # cd to the migration directory and run run the PleskX.pl migration module create a dump# of your sites and data in Migration Manager format. <address>cd  /home/migration</address><address>chmod +x PleskX.pl</address><address>./PleskX.pl --dump-all -v5</address> # Once the export has completed, stop MySQL <address>/etc/init.d/mysqld stop</address> # Create a directory named "archive" and move all Migration Manager files to it# Move ONLY dump.xml back out <address>mkdir /home/migration/archive</address><address>mv /home/migration/* /home/migration/archive/</address><address>mv /home/migration/archive/dump.xml /home/migration/</address> # And exit the chroot environment <address>exit</address> ## NOTE: End screen session described above## Restart Plesk and related services (Since you are no longer in the chroot shell,# you are now starting Plesk on your new disk <address>/etc/init.d/psa start</address> # Now login to Plesk at <a href="https://<your-ip-address>:8443#" rel="nofollow">https://<your-ip-address>:8443#</a> and go to Server => Migration Manager => Start a new Migration## You will be prompted for the location of your data. Select Local Store, then select the# partition labeled /mnt/old_disk/home and then enter "migration" in the directory field. admin on "How to restore sites after OS reinstall Linux Plesk" http://forums.domaingurus.com/topic/how-to-restore-sites-after-os-reinstall-linux-plesk#post-149 Sun, 14 Jun 2009 15:43:43 +0000 admin 149@http://forums.domaingurus.com/ <h1>How to restore/copy sites after OS reinstall Linux + Plesk</h1> Once you have your new OS running, just log into Plesk, and create all the domains you wish to restore. After this is done, SSH to your server. Once in the command prompt you should have a tree structure under /home/httpd/vhost/domains If so then all you need to do is sync or update these directories with the info you have on your old drive, which most of the time is mounted under /mnt/old-drive or /mnt/orig-drive. To do this just do as following: rsync -auv /mnt/orig-drive/home/httpd/vhost/domain /home/httpd/vhost/domain This will update the folder in your current hard drive with info of the old hard drive (updating the files inside of it). Sometimes after this is done the owner and group that these files belong to is root, so the site wont immediately work, but you can change the owner and group, just go back to Plesk and go to the file manager under the desired domain. Once there you'll see an user and a group to your right just next to the file name and permissions, this is the user and group we will use on the domain directly at your server. chown user:group -R /home/httpd/vhost/domain This will change the owner and group for all the folders under the desired domain, including the domain folder itself, remember its important you gather the user and group from Plesk rather making it up. Now you can test <a href="http://domain/" rel="nofollow">http://domain/</a> and it should work just fine. admin on "create nightly dumps on Plesk Server" http://forums.domaingurus.com/topic/create-nightly-dumps-on-plesk-server#post-148 Sun, 14 Jun 2009 15:41:24 +0000 admin 148@http://forums.domaingurus.com/ How can I create nightly dumps of my MySQL databases on my Linux Plesk server? To perform nightly database dumps on a Plesk system, create a file /etc/cron.daily/mysqldump and add the following contents: #!/bin/bash DUMPDIR=/var/mysqldumps test -d ${DUMPDIR} || /bin/mkdir ${DUMPDIR} chmod 700 ${DUMPDIR} cd /var/lib/mysql/ for i in * do   test -d ${i} && /usr/bin/mysqldump -uadmin   -p<code>cat /etc/psa/.psa.shadow</code> <code>echo ${i}|sed -e 's////g'</code>   | /usr/bin/bzip2 > ${DUMPDIR}/${i}.sql.bz2 done The locations the dumps are made to can be adjusted by changing the DUMPDIR variable admin on "Plesk fails to start BIND or resolve on Fedora" http://forums.domaingurus.com/topic/plesk-fails-to-start-bind-or-resolve-on-fedora#post-147 Sun, 14 Jun 2009 15:39:06 +0000 admin 147@http://forums.domaingurus.com/ <h1>Plesk fails to start BIND or resolve on Fedora</h1> As with any strange behavior in Plesk, first run the updater. This will often either correct the problem you're experiencing or update packages that are contributing to the problem. In some cases, Plesk will give an error when trying to start named (BIND) from the services page. Check /var/log/messages after attempting to start and look for errors indicating that bind can't load files from /var/named because they're missing (not found). If you find these messages, the problem is most likely because of bind-chroot. The bind-chroot package starts BIND in a chroot jail, limiting the security risk should bind be breached. This creates a fake root directory exclusively for BIND in /var/named/run-root. When BIND is started, /var/named/run-root is mapped to / and BIND sees the contents as the root directory. This is why BIND can't find files that's looking for: Plesk is putting them in the real /var/named. To confirm that bind-chroot is installed, do 'rpm -qa|grep chroot'. To fix the problem do 'rpm -ev '. Then, try to start named from the Plesk Services page. Once this is complete, you may need to go into the DNS for each domain and hit "Switch" twice to resave the zone configs admin on "Unable to lock mailbox on Plesk" http://forums.domaingurus.com/topic/unable-to-lock-mailbox-on-plesk#post-146 Sun, 14 Jun 2009 15:37:31 +0000 admin 146@http://forums.domaingurus.com/ <h1>Unable to lock mailbox on Plesk</h1> Email error: "Unable to lock mailbox" on Plesk/Windows server   This can occur when the hostname is incorrectly set in MailEnable (the mail server used by Plesk). To add the correct hostname, you must use remote desktop to access the console (this can't be done through Plesk). First do the following. Click Start->(Click)run->(type)cmd.(Click Run). Now, in the command prompt type the following. cd %plesk_bin% From there run the following command. mchek --all --fix=all Wait for it to finish and it should run as normal Also another fix for SMTP issues on Plesk 7.5.3 windows Go to start->All Programs->Mail Neable->(click)MailEnable Administrator When that's running do the following. Click [+]-MailEnable  then Click [+]Mail Enable Management Click [+]-Servers" Click [+]-Localhost Click [+]-Connectors right click "SMTP" then go to "Properties" After you've completed that you will need to find the exact hostname of the box. Example (2k3s-221-28 -221-228 last numbers of the IP address.) Now put the 2k3s-221-28.aspadmin.net (aspadmin.net = domain of where it's at) into the "Local Domain Name:". Click "Apply" and click "ok" close MailEnable" and (Logged in as 'root' on the Windows 2003 server, right click the "Plesk server control" icon in the tray go to click "Control Panel" then when that's open click the check box next to "Mail Server" and on the right hand side click "Restart" it should all work again, no errors.     admin on "How do I renew my Plesk license?" http://forums.domaingurus.com/topic/how-do-i-renew-my-plesk-license#post-145 Sun, 14 Jun 2009 15:33:25 +0000 admin 145@http://forums.domaingurus.com/ <h1>How do I renew my Plesk license?</h1> I am receiving Plesk license expiration notices.  The Plesk control panel license must be renewed periodically. Plesk will send renewal notifications prior to the expiration date. When you get the pending expiration notice, take the following action to renew your Plesk license: 1- Log into Plesk Administration control panel on the server 2- Click on the Server icon in the left margin to display the Systems Administration page. 3- Click on the License Management icon in the System group. 4- Click on the Retrieve Keys icon. Your new key will be downloaded automatically. If an error message is displayed, please contact your provider. RogelioF on "Ports used by Plesk Panel" http://forums.domaingurus.com/topic/ports-used-for-plesk#post-105 Sun, 03 May 2009 07:30:48 +0000 RogelioF 105@http://forums.domaingurus.com/ You have to make sure your firewall have the following ports opened in order to Plesk Panel works correctly 20 for ftp-data; 21 for ftp; 22 for ssh; 25 for smtp; 53 for dns (TCP and UDP); 80 for http (web server and Parallels Plesk Panel updater); 106 for poppassd (for localhost only); 110 for pop3; 113 for auth; 143 for imap; 443 for https; 465 for smtps; 587 for mail message submission; 990 for ftps; 993 for imaps; 995 for pop3s; 3306 for mysql; 5224 for (outgoing connections only) plesk-license-update; 5432 for postgres; 8443 for plesk-https; 8880 for plesk-http; 9080 for tomcat; 5224 for license updates. admin on "Plesk for your Dedicated Server" http://forums.domaingurus.com/topic/plesk-for-your-dedicated-server#post-79 Mon, 20 Apr 2009 20:52:15 +0000 admin 79@http://forums.domaingurus.com/ <h1>Plesk for your Dedicated Server</h1> You need a solution for an easy way to control your website, this is the one. Plesk is a control panel that works like a solution for management of hosting providers on shared or dedicated hosting. This tool is deployed to make easier the problem of the management of web sites. This control panel reduces operating costs and resources at the same time that increase the efficiency and customer satisfaction. Plesk is mostly used for users of dedicated servers for a reason that is where we see that the management of web sites more difficult. The plesk panel has many features that can facilitate the management, access and control of multiple domain hosting, you can have a control of any of your websites, and you can control this by departments for example: Marketing, sales, support and others; these departments are managed like clients. With this client feature on the plesk control panel, you also can manage any single client with certain kind of limits, specific control of access for some clients; this is to make a structure like an enterprise where you have levels to access to specific points. This control panel resolves the problems of the management of all the services that you want to control, the websites and the support for your clients. admin on "Changing Plesk vhosts Directory" http://forums.domaingurus.com/topic/changing-plesk-vhosts-directory#post-64 Tue, 14 Apr 2009 23:03:01 +0000 admin 64@http://forums.domaingurus.com/ <h1>Changing Plesk "vhosts" Directory</h1> vhosts is the default directory in which Plesk stores its websites. It is often useful to change the default location of vhosts from /var/www/vhosts to a location with more space available, such as /home. Our default partitioning is as follows:     * 100MB /boot     * 10GB /     * 25GB /var     * 1.5GB swap     * REST /home As you can see, the var partition is very limited and customers with many clients will probably need more space. This guide will walk you through changing this directory for Plesk users.   Stop all running Plesk services # /etc/init.d/psa stopall Make a new directory to replace /var/www/vhosts within /home # mkdir /home/httpd Change directories to /var/www # cd /var/www Copy all data from vhosts into the new directory # cp -av vhosts/ /home/httpd/vhosts Verify that the same number of files exist in both directories # find vhosts/ -type f | wc -l # find /home/httpd/vhosts/ -type f | wc -l Remove vhosts # rm -rf vhosts/ Create a symbolic link, pointing all vhosts quiries to the new location # ln -s /home/httpd/vhosts/ . Edit the Plesk configuration file to reflet these changes # vim /etc/psa/psa.conf Replace this line HTTPD_VHOSTS_D /var/www/vhosts HTTPD_VHOSTS_D /home/httpd/vhosts Start Plesk # /etc/init.d/psa start Tell Plesk to reconfigure itself # /usr/local/psa/admin/bin/websrvmng --reconfigure-all