Ramblings from MostlyChris

Tech stuff and a bit more

Browsing Posts in Plesk

I had occassion to run across the following question recently: "Plesk was just upgraded to version 9.2.x and all domains now have an overuse policy set to not allow overuse. I can manually change this to allow overuse, but is there a way to do this through the database so I don't have to do [...]

This is probably one of a million different ways to fix a Plesk upgrade failure. Here are the specifics… During an upgrade, it is very important that the hostname match the IP address in /etc/hosts because the updater will use that information to make connections, etc. While I was doing a recent upgrade I made [...]

There are times when you may need to migrate many IP addresses in Plesk. You could either do this by hand, one domain at a time or you can modify the database by hand which will save countless years of your life. I will assume you have logged into mysql and have selected the psa [...]

First, copy the smtp_psa file. cp /etc/xinetd.d/smtp_psa /etc/xinetd.d/smtp_additional Edit the newly copied file and replace the first line. Replace 'service smtp' with 'service submission' vi /etc/xinetd.d/smtp_additional Restart xinetd.d service xinetd restart Check that port 587 is listening on the server netstat -ltnp

NOTE: Most of this is now deprecated. You can use the autoupdater included in the ~[plesk]/bin directory to do the updates. Just make sure you back things up first! Back everything up! ifconfig eth0; hostname cat /etc/hosts ## Verify that the primary IP matches hostname and hosts file     Backups mkdir plesk_upgrade cp -a [...]